Date: Fri, 19 Jan 1996 09:20:59 +0100 (MET) From: Christoph Kukulies <kuku@gilberto.physik.rwth-aachen.de> To: terry@lambert.org (Terry Lambert) Cc: adam@veda.is, freebsd-current@FreeBSD.ORG Subject: Re: Windows TCP/IP interoperability? Message-ID: <199601190821.JAA02867@gilberto.physik.rwth-aachen.de> In-Reply-To: <199601182334.QAA06556@phaeton.artisoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > Followups on this should be redirected to -questions, unless you > believe you are having this problem because of -current specific > changes? > > > 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? > > I do know that there is a well known problem caused by Microsoft's > TCP/IP listening to RIP responses (in violation of legal usage of the > packets) and dropping connections based on this. That is, if there is > a flakey network on your wire, it will cause the windows boxes to act > flakey. The "fix" for this is to put a gateway box between the > offending box and the Windows boxes so that they are not on the same > logical subnet (since this will isolate them from the broadcasts). > > There is also a known problem with Windows NT boxes illegally generating > RIP packets and causing other hosts to dump. This is fixed in the > latest release of NT, or a patch is available through MSN. Have you > recently added an NT machine to a previously functional network? Is this what has been reported a year ago (by Keith B.) as the so called 'sniper bug' ? > > > 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. > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. > --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199601190821.JAA02867>