Date: Fri, 19 Jan 1996 00:38:45 +0000 (GMT) From: "Adam David" <adam@veda.is> To: terry@lambert.org (Terry Lambert) Cc: freebsd-current@freebsd.org Subject: Re: Windows TCP/IP interoperability? Message-ID: <199601190038.AAA03779@ubiq.veda.is> In-Reply-To: <199601182334.QAA06556@phaeton.artisoft.com> from "Terry Lambert" at Jan 18, 96 04:34:35 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > During the past 2 weeks (perhaps longer) I seem to have been experiencing > > diverse interoperability problems between FreeBSD current and Windows(TM), > > both in client and server roles. Typically it has manifested as the inability > > to establish a connection in either direction, or connections hanging and > > timing out after a minimal amount of data transfer. Does anyone know what > > might be going on here? > > I have seen no generic Windows/BSD TCP/IP interoperability problems > for WFWG or Windows95. Perhaps it is related to your client/server > software... can you describe you environment in more detail? This is definitely something that has occured since 2.1 and seems to affect many (but not all) TCP connections both incoming and outgoing. It has only been seen when the remote machine is a Windows PC, and affects for instance telnet,ftp,(dcc),http connections, which is why I mentioned it as a TCP/IP networking interoperability problem. [description of flakey RIP on local net] The Windows machines are not on the same local net. > If this doesn't help, try backing off to an older version of FreeBSD; > if this helps, then you will be able to CVS diff to find the actual > problem code. :-) yes -- Adam David <adam@veda.is>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199601190038.AAA03779>