From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1QX0ET-0000EF-OP for garchives@archives.gentoo.org; Thu, 16 Jun 2011 00:14:50 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 5DADE1C003; Thu, 16 Jun 2011 00:13:23 +0000 (UTC) Received: from mail.ukfsn.org (mail.ukfsn.org [77.75.108.10]) by pigeon.gentoo.org (Postfix) with ESMTP id 1326C1C003 for ; Thu, 16 Jun 2011 00:13:21 +0000 (UTC) Received: from localhost (smtp-filter.ukfsn.org [192.168.54.205]) by mail.ukfsn.org (Postfix) with ESMTP id 90617DEC44 for ; Thu, 16 Jun 2011 01:13:20 +0100 (BST) Received: from mail.ukfsn.org ([192.168.54.25]) by localhost (smtp-filter.ukfsn.org [192.168.54.205]) (amavisd-new, port 10024) with ESMTP id bui1xEhzhzzu for ; Thu, 16 Jun 2011 01:13:20 +0100 (BST) Received: from wstn.localnet (unknown [78.32.181.186]) by mail.ukfsn.org (Postfix) with ESMTP id 5BF9FDEC14 for ; Thu, 16 Jun 2011 01:13:20 +0100 (BST) From: Peter Humphrey Organization: at home To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Internet Date: Thu, 16 Jun 2011 01:13:19 +0100 User-Agent: KMail/1.13.7 (Linux/2.6.38-gentoo-r6; KDE/4.6.3; x86_64; ; ) References: <4DF762E6.3050306@club-internet.fr> <4DF773EF.4010609@club-internet.fr> <4DF77EAE.6080804@asyr.hopto.org> In-Reply-To: <4DF77EAE.6080804@asyr.hopto.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201106160113.19693.peter@humphrey.ukfsn.org> X-Archives-Salt: X-Archives-Hash: 5dd7b66a8cedcbf30f26ab6c0345973c On Tuesday 14 June 2011 16:30:54 Thanasis wrote: > on 06/14/2011 05:45 PM Cahn Roger wrote the following: > >> Can you check the network cable and connections to ensure that is > >> actually correct? > > > > The cable and connections are well. > > NIC became faulty? After reading this thread, I'd say that either the NIC is faulty or he's using a cross-over cable instead of straight-through. Or someone's standing on the cable :-) -- Rgds Peter