From owner-freebsd-questions Sun Feb 28 16:18:36 1999 Delivered-To: freebsd-questions@freebsd.org Received: from mail.rdc1.on.home.com (ha1.rdc1.on.wave.home.com [24.2.9.66]) by hub.freebsd.org (Postfix) with ESMTP id CB96915366 for ; Sun, 28 Feb 1999 16:18:12 -0800 (PST) (envelope-from inge@home.com) Received: from mimico ([24.112.75.79]) by mail.rdc1.on.home.com (InterMail v4.00.03 201-229-104) with SMTP id <19990301001756.ZMEJ14824.mail.rdc1.on.home.com@mimico>; Sun, 28 Feb 1999 16:17:56 -0800 Message-ID: <001801be6f3b$6cc86aa0$4f4b7018@mimico.firstmaple.ca> From: "Edward Ing" To: "Greg Lehey" Cc: Subject: Re: TCP/IP on LAN drops after a few minutes. Date: Mon, 15 Mar 1999 18:27:42 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >What do you mean by "drops"? What are the symptoms? What version of >FreeBSD? Please describe what you observe. Version: FreeBSD 2.2.8. Using a DEC203 (Etherworks3) card. (le0 device). Running on a VESA bus 486 with 32M of ram and scsi disks. The network card is ISA. I configured FreeBSD to have 2 NICs. One to the Internet and one to my private (non-registered ip) with ip forwarding turned off. I also ensure that only TCP/IP was running on the Windows Machines.(i.e. no windows networking). The TCP/IP communications stops working at about 5 minutes every time after the FreeBSD machine is booted and rebooted. If I try to ftp or ping the FreeBSD box from WindowsNT or Window98 ping fails (times out) and ftp fails. From the FreeBSD side if I start pinging the Windows machine and let it continue right after I reboot, ping is okay at first but within 5 minutes the pinging will fail and a message will say something to the effect that "There is no buffer space available" everytime it tries to ping. If I start pinging after a period after reboot when I know the TCP/IP is down ping will tell me that there is a timeout. I am pretty sure the problem is on FreeBSD for the following reasons, if I try WindowsNT or Windows95, I have the problem. Using the same network card with Linux as the server rather that FreeBSD, I have no problem. If I swap the DEC 203 with another DEC 203 on FreeBSD, I still get the problem. But now I have swapped out the DEC and replaced it with a SMC adapter (ed0) and I have no problems. This doesn't solve the problem. It just avoids it. I wish I know enough about FreeBSD to poke around an figure out what is going on. When the TCP/IP droped I did netstat -r to check if the problem was not a routing problem, but netstat -r told me everything was okay. ie. My defaultroute and the gateway to my LAN was listed in the table. I also tried disabling routing and gateway on FreeBSD to isolate the problem. And also I made sure I did not have default route on Windows setup which is other than FreeBSD. -----Original Message----- From: Greg Lehey To: Edward Ing ; freebsd-questions@FreeBSD.ORG Date: Sunday, February 28, 1999 5:44 PM Subject: Re: TCP/IP on LAN drops after a few minutes. >On Monday, 15 March 1999 at 9:17:18 -0500, Edward Ing wrote: >> I have a ethernet lan network with a FreeBSD machine and a dual boot >> window98/windowsNT workstation machine. The FreeBSD machine has two NICs, >> one on the LAN and one on cable modem on the internet. >> >> Whenever I first boot the FreeBSD machine the TCP/IP is working fine. But >> after several miniutes the TCP/IP drops. If I reboot FreeBSD, everthing work >> again for five minutes. > >What do you mean by "drops"? What are the symptoms? What version of >FreeBSD? Please describe what you observe. > >> The FreeBSD is not set as a gateway or a router. There is no micrsoft >> neworking setup on the Win98/WindowsNT machine. This problem occurs with >> both NT and 98. > >Are you talking about FreeBSD or Microsoft? > >Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message