Aug 3, 2011 - When I set it static I get 'destination host unreachable'. If I put Windows 7 on it instead, it gets an IP address from DHCP and can access the.
I have a PC on my network. It is configured with a static IP address, 192.168.1.110. It is connected via LAN cable directly to my router with IP address 192.168.1.1.
The PC's gateway is set to the router's IP address.From another PC, IP address 192.168.1.2, also connected to the router over LAN, I am unable to ping 192.168.1.110 (destination host unreachable). I am also unable to remote into it.From my Android phone, using Microsoft Remote Desktop, and with the phone connected to the router via WiFi, I am able to remote into 192.168.1.110. Here is a screengrab from my phone:When I open my router's status page, I see the target PC's MAC address on the clients tab three times: Once under Active Clients, with the expected static IP address, and twice unexpectedly under the dynamic clients tab, with different IP addresses, even though the PC is not configured to use DHCP:What is going on here that I can't reach.110 from.2?EDIT: I am also unable to ping or remote into the two dynamic addresses,.127 and.128.EDIT 2: Additional info.
Well, since it says destination host unreachable, its is likely that the problem is on the.2 host, rather than the.110 host. What does its routing table look like, does it have a default gateway set, and is its subnet mask the same? Disregard the DHCP page on your router, its just telling you that that mac has previously had a DHCP lease.
Most of the time, a dhcp server is not made aware that a host is offline or switched to static, since the host never tells the server about the change so the server just displays the old lease. Also adjust your dhcp pool to exclude the static IP (.110).–Oct 20 '16 at 14:21. The fact that the MAC address associated with IP address 192.168.1.110 via a static configuration is ALSO is associated with, not just one, but, two, DHCP-assigned IP addresses cannot be overlooked. Unless the device at 110 has three NICs legitimately holding the three IP addresses (.110,.127 and.128) then there is a form of route cache poisoning in effect. Although it is difficult to say exactly why your ping attempt is returning a destination host unreachable, it is not entirely unexpected considering the router's uncertainty concerning the MAC hardware's true IP assignment. Therefore by deleting those two erroneous DHCP leases (or otherwise eliminating them from the router's view as you did when you transferred the IP entry to the other router) you should be able to restore normal ICMP (ping) visibility between the two machines (.2 and.110). Remember, unless the device has multiple ethernet interfaces, there should be a one-to-one correspondence between the MAC address and the IP address.
Destination Host Unreachable Ping Solution
Ensuring this should clear up the problem.
Cara Mengatasi Destination Host Unreachable Speedy
I have a weird issue.I think.I just noticed that on my servers (all HP and setup by someone else), if I would ping an IP address of a downed machine or an IP not in use all in the same subnet, I get a message of 'Reply from 10.10.10.20: Destination host unreachable and the server IPthat I am pinging from is the 10.10.10.20.From my experience, I should be getting a 'request timed out message' only if it's on the same subnet. Anyone know why I'm getting the Destination host unreachable message when I'm not trying to reach a different subnet and why is it coming from mymachine? The response 'Reply from 10.10.10.20: Destination host unreachable.' Actually is the correct one. When pinging a host on your own subnet the sender will first send an ARP request for the MAC address of the associated IP address. Sincethe host does not exist, the sending station is reporting to you that the destination host is unreachable because the ARP request was not completed.
The actual ICMP echo was never sent which is why you aren't getting a 'request timed out' message.You can't send a layer 3 packet if you can't resolve the layer 2 address of the host (or the gateway if the destination is on another network).The reason why you would not get this same message if you were pinging hosts on a different subnet is that the sender would ARP for the gateway address since the target is on a different subnet. The ARP completes properly and the ICMP echo is sentbut the timeout value is reached since the destination host never responded with an echo-reply.It seems that Win7/2008 just gives more specific failure reasons now than Windows XP does. This is a good thing in my estimation.Matt W. CCNP, CCDA, CCNA-S, RHCT, MCSE, MCSA, MCP+I, A+. I verified that the default gatway is correct but it still shouldn't matter because the traffic is local to the subnet.Here's the output for the route print command. The response 'Reply from 10.10.10.20: Destination host unreachable.' Actually is the correct one.
When pinging a host on your own subnet the sender will first send an ARP request for the MAC address of the associated IP address. Sincethe host does not exist, the sending station is reporting to you that the destination host is unreachable because the ARP request was not completed.
The actual ICMP echo was never sent which is why you aren't getting a 'request timed out' message.You can't send a layer 3 packet if you can't resolve the layer 2 address of the host (or the gateway if the destination is on another network).The reason why you would not get this same message if you were pinging hosts on a different subnet is that the sender would ARP for the gateway address since the target is on a different subnet. The ARP completes properly and the ICMP echo is sentbut the timeout value is reached since the destination host never responded with an echo-reply.It seems that Win7/2008 just gives more specific failure reasons now than Windows XP does. This is a good thing in my estimation.Matt W.
CCNP, CCDA, CCNA-S, RHCT, MCSE, MCSA, MCP+I, A+. I had a different situation that I 'THOUGHT' was windows 2008 related. Turns out that the virtual machines I was using were not being given UNIQUE MAC addresses. It was the comments above about ARP that made me realize what was happening.I made manual settings and then PING started working because ARP could do its job.Oddly enough.
RDP worked to each of these virtual machines but that traffice went through a gateway and thus the local subnet didn't seem to be an issue.Just thought I would share.Monitoring is the art of looking for something you don't want to find. Hi,I'm having the same issue (Destination host unreachable) when trying to ping an internal platform I need to access. Thing is, I'm using Windows 7's, Windows XPMode (ie.
Virtual machine). It's strange because I CAN ping the SAME IP address frommy host machine (ie. Windows 7 OS) but get this issue when trying to ping from the XP mode (ie. Virtual machine) only.Any ideas guys?PS - I NEED to be able to contact the platform from XP Mode because the test case I am trying to run does NOT operate on Win 7.