The machine is working fine. After some time (2-3 days) the machine cannot
be reached over the network anymore. No ping, no telnet, no ssh. Now the
funny part: After logging into the machine by the console, the network
connection is restored immediately.
APM features in the BIOS are turned off (that was my first guess). But
unfortunately this did not help.
It's a TYAN S1836DLUAN Thunder 100 Mainboard, which is equipped with a
Intel 82558 10/100 Ethernet-Controller.
Assigned to dledford
I'm getting this problem almost exactly, except it's version 6.2. (Hmmmm, I
wonder if it's the same thing? Maybe I should post a new bug...) The difference
is that the server's keyboard is not physically accessable to me, as it is
co-located. Here's the trick: if I log into one of the other co-located
machines at the same site, I can then ssh from that box to the screwed-up box
over the LAN! Then if I type "ping <machine on internet>" the network
connection is restored for a few minutes, until it disappears again.
My temporary fix is to have "ping yahoo.com > /dev/null &" running at all times.
The first report looks like the a known problem with the intel stuff that should
be mostly fixed in 2.2.16 but not 100% of cases. Please try the update kernel
and let m eknow
The second is the classic misconfigured bridge (probably 3com) which is not set
to broadcast frames to an unknown mac address but instead drop them.
Believed fixed in 6.2 errata kernel.
Other problem appears to be non Linux
I have same problem with network on a RedHat 6.0 2.2.5-22.
Sometimes networks disconnects misteriously, and i have to reboot the
With new 2.2.16-3 upgrade the problem was fixed?