Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!hao!boulder!sunybcs!rutgers!bellcore!faline!sabre!gamma!pyuxp!pyuxe!pwy
From: pwy@pyuxe.UUCP (Peyton Yanchurak)
Newsgroups: comp.sys.att
Subject: Re: WIN TCP/IP
Message-ID: <528@pyuxe.UUCP>
Date: Sun, 13-Sep-87 14:32:23 EDT
Article-I.D.: pyuxe.528
Posted: Sun Sep 13 14:32:23 1987
Date-Received: Thu, 17-Sep-87 05:28:33 EDT
References: <5178@drutx.ATT.COM> <837@umix.cc.umich.edu>
Distribution: comp
Organization: Bell Communications Research
Lines: 34
Summary: What Release Please

In article <837@umix.cc.umich.edu>, honey@umix.cc.umich.edu (Peter Honeyman) writes:
> it's close ... but not quite all there.  some bugs:
> 
> o	the telnet client hangs when run from a layers layer.
> o	the tcp server is sloooow -- telnet to a 3b2 running
> 	win tcp/ip and "it's like not being there."
> o	there's some bizarre process interaction that i haven't
> 	been able to diagnose, preventing me from running a
> 	uucp server. 
> 
> the lack of a domain name server is also a hindrance.
> 
> on the other hand, the rest of the supplied utilities work, and it
> wasn't too hard to get ping and a uucp client to work.  
> 
> if i could, i'd try the lachman version, but their pricing policy
> precludes that tack.


There have been several versions of WIN TCP/IP for the 3B2 distributed
as either production releases, controlled introduction releases
of beta releases.

The production version of STREAMS based  WIN TCP/IP (known
as Release 2.1) was announced a couple a weeks ago as part
of AT&Ts big product announcement (386 based PC, 3B2/500 and the 3B4000).
Are the above problems part of the new 2.1 Release or are
they refering to the 2.0 beta STREAMS release or the eariler non
STREAMS release.  I know there were some problems with the earlier
releases, but I was hoping they would be corrected in the 2.1 release.

				Peyton Yanchurak
				Bellecore
				pyuxe!pwy