From owner-freebsd-questions Wed Apr 5 18: 7:15 2000 Delivered-To: freebsd-questions@freebsd.org Received: from wat-border.sentex.ca (waterloo-hespler.sentex.ca [199.212.135.66]) by hub.freebsd.org (Postfix) with ESMTP id 0591B37B7A5 for ; Wed, 5 Apr 2000 18:07:09 -0700 (PDT) (envelope-from mike@sentex.net) Received: from granite.sentex.net (granite-atm.sentex.ca [209.112.4.1]) by wat-border.sentex.ca (8.9.3/8.9.3) with ESMTP id VAA20782; Wed, 5 Apr 2000 21:06:59 -0400 (EDT) (envelope-from mike@sentex.net) Received: from chimp (ospf-mdt.sentex.net [205.211.164.81]) by granite.sentex.net (8.8.8/8.6.9) with ESMTP id VAA11924; Wed, 5 Apr 2000 21:06:57 -0400 (EDT) Message-Id: <4.2.2.20000405210130.036af008@mail.sentex.net> X-Sender: mdtancsa@mail.sentex.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Wed, 05 Apr 2000 21:04:16 -0400 To: Jens Rehsack From: Mike Tancsa Subject: Re: connection problem: FreeBSD Computer does not respond Cc: freebsd-questions@FreeBSD.ORG In-Reply-To: <38EBD7DF.4307F55E@informatik.uni-halle.de> References: <38EA7F40.FE128093@informatik.uni-halle.de> <20000404172309.V20770@fw.wintelcom.net> <38eab248.7085097@mail.sentex.net> <4.2.2.20000405074454.0368cdf8@mail.sentex.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 02:18 AM 4/6/2000 +0200, Jens Rehsack wrote: >But since today morning I let the machine ping it's right neighbor(?). >It works uninterrupted. >But yesterday I tries to ping the machine if it doesn't send packets out >by itself and it does not response. > >To say it again: >1) If I boot the machine, it will not answer, but the NIC >gets/recognizes the packets. >2) If I send some data out (f.e. echo request, ns lookup), the machine >answers packets for ca. 3 hours. >3) Then it seems to be dead from world, but a look to the console shows: >it's alive. >4) GoTo 2 ':-) Well, my money would be something with the NIC. Perhaps it doesnt set its media type correctly or its busted ? I dont know, but I would suspect it, or the driver perhaps. Do you have another type of network card you can try ? I am not familiar with the vx driver or how well it performs. I generally stick to the Intel Etherexpress Pro and plain old NE2000 PCIs when I need something very cheap. ---Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message