On Thu, Jan 7, 2010 at 2:43 PM, Mike Connors <[email protected]> wrote: > Denis Heidtmann wrote: >> My plan at this point is to leave the computer up to see if it fails >> while running. Also, I am borowing a card to enable more >> troubleshooting, when the trouble occurs. >> >> Any other ideas? >> >> > Once you can't ping the upstream modem, see if the interface is still up, > has a valid ip address, a routing table, and an arp entry for the modem > if it's directly connected. What I'd be trying to determine is whether it's > a NIC hw faiure, OS, or TCP/IP stack bug. > > Rather than me regurgitating all the commands for this, take a look at > this page. > > http://www.linuxhomenetworking.com/wiki/index.php/Quick_HOWTO_:_Ch04_:_Simple_Network_Troubleshooting > Thanks for that reference. It seems to address potential problems for systems much more complicated than mine. Mine is a desktop computer connected to a dsl modem via a 3' cable. I executed some of the diagnostics mentioned and saved the results to a text file for future reference (the network is fine at the moment.) When it breaks again I will repeat the diagnostics to see if it shows anything informative.
My goal is to blame the NIC, the cable, or the modem. What else should be on this list? -Denis _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
