From owner-freebsd-current Thu Jan 18 12:29:31 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA00250 for current-outgoing; Thu, 18 Jan 1996 12:29:31 -0800 (PST) Received: from ubiq.veda.is (ubiq.veda.is [193.4.230.60]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id MAA00224 for ; Thu, 18 Jan 1996 12:29:15 -0800 (PST) Received: (from adam@localhost) by ubiq.veda.is (8.7.3/8.6.9) id UAA03513 for freebsd-current@freebsd.org; Thu, 18 Jan 1996 20:28:30 GMT Message-Id: <199601182028.UAA03513@ubiq.veda.is> Subject: Windows TCP/IP interoperability? To: freebsd-current@freebsd.org Date: Thu, 18 Jan 1996 20:28:29 +0000 (GMT) From: "Adam David" X-Mailer: ELM [version 2.4 PL25 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org Precedence: bulk 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? -- Adam David