Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Distribution: Ubuntu 8.04.1 desk; Red Hat 9.0 server
Posts: 275
Rep:
How would you trouble-shoot this no Web?
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.
Run ethereal and grab all traffic to compare what happens when a non-afflicted system gets through the router, to when the afflicted system fails to get through. This would seem to almost certainly be a router configuration issue, to me. Is there any disruption of service within the local LAN? What if you make one of the other hosts into a web server?
Distribution: Ubuntu 8.04.1 desk; Red Hat 9.0 server
Posts: 275
Original Poster
Rep:
rod--
Thanks for your quick reply!
Any tricks to running ethereal? I have never run it. I will grab it and see what it can tell me.
I just ran through the router configuration and did not see anything that looked suspicious to my untrained eye. At least there were no references to 192.168.0.200.
There was one place where it said the range of ipaddresses was 192.168.0.0--200, and another where it said the last digit was 100--149. All workstations are within both ranges, the only machine outside is -200. (8 computers total).
No, I have noticed no interruption in service on the LAN.
Not sure how I would go about making another machine a web server. You make it sound trivial....
Since there is already a couple of linux hosts on the LAN, they may already have web servers installed, simply waiting to be started:
Code:
/sbin/service httpd start
might do it, if Ubuntu is anything similar to Redhat/Fedora setups.
As for the operation of ethereal, it is beyond the scope a discussion like this to fully explain it's workings. I can tell you this, though: you will probably need to run it as root in order to get it to work as a promiscuous receiver. Also, if you are on a switched network LAN, you may want to buy or borrow a hub, to allow you to see traffic from multiple hosts, unless you have a manged switch that allows it to be operated like a hub. Too bad your router isn't a linux based router, as that would allow you to get a better look at what traffic is being blocked, and why.
Distribution: Ubuntu 8.04.1 desk; Red Hat 9.0 server
Posts: 275
Original Poster
Rep:
rod--
Thanks. You are helping my education!
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.