home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!olivea!spool.mu.edu!uwm.edu!cs.utexas.edu!csc.ti.com!tilde.csc.ti.com!pan.mc.ti.com!a722756
- From: a722756@roper.mc.ti.com (W. Donald Rolph)
- Newsgroups: comp.protocols.tcp-ip.ibmpc
- Subject: Re: TCP/IP and Windows for Workgroups
- Message-ID: <1992Dec15.104151@roper.mc.ti.com>
- Date: 15 Dec 92 15:41:51 GMT
- References: <9212010440.AA22334@cheetah.ece.clarkson.edu> <723269140snx@crynwr.com> <77040@hydra.gatech.EDU> <1992Dec07.185834.12251@microsoft.com>
- Sender: usenet@pan.mc.ti.com (USENET News System)
- Organization: Texas Instruments / Attleboro Mass / USA
- Lines: 16
- Originator: a722756@roper.mc.ti.com
-
-
- As an aside, we have approximatley 300 pcs running microsoft lanman over tcp/ip
- (bought froma variety of vendors). If the primary requirement is netbios over
- tcp/ip thenour experience wiht microsoft lanman tcp/ip has been very good
- (note the originalstack is really HPs). We use a variety of utilities on this
- stack, with the most prevelant being DECs pathworks tcp/ip (which sits on the HP
- tcp/ip stack and uses a variant of microsofts redirector).
-
- I believe firmly that tcp/ip must be provided by the system vendor, must be
- tightly integrated with the operating system, and am pleased that mircosoft is
- slowly moving towards this position!
- --
-
- Regards.
-
- Don Rolph a722756@pan.mc.ti.com WD3 MS10-13 (508)-699-1263
-