Reply from <ip address>: Destination host unreachable.

kwatts59 · 06-10-2014, 06:25 PM

When I try to ping my server (131.216.46.60) from the dos command prompt I get "destination host unreachable". But when I ping my other server (131.216.46.121) it works fine. Below are the messages:

Code:

C:\Users\Ken>ping 131.216.46.60
Pinging 131.216.46.60 with 32 bytes of data:
Reply from 131.216.46.66: Destination host unreachable.
Reply from 131.216.46.66: Destination host unreachable.
Reply from 131.216.46.66: Destination host unreachable.
Reply from 131.216.46.66: Destination host unreachable.
Ping statistics for 131.216.46.60:
  Packets sent = 4, Received = 4, Lost = 0 (0% loss),

C:\Users\Ken>ping 131.216.46.121
Pinging 131.216.46.121 with 32 bytes of data:
Reply from 131.216.46.121: bytes=32 time=2ms TTL=64
Reply from 131.216.46.121: bytes=32 time<1ms TTL=64
Reply from 131.216.46.121: bytes=32 time<1ms TTL=64
Reply from 131.216.46.121: bytes=32 time<1ms TTL=64
Ping statistics for 131.216.46.121:
  Packets sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
  Minimum = 0ms, maximum = 2ms, Average = 0ms

I also cannot access 131.216.46.60 from my PC via Navicat or my terminal software. It was working fine earlier today but I disconnected my Dlink DES-1005E switch to test a printer problem. 131.216.46.60 and my PC are connected to this switch but 131.216.46.121 is not. I can access the internet from my PC, but I cannot access the internet from the 131.216.46.60 console.
Any advice on how to get this server to respond would be great.

frankbell · 06-10-2014, 07:48 PM

I duplicated the problem from here.

Is it physically possible to swap the cables between 131.216.46.121 and 131.216.46.60? That would be the quickest way to determine whether the issue lies in 131.216.46.60 or between it and the gateway. In a situation such as this, testing the hardware first can be very helpful, as no amount of software troubleshooting can fix a broken component.

Not knowing the geography of your system, it's difficult to speak other than generally, but here are some ideas:

Rule out the uplink from the switch by hooking a computer directly to it long enough to test from there. If the uplink is good, then

Rule out the switch by swapping it in place with a known-good switch, if the switch is good, then

Rule out the cabling from 131.216.46.60 to the switch replacing it with a known-good stretch of cable long enough to test the connection. (And so on.)

If all the components from the computer to the gateway test as valid, check the ethernet card in the computer.

kwatts59 · 06-10-2014, 08:46 PM

Thank you for your quick response. An excellent suggestion frankbell.

My Dlink DES-1005E switch has 5 ports on it. The configuration is as follows:
port 1 is connected to a wire that goes into the wall
port 2 is empty
port 3 is connected to the server 131.216.46.60
port 4 is connected to a printer that I can't get working but that's a different matter
port 5 is connected to my PC

I swapped the wires going into port 3 and port 5.
When I ping from my PC, the results are the same.
I can ping 131.216.46.121 but I cannot ping 131.216.46.60 and I still can access the internet from my PC.
I did some additional swapping and no matter how I swap the wires, there is no change.
This rules out a problem with the ports.

The server 131.216.46.121 is in another room. I am not able to switch the wire with my other server right now.
Is there anything else I can try?

jefro · 06-10-2014, 08:51 PM

Find out why .60 doesn't seem to be connected to anything. The place to start is the switch area.

kwatts59 · 06-11-2014, 01:19 PM

Problem resolved!

I typed the following command on the server and it resolved the problem

Code:

$ sudo dhclient -v eth2

Thanks all for your help.

jefro · 06-11-2014, 03:42 PM

Good job, thanks for the update and solution.

frankbell · 06-11-2014, 07:41 PM

Glad you're back up!