Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!lll-crg!mordor!sri-spam!nike!ucbcad!ucbvax!TRANTOR.UMD.EDU!louie
From: louie@TRANTOR.UMD.EDU (Louis A. Mamakos)
Newsgroups: mod.protocols.tcp-ip
Subject: Ultrix 1.2 and unacceptable tcp packets
Message-ID: <8609162110.AA01204@trantor.UMD.EDU>
Date: Tue, 16-Sep-86 17:10:37 EDT
Article-I.D.: trantor.8609162110.AA01204
Posted: Tue Sep 16 17:10:37 1986
Date-Received: Wed, 17-Sep-86 12:28:58 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 18
Approved: tcp-ip@sri-nic.arpa

I've noticed other TCP problems with Ultrix 1.2's TCP.  After we installed
ULTRIX on a MicroVAX system, we don't seem to be able to send mail to our
Sperry 1100 system anymore.  The connection just hangs after a bit.  This
concerned me greatly, being one of the authors of the TCP/IP software on
the Sperry host.  None of our other systems had any problems, (2.9BSD UNIX,
4.2 BSD UNIX, Wollongong VMS, FUZZBALL, *Ultrix 1.1*).  Examination of
trace data on the Sperry indicates that it's just waiting for more data
on the SMTP connection after sending a window update.

(Flame on)
Our solution?  Very simple.  Trash Ultrix and run 4.3 BSD.  Not only has
DEC managed not to fix broken code, but they've even broken working code!

I'll just bet DECNET works though.
(Flame off)

Louis A. Mamakos  WA3YMH    Internet: louie@TRANTOR.UMD.EDU
University of Maryland, Computer Science Center - Systems Programming