From owner-freebsd-current Fri Jan 19 00:20:06 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA27738 for current-outgoing; Fri, 19 Jan 1996 00:20:06 -0800 (PST) Received: from mail.rwth-aachen.de (mail.RWTH-Aachen.DE [137.226.144.9]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id AAA27659 for ; Fri, 19 Jan 1996 00:19:56 -0800 (PST) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de) by mail.rwth-aachen.de (PMDF V5.0-4 #13110) id <01I06TXVP83K002L69@mail.rwth-aachen.de>; Fri, 19 Jan 1996 09:20:43 +0100 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) id JAA02867; Fri, 19 Jan 1996 09:21:00 +0100 Date: Fri, 19 Jan 1996 09:20:59 +0100 (MET) From: Christoph Kukulies Subject: Re: Windows TCP/IP interoperability? In-reply-to: <199601182334.QAA06556@phaeton.artisoft.com> To: terry@lambert.org (Terry Lambert) Cc: adam@veda.is, freebsd-current@FreeBSD.ORG Reply-to: Christoph Kukulies Message-id: <199601190821.JAA02867@gilberto.physik.rwth-aachen.de> X-Mailer: ELM [version 2.4 PL24] Content-type: text Content-transfer-encoding: 7BIT Sender: owner-current@FreeBSD.ORG Precedence: bulk > > 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