From owner-freebsd-current Fri Jan 19 13:54:28 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA17188 for current-outgoing; Fri, 19 Jan 1996 13:54:28 -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 NAA17181 for ; Fri, 19 Jan 1996 13:54:23 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA08703; Fri, 19 Jan 1996 14:45:14 -0700 From: Terry Lambert Message-Id: <199601192145.OAA08703@phaeton.artisoft.com> Subject: Re: Windows TCP/IP interoperability? To: kuku@gilberto.physik.rwth-aachen.de Date: Fri, 19 Jan 1996 14:45:14 -0700 (MST) Cc: terry@lambert.org, adam@veda.is, freebsd-current@FreeBSD.ORG In-Reply-To: <199601190821.JAA02867@gilberto.physik.rwth-aachen.de> from "Christoph Kukulies" at Jan 19, 96 09:20:59 am 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 > > 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' ? Yes. It's really a problem when you have an older MS/TCP listening to the bogus RIP broadcasts and using them to preeemptively dump connections. The problems are synergistic. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.