Date: Tue, 5 Dec 2000 14:42:01 -0500 From: "Drew J. Weaver" <drew.weaver@thenap.com> To: 'Julian Elischer' <julian@elischer.org> Cc: "'freebsd-net@freebsd.org'" <freebsd-net@freebsd.org> Subject: RE: Really odd problem Message-ID: <B1A7D9973EBED3119ADD009027DC8649180846@mailman.thenap.com>
next in thread | raw e-mail | index | archive | help
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C05EF3.700E0AEA
Content-Type: text/plain;
charset="iso-8859-1"
I *could* do that, whats the hostname of your mail server? I'll have it ping
that =p 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
-----Original Message-----
From: Julian Elischer [mailto:julian@elischer.org]
Sent: Tuesday, December 05, 2000 2:30 PM
To: Drew J. Weaver
Cc: 'freebsd-net@freebsd.org'
Subject: Re: Really odd problem
> "Drew J. Weaver" wrote:
>
> We have a Freebsd 4.2 box on our network, after the box boots,
it
> brings up the network and everything is great, I can telnet into it..
> everything good, but about 30-60 minutes later no incoming traffic is
getting
> to the server. If i ping the machine, or telnet to it, I get nothing. If I
go
> to the terminal and ping anything then it "wakes up" does anyone have any
idea
> what would cause it to stop "listening" to incoming network requests? This
is
> becoming 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..
the transmit timeout for many drivers will try reinitialise the chip.
Which may bring it back to life... (for a while)
you could always add 'ping -i 120 [some address]'
to some startup script
:-)
>
> Thanks,
> -Drew
--
__--_|\ Julian Elischer
/ \ julian@elischer.org
( OZ ) World tour 2000
---> X_.---._/ presently in: Budapest
v
------_=_NextPart_001_01C05EF3.700E0AEA
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2650.12">
<TITLE>RE: Really odd problem</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=3D2>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</FONT></P>
<P><FONT SIZE=3D2>-Drew</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Julian Elischer [<A =
HREF=3D"mailto:julian@elischer.org">mailto:julian@elischer.org</A>]</FON=
T>
<BR><FONT SIZE=3D2>Sent: Tuesday, December 05, 2000 2:30 PM</FONT>
<BR><FONT SIZE=3D2>To: Drew J. Weaver</FONT>
<BR><FONT SIZE=3D2>Cc: 'freebsd-net@freebsd.org'</FONT>
<BR><FONT SIZE=3D2>Subject: Re: Really odd problem</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>> "Drew J. Weaver" wrote:</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT =
SIZE=3D2>>  =
; We have a Freebsd 4.2 box on our network, after the box boots, =
it</FONT>
<BR><FONT SIZE=3D2>> brings up the network and everything is great, =
I can telnet into it..</FONT>
<BR><FONT SIZE=3D2>> everything good, but about 30-60 minutes later =
no incoming traffic is getting</FONT>
<BR><FONT SIZE=3D2>> to the server. If i ping the machine, or telnet =
to it, I get nothing. If I go</FONT>
<BR><FONT SIZE=3D2>> to the terminal and ping anything then it =
"wakes up" does anyone have any idea</FONT>
<BR><FONT SIZE=3D2>> what would cause it to stop =
"listening" to incoming network requests? This is</FONT>
<BR><FONT SIZE=3D2>> becoming very tiresome and i've done everything =
known to me.</FONT>
</P>
<P><FONT SIZE=3D2>Are you getting messages on the console?</FONT>
</P>
<P><FONT SIZE=3D2>possibly the card is bad and dies after a =
while..</FONT>
<BR><FONT SIZE=3D2>the transmit timeout for many drivers will try =
reinitialise the chip.</FONT>
<BR><FONT SIZE=3D2>Which may bring it back to life... (for a =
while)</FONT>
</P>
<P><FONT SIZE=3D2>you could always add 'ping -i 120 [some address]' =
</FONT>
<BR><FONT SIZE=3D2>to some startup script </FONT>
</P>
<P><FONT SIZE=3D2>:-)</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> Thanks,</FONT>
<BR><FONT SIZE=3D2>> -Drew</FONT>
</P>
<P><FONT SIZE=3D2>-- </FONT>
<BR><FONT SIZE=3D2> __--_|\ Julian =
Elischer</FONT>
<BR><FONT SIZE=3D2> =
/ \ julian@elischer.org</FONT>
<BR><FONT SIZE=3D2> ( =
OZ ) World tour 2000</FONT>
<BR><FONT SIZE=3D2>---> X_.---._/ presently in: =
Budapest</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; v</FONT>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01C05EF3.700E0AEA--
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B1A7D9973EBED3119ADD009027DC8649180846>