From owner-freebsd-current Thu Jan 18 15:47:31 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA12846 for current-outgoing; Thu, 18 Jan 1996 15:47:31 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA12841 for ; Thu, 18 Jan 1996 15:47:28 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id QAA06556; Thu, 18 Jan 1996 16:34:35 -0700 From: Terry Lambert Message-Id: <199601182334.QAA06556@phaeton.artisoft.com> Subject: Re: Windows TCP/IP interoperability? To: adam@veda.is (Adam David) Date: Thu, 18 Jan 1996 16:34:35 -0700 (MST) Cc: freebsd-current@freebsd.org In-Reply-To: <199601182028.UAA03513@ubiq.veda.is> from "Adam David" at Jan 18, 96 08:28:29 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII 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? 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.