From owner-freebsd-questions@FreeBSD.ORG Fri Jan 2 04:35:32 2004 Return-Path: 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 9245C16A4CE for ; Fri, 2 Jan 2004 04:35:32 -0800 (PST) Received: from pfepa.post.tele.dk (pfepa.post.tele.dk [195.41.46.235]) by mx1.FreeBSD.org (Postfix) with ESMTP id C068D43D46 for ; Fri, 2 Jan 2004 04:35:30 -0800 (PST) (envelope-from neoneye@adslhome.dk) Received: from [10.0.0.10] (0x50c4101e.boanxx9.adsl-dhcp.tele.dk [80.196.16.30]) by pfepa.post.tele.dk (Postfix) with ESMTP id 27626480097 for ; Fri, 2 Jan 2004 13:35:29 +0100 (CET) From: Simon Strandgaard To: freebsd-questions In-Reply-To: <20040101194356.GB17271@happy-idiot-talk.infracaninophile.co.uk> References: <1072982749.16817.11.camel@server.neoneye.home> <20040101194356.GB17271@happy-idiot-talk.infracaninophile.co.uk> Content-Type: text/plain Organization: Message-Id: <1073046721.19645.1.camel@server.neoneye.home> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.4 Date: 02 Jan 2004 13:32:01 +0100 Content-Transfer-Encoding: 7bit Subject: Re: unknown slowdown X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: neoneye@adslhome.dk List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Jan 2004 12:35:32 -0000 On Thu, 2004-01-01 at 20:43, Matthew Seaman wrote: > On Thu, Jan 01, 2004 at 07:45:49PM +0100, Simon Strandgaard wrote: > > In my wardrobe I have my noisy/fast server, to which I can connect via > > the xdmcp protocol, either with my silent desktop machine or if im not > > at home I can use ssh. It worked fluently for 6 months, but recently it > > has become non-responsive and lagging. The network speed are 100Mbits > > and I have killed all suspicius processes. I have even tried to restart > > the server, but no luck. > > Two things to check: > > Does 'netstat -i' show any errors, either on your server or on your desktop? > > If so, then there's probably a fault somewhere in your networking > setup. It could be a simple as a network cable not plugged in > properly or as bad as your switch/hub slowly giving up the ghost, > or one of the NICs in one of the machines spiralling into oblivion. [snip] Solved: It was a bad network cable.. Now it works again, Thanks :-) -- Simon Strandgaard