How would you trouble-shoot this no Web?

[dgermann]

Hi--

Without my server up and running, I cannot connect to the Web with a Web browser. Once the Web connection is made, as long as I keep that computer up, I can shut off the browser, turn it back on, and surf as I want. When I shut off or reboot this computer, if the server is not up, I cannot again access the Web--until I reboot the server, then reboot the client machine, in that order.

Trouble is, my server crashed yesterday.

My server was a Red Hat 9.0 box at 192.168.0.200. My client is an Ubuntu 6.06 at 192.168.0.107. My router (Lynksys WRT54G) is at 192.168.0.1. My other two linux boxes (also Ubuntu 6.06) can get to the Web fine. So can at least one Windows box.

The server is mainly to serve up smb/cifs shares in a production environment. It did not even have X installed.

I have checked network settings and networking from the gnome System > Administration menu on this client box and have found no references to 192.168.0.200--I had thought that perhaps that was set up as my default gateway, but that does not seem to be the case.

How else would you trouble shoot this?

Thanks!

[teeitup]

Is your network interface up and does it have an IP address?

/sbin/ifconfig

Can you connect to your router and other systems using a browser and/or ssh?

What does your routing table look like?

/sbin/route

Can you launch Google by IP address (http://66.102.7.104/)?

Since your using Gnome try a traceroute using Network Tools, or use the command line and see where it hangs up

/usr/bin/traceroute www.google.com

Good Luck,

[mrBen]

Are you using static IPs or DHCP? If DHCP, check that the server is not the main DHCP server, rather than the linksys box.

[dgermann]

mrBen and teeitup--

Last night we had a major lightning storm. It was forecast, so with trepidation, I shut down the whole network and unplugged everything from the walls--router, switch, modem, all computers, etc. I thought for sure I would not be able to get on the Web in the morning.

Luckily, I was wrong. I have rebooted this machine a couple of times today and can still get on to the Web.

So the problem was either sporadic in the past, or taking the old box off the network solved something.

In any case, for now, no more problem.

Thanks for your help, mrBen and teeitup!