Linux - Networking This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
06-10-2014, 07:25 PM
|
#1
|
Member
Registered: Aug 2012
Posts: 34
Rep:
|
Reply from <ip address>: Destination host unreachable.
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.
|
|
|
06-10-2014, 08:48 PM
|
#2
|
LQ Guru
Registered: Jan 2006
Location: Virginia, USA
Distribution: Slackware, Ubuntu MATE, Mageia, and whatever VMs I happen to be playing with
Posts: 19,622
|
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.
Last edited by frankbell; 06-10-2014 at 08:49 PM.
|
|
|
06-10-2014, 09:46 PM
|
#3
|
Member
Registered: Aug 2012
Posts: 34
Original Poster
Rep:
|
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?
|
|
|
06-10-2014, 09:51 PM
|
#4
|
Moderator
Registered: Mar 2008
Posts: 22,144
|
Find out why .60 doesn't seem to be connected to anything. The place to start is the switch area.
|
|
|
06-11-2014, 02:19 PM
|
#5
|
Member
Registered: Aug 2012
Posts: 34
Original Poster
Rep:
|
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.
|
|
|
06-11-2014, 04:42 PM
|
#6
|
Moderator
Registered: Mar 2008
Posts: 22,144
|
Good job, thanks for the update and solution.
|
|
|
06-11-2014, 08:41 PM
|
#7
|
LQ Guru
Registered: Jan 2006
Location: Virginia, USA
Distribution: Slackware, Ubuntu MATE, Mageia, and whatever VMs I happen to be playing with
Posts: 19,622
|
Glad you're back up!
|
|
|
All times are GMT -5. The time now is 08:02 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|