From owner-freebsd-net Thu Dec 7 6:12:39 2000 From owner-freebsd-net@FreeBSD.ORG Thu Dec 7 06:12:33 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from server.sito.it (server.sito.it [195.191.47.194]) by hub.freebsd.org (Postfix) with ESMTP id 7540937B400 for ; Thu, 7 Dec 2000 06:11:14 -0800 (PST) Received: from dado ([212.110.20.254]) by server.sito.it (#.#.#/?.?.?) with SMTP id PAA91873 for ; Thu, 7 Dec 2000 15:11:16 +0100 (CET) Message-ID: <023201c06057$7a7541a0$0a01a8c0@dado.gruppoidea.it> Reply-To: "Davide Lemma" From: "Davide Lemma" To: Subject: Re: Really odd problem Date: Thu, 7 Dec 2000 15:10:39 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_022F_01C0605F.DBFFADE0" 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-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. ------=_NextPart_000_022F_01C0605F.DBFFADE0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I had the same problem... my server was an ADM-II K6-400, the = motherboard was a SOYO and 3Com50X as ethernet card, by now the problem = is solved by changing the motherboard and the case. For my personal opinion it is something linked to the APM, or some = strange bug in the motherboard's chipset, not the nic card... because = now it works right. =20 bye Davide =20 =20 I *could* do that, whats the hostname of your mail server? I'll have = it ping that =3Dp No messages on the console at all, and again i've = tried two seperate NIC cards both the (onboard intel) and the offboard = PCI Intel 10/100 -Drew=20 =20 =20 -----Original Message-----=20 From: Julian Elischer [mailto:julian@elischer.org]=20 Sent: Tuesday, December 05, 2000 2:30 PM=20 To: Drew J. Weaver=20 Cc: 'freebsd-net@freebsd.org'=20 Subject: Re: Really odd problem=20 =20 =20 > "Drew J. Weaver" wrote:=20 >=20 > We have a Freebsd 4.2 box on our network, after the box = boots, it=20 > brings up the network and everything is great, I can telnet into = it..=20 > everything good, but about 30-60 minutes later no incoming traffic = is getting=20 > to the server. If i ping the machine, or telnet to it, I get = nothing. If I go=20 > to the terminal and ping anything then it "wakes up" does anyone = have any idea=20 > what would cause it to stop "listening" to incoming network = requests? This is=20 > becoming very tiresome and i've done everything known to me.=20 Are you getting messages on the console?=20 possibly the card is bad and dies after a while..=20 the transmit timeout for many drivers will try reinitialise the = chip.=20 Which may bring it back to life... (for a while)=20 you could always add 'ping -i 120 [some address]'=20 to some startup script =20 :-)=20 =20 =20 >=20 > Thanks,=20 > -Drew=20 --=20 __--_|\ Julian Elischer=20 / \ julian@elischer.org=20 ( OZ ) World tour 2000=20 ---> X_.---._/ presently in: Budapest=20 v=20 ------=_NextPart_000_022F_01C0605F.DBFFADE0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: Really odd problem

I had the=20 same problem... my server was an ADM-II K6-400, the motherboard was = a SOYO=20 and 3Com50X as ethernet card, by now the problem is solved by = changing the=20 motherboard and the case.
For my personal opinion it is something linked = to the APM,=20 or some strange bug in the motherboard's chipset, not the nic = card...=20 because now it works right.
 
bye Davide

 

I *could* do that, whats the hostname of your mail = server?=20 I'll have it ping that =3Dp No messages on the console at all, and = again i've=20 tried two seperate NIC cards both the (onboard intel) and the = offboard PCI=20 Intel 10/100

-Drew


-----Original Message-----
From:=20 Julian Elischer [mailto:julian@elischer.org]=20
Sent: Tuesday, December 05, 2000 2:30 PM =
To: Drew J. Weaver
Cc:=20 'freebsd-net@freebsd.org'
Subject: Re: = Really odd=20 problem


> "Drew J. Weaver" wrote: =
>
>          = We=20 have a Freebsd 4.2 box on our network, after the box boots, = it=20
> brings up the network and everything is = great, I can=20 telnet into it..
> everything good, but = about=20 30-60 minutes later no incoming traffic is getting
> to the server. If i ping the machine, or telnet to it, = I get=20 nothing. If I go
> to the terminal and = ping=20 anything then it "wakes up" does anyone have any = idea=20
> what would cause it to stop = "listening" to=20 incoming network requests? This is
> = becoming=20 very tiresome and i've done everything known to me.

Are you getting messages on the console? =

possibly the card is bad and dies after a = while..=20
the transmit timeout for many drivers will try = reinitialise=20 the chip.
Which may bring it back to = life... (for a=20 while)

you could always add 'ping -i 120 [some address]'=20
to some startup script 

:-)


>
> Thanks, =
> -Drew

--
     =20 __--_|\  Julian Elischer
     = /       \=20 julian@elischer.org
    = (  =20 OZ    ) World tour 2000
--->=20 X_.---._/  presently in:  Budapest
          &nbs= p;=20 v

------=_NextPart_000_022F_01C0605F.DBFFADE0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message