From owner-freebsd-questions Sat Nov 11 11:13: 0 2000 Delivered-To: freebsd-questions@freebsd.org Received: from priv-edtnes04-hme0.telusplanet.net (fepout2.telus.net [199.185.220.237]) by hub.freebsd.org (Postfix) with ESMTP id D311037B479 for ; Sat, 11 Nov 2000 11:12:58 -0800 (PST) Received: from woodsie ([161.184.241.49]) by priv-edtnes04-hme0.telusplanet.net (InterMail vM.4.01.02.11 201-229-116-111) with SMTP id <20001111191253.TZID20445.priv-edtnes04-hme0.telusplanet.net@woodsie> for ; Sat, 11 Nov 2000 12:12:53 -0700 From: "Dave Woods" To: Subject: Sambe dropping Connections Date: Sat, 11 Nov 2000 12:20:30 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 In-Reply-To: <20001111125018.A26077@gv.edu.pl> Importance: Normal Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is an interesting discovery we made: What we had is a FreeBSD 3.4 server with one file share that an NT server scanned for new files. When we upgraded to FreeBSD 4.0 the scanning software started failing every two hours (yes it was poorly written software). We thought we had misconfigured the new drive but then downgraded it to 3.4 and everything works fine again. I am assuming that this has something to do with the difference between FreeBSD 3.4 and 4.0's TCP stack. Hope this helps out someone who might run into the same problem. I am doubting it is possible to keep the TCP of 3.4 while running 4.0 so this seems to be the only solution to the problem. Very strange. Hope this helps someone out. Woods To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message