home *** CD-ROM | disk | FTP | other *** search
/ NetNews Usenet Archive 1992 #27 / NN_1992_27.iso / spool / comp / os / mswindo / apps / 5050 < prev    next >
Encoding:
Internet Message Format  |  1992-11-18  |  4.4 KB
  1. Xref: sparky comp.os.ms-windows.apps:5050 comp.protocols.tcp-ip.ibmpc:6403
  2. Newsgroups: comp.os.ms-windows.apps,comp.protocols.tcp-ip.ibmpc
  3. Path: sparky!uunet!gumby!destroyer!news.iastate.edu!isucard.card.iastate.edu!MLONG
  4. From: MLONG@isucard.card.iastate.edu
  5. Subject: Re: TCP/IP and Windows for Workgroups
  6. Message-ID: <168A3C99A.MLONG@isucard.card.iastate.edu>
  7. Sender: news@news.iastate.edu (USENET News System)
  8. Organization: CARD
  9. References:  <1992Nov17.162001.14830@devildog.att.com>
  10. Date: Wed, 18 Nov 1992 20:20:06 GMT
  11. Lines: 26
  12.  
  13. In article <1992Nov17.162001.14830@devildog.att.com>                                                                                                  
  14. steveh@devildog.att.com (Steve Hendershott) writes:                                                                                                   
  15.                                                                                                                                                       
  16. >If I currently use TCP/IP (FTP's) to communicate from DOS/Windows to                                                                                 
  17. >UNIX (telnet, ftp, etc), can I put up Windows for Workgroups (WFWG) and                                                                              
  18. >set up to communicate with my associates who also install WFWG? In                                                                                   
  19. >other words, is it that simple to say WFWG will work over TCP/IP? What                                                                               
  20. >else does one have to do? Is there a simple answer or is it                                                                                          
  21. >complicated?                                                                                                                                         
  22. >                                                                                                                                                     
  23. >Thanks for any help I can get in understanding this.                                                                                                 
  24. >                                                                                                                                                     
  25. >Steve Hendershott                                                                                                                                    
  26. >steveh@devildog.att.com                                                                                                                              
  27. >--                                                                                                                                                   
  28. >Stephen W. Hendershott                                                                                                                               
  29. >steveh@devildog.att.com                                                                                                                              
  30. >                                                                                                                                                     
  31. Wg4W peer server is like a SMB file server, like LAN Server or LAN Manager                                                                            
  32. or PC LAN Program.  I have never used it (Wg4W) but would assume that                                                                                 
  33. it uses NETBIOS for communication.  You may be able to get the NETBIOS                                                                                
  34. to be encapsulated in TCP/IP packets if nessassary.  HP's LAN Manager/X                                                                               
  35. does it this way, the newer LAN Server can do this, and newer LAN Manager??                                                                           
  36. can probably do this too.                                                                                                                             
  37.                                                                                                                                                       
  38. Mike Long                                                                                                                                             
  39.