Topic: Lost internet access from my Server.

[turtle2472]

I have been running SME 7.2 in gatewayserver mode for a few months now and it's been great.  At some time yesterday I lost my connection to the web.  I plugged a computer directly into the cable modem and have a good connection there, but there is nothing going through the server.  I'm not sure what the issue is because I'm really not an IT guy but just a geek when it comes to computers.  Linux/Unix isn't something I'm very good with at all either, so this limits me doing things in a command line type interface just because of my ignorance.  I know how to do it, I just don't yet understand what I'm doing, if that makes sense. :\

SME is handling my internal DHCP fine and there just seems to be the break in my internet.  I'm not sure how to test it or even what happened.  It just quit working.  I installed a Brother HL-2070N on the network the night before, but that shouldn't have any relevance to this problem.

Where do I start?  I went through the local setup on the server and verified everything looked good.  Both NICs are listing like they should and all the other configuration settings are as they should be.

When I try to connect to an IP address I get this:

ERROR
The requested URL could not be retrieved

While trying to retrieve the URL: http://208.67.222.222/

The following error was encountered:

    * Connection to Failed

The system returned:

    (101) Network is unreachable

The remote host or network may be down. Please try the request again.

Your cache administrator is admin@digitalphoto-etc.com.
Generated Wed, 10 Oct 2007 17:22:18 GMT by lenny.digitalphoto-etc.com (squid/2.5.STABLE14)

When I attempt to connect via URL I get this:

Server not found

Firefox can't find the server at wiki.contribs.org.

    *   Check the address for typing errors such as
          ww.example.com instead of
          www.example.com

    *   If you are unable to load any pages, check your computer's network
          connection.

    *   If your computer or network is protected by a firewall or proxy, make sure
          that Firefox is permitted to access the Web.

[arne]

What I would have done:

First log into the server from shell.

Then ping som web address: "ping www.bbc.com"

And the ip:  "ping 212.58.226.232"

No you know if you have internet connection to/from the server.

Than check the network adapters:

"ifconfig eth0" and "ifconfig eth1"

try also to ping a local address. Post result of finding here.

Ping also from a local client to the gateway server.

[turtle2472]

What I would have done:

First log into the server from shell.

Then ping som web address: "ping www.bbc.com"

ping: unknown host www.bbc.com

And the ip:  "ping 212.58.226.232"

connect: Network is unreachable

No you know if you have internet connection to/from the server.

Than check the network adapters:

"ifconfig eth0" and "ifconfig eth1"

try also to ping a local address. Post result of finding here.

Code: [Select]

eth0 Link encap:Ethernet HWaddr 00:C0:F0:31:6C:56
       inet addr:192.168.4.1  Bcast:192.168.4.255 Mask:255.255.255.0
       UP BROADCAST RUNNING MULTICAT MTU:1500 Metric:1
       RX packets:641 errors:1 dropped:0 overruns:0 frame:0
       TX packets:398 errors:0 dropped:0 overruns:0 carrier:0
       collisions:0 txqueuelen:1000
       RX bytes:58812 (57.1KiB) TX bytes:38486 (37.5 KiB)
       Interrupt:209 Base address:0xa00

eth1 Link encap:Ethernet  HWaddr 00:11:09:16:0F:5D
       UP BROADCAST RUNNING MULTICAST  MTU:1500 Metric:1
       RX packets:3590 errors:0 dropped:0 overruns:0 frame:0
       TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
       collisions:0 txqueuelen:1000
       RX bytes:220883 (215.7 KiB)  TX bytes:2052 (2.0 KiB)
       Interrupt:209 Base address:0xde00

Ping also from a local client to the gateway server.

Ping has started ...

PING 192.168.4.1 (192.168.4.1): 56 data bytes
64 bytes from 192.168.4.1: icmp_seq=0 ttl=64 time=0.338 ms
64 bytes from 192.168.4.1: icmp_seq=1 ttl=64 time=0.244 ms
64 bytes from 192.168.4.1: icmp_seq=2 ttl=64 time=0.230 ms
64 bytes from 192.168.4.1: icmp_seq=3 ttl=64 time=0.227 ms
64 bytes from 192.168.4.1: icmp_seq=4 ttl=64 time=0.215 ms
64 bytes from 192.168.4.1: icmp_seq=5 ttl=64 time=0.230 ms
64 bytes from 192.168.4.1: icmp_seq=6 ttl=64 time=0.388 ms
64 bytes from 192.168.4.1: icmp_seq=7 ttl=64 time=0.217 ms
64 bytes from 192.168.4.1: icmp_seq=8 ttl=64 time=0.214 ms
64 bytes from 192.168.4.1: icmp_seq=9 ttl=64 time=0.186 ms

--- 192.168.4.1 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.186/0.249/0.388/0.060 ms

[haymann]

Don't forget to reset your cable modem between connecting devices to it. Every cable modem that I have used would only give an IP once. It wouldn't explain why you lost the connection in the first place, but be sure to reset it before you plug your server back in to it.

I usually go in this order:

• Shutdown your server
• Unplug the modem power cord
• Wait about 20 seconds
• Plug the modem back in
• Turn on the server

Again, this doesn't explain why you lost connection, but if your modem has given another machine an IP address and has not been reset since, it won't give your server an address when it tries to get one...
Ryan

[turtle2472]

Ok, well I'm still not sure why this mattered, but I rebooted the server and selected a different version during the boot.  Seems there is and option during boot up to select from a menu.  I chose the second down and it now works.  Is there more detail that can be gained from this? 

After selecting the second "listing" of SME it now shows two updates in my software updates. 
nut-client.i386 2.2.0-3.2.el4.sme - smeupdates
nut.i386 2.2.o-3.2.el4.sme - smeupdates

I think I'll be skipping these updates now.

[arne]

From your post above one can see that your external network card had not received an ip adress via the built in dhcp client.
One can also see that your internal network is working fine.

It's a normal and good thing to reboot your server to obtain a new ip adress, by initiating the network card and the dhcp client again.

 

[haymann]

After selecting the second "listing" of SME it now shows two updates in my software updates. 
nut-client.i386 2.2.0-3.2.el4.sme - smeupdates
nut.i386 2.2.o-3.2.el4.sme - smeupdates

I think I'll be skipping these updates now.

Actually if you are using a UPS (at least a USB UPS), you will want to install those right away. If not your server will email you every 5 minutes that it has lost connection w/ the UPS. Didn't take long for me to gain around 600 messages in my inbox from that...

[turtle2472]

From your post above one can see that your external network card had not received an ip adress via the built in dhcp client.
One can also see that your internal network is working fine.

It's a normal and good thing to reboot your server to obtain a new ip adress, by initiating the network card and the dhcp client again.

I have no problem rebooting my system.  In fact I normally install all the updates as soon as I notice they are there and almost always a reboot i required.  I'm not sure what the issue was this time.

Actually if you are using a UPS (at least a USB UPS), you will want to install those right away. If not your server will email you every 5 minutes that it has lost connection w/ the UPS. Didn't take long for me to gain around 600 messages in my inbox from that...

I don't have an UPS USB connected into it even though I know I should.