From owner-freebsd-questions Wed Sep 18 21:27:55 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1CEAD37B401 for ; Wed, 18 Sep 2002 21:27:54 -0700 (PDT) Received: from mx2.licentia.net (24-196-96-227.jvl.wi.charter.com [24.196.96.227]) by mx1.FreeBSD.org (Postfix) with SMTP id 6C01043E65 for ; Wed, 18 Sep 2002 21:27:53 -0700 (PDT) (envelope-from lists@stevenfettig.com) Received: (qmail 45309 invoked from network); 19 Sep 2002 04:27:52 -0000 Received: from unknown (HELO Unknown21) (10.6.18.1) by mx2.licentia.net with SMTP; 19 Sep 2002 04:27:52 -0000 Date: Wed, 18 Sep 2002 23:27:52 -0500 Subject: Re: NIC problem Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v482) From: Steve Fettig To: Jason Hunt , freebsd-questions@freebsd.org Content-Transfer-Encoding: 7bit In-Reply-To: <20020918185937.R16127-100000@lethargic.dyndns.org> Message-Id: <296BB961-CB88-11D6-BDD9-00039384AB84@stevenfettig.com> X-Mailer: Apple Mail (2.482) Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wednesday, September 18, 2002, at 06:00 , Jason Hunt wrote: > On Tue, 17 Sep 2002, Bob Bomar wrote: > >> I have a dual P-200 file server that is haveing some connection >> problems. When I ssh to the box, I login in fine, but some times >> it lags for a while, but the two boxes are physically sitting next >> to each other, and are on ports that are side by side on the >> switch. While I ssh out of the box from the console, to another >> box on the LAN, it is still intermitant. Any body have any ideas? >> > > This is just a stab in the dark, but could it be DNS? > Personal experience has shown this to be the usual culprit of ssh lag (whereby a server cannot reverse lookup the IP and waits until the timeout period has lapsed). But if you are talking about lag after the password has been accepted, etc, then it is almost certainly a network problem (NIC, Switch/hub, netmask settings wrong, cable, RF from a florescent light) - I had dealt with this a lot over a wireless connection where I wasn't monitoring the signal strength and found that as the signal dropped, so did my lag (and quite significantly). So, I would imaging the same thing would be true of a wired network if there are physical problems. The usual suspects are cable and hub... at least in my experience - even when I was so sure that it wasn't that I wasted two days on a network problem only to find out that the switch port was slowly going bad... If you have any extra equipment (or money) try different NIC's completely, different cables (that shouldn't be difficult since they are so close to one another) and also a different hub. Also, while you are ssh'ing, try pinging the server from the client in a separate window or terminal and see if you ever get "stoppage" - if you do, it almost surely is a network problem. HTH, Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message