Destination host unreachable windows 7#
Destination host unreachable mac#

Windows 7 seems rather conflicted to me about the situation :). Reply from nnn.mmm.75.131: Destination host unreachable. If 'destination host unreachable' is 'correct' how do you explain this from running a ping to a machine being rebooted on the same segment from a Windows 7 machine? Network Address Netmask Gateway Address Metric Disregard the IP that was in the first post. Here's the output for the route print command. I verified that the default gatway is correct but it still shouldn't matter because the traffic is local to the subnet.

CCNP, CCDA, CCNA-S, RHCT, MCSE, MCSA, MCP+I, A+ It seems that Win7/2008 just gives more specific failure reasons now than Windows XP does. The ARP completes properly and the ICMP echo is sentīut the timeout value is reached since the destination host never responded with an echo-reply. 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. 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 actual ICMP echo was never sent which is why you aren't getting a 'request timed out' message. The host does not exist, the sending station is reporting to you that the destination host is unreachable because the ARP request was not completed.

Destination host unreachable mac#

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. The response 'Reply from 10.10.10.20: Destination host unreachable.' actually is the correct one.