Xref: utzoo comp.unix.ultrix:4872 comp.sys.mips:1094 Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!cbmvax!grr From: grr@cbmvax.commodore.com (George Robbins) Newsgroups: comp.unix.ultrix,comp.sys.mips Subject: Re: TCP chokes between Ultrix 4 and 3.1c systems Message-ID: <15023@cbmvax.commodore.com> Date: 10 Oct 90 07:08:03 GMT References: <3246@uakari.primate.wisc.edu> Reply-To: grr@cbmvax.commodore.com (George Robbins) Organization: Commodore, West Chester, PA Lines: 26 In article <3246@uakari.primate.wisc.edu> bin@primate.wisc.edu writes: > From article , by lgy@phys.washington.edu (Laurence G. Yaffe): > > gamiddle@maytag.waterloo.edu (Guy Middleton) writes: > >>Aha. That seems to fix the problem. I'll disable trailers on all our mips > >>boxes; they are evil in any case. > > > > Why? > > I don't know the "official" answer, the the practical answer is: > precisely because they cause the kind of problems seen in this thread. > Not all implementations of TCP/IP know about them, and some handle them > badly, and you get crashed, hung or broken connections of all sorts. > Such as (this is what I've seen here, communicating with, e.g., 3b2's On the other hand, Ultrix 3.1 trailer negotiation seems to work, and if Ultrix 3.1 and Ultrix 4.0 can't talk TCP with and without trailers, then there is something wrong. I hope someone having this diffuculty follows up with the Support Center or an SPR, in this day and age, networking problems shouldn't be left lingering around till the "next release"... -- George Robbins - now working for, uucp: {uunet|pyramid|rutgers}!cbmvax!grr but no way officially representing: domain: grr@cbmvax.commodore.com Commodore, Engineering Department phone: 215-431-9349 (only by moonlite)