Destination host unreachable.
No path to the host could be found
Seen in Windows ping, Linux ping (Destination Host Unreachable), tracert
A router, or your own machine, reported that it could not deliver packets to that host.
Common causes
- On the local subnet, the host did not answer ARP: it is off, disconnected or has a different address.
- A router has no route to the destination network (shown as "Destination net unreachable").
- A wrong subnet mask or gateway on your machine sends traffic the wrong way.
How to fix it
- Look at who replied: "Reply from <your own IP>" means the problem is local (ARP or routing), while a router's IP points to a problem further along.
- Check the target is powered on and on the expected address, and check `arp -a` for its entry.
- Verify your IP, subnet mask and default gateway with `ipconfig` or `ip addr` and `ip route`.
Got a different message? Paste it into the error explainer.
Related errors
- Broken pipe · Wrote to a connection or pipe that was already closed
- Software caused connection abort · Your own system aborted the connection
- TTL expired in transit. · Packets ran out of hops before arriving
- PING: transmit failed. General failure. · Windows could not send the ping at all
- Packet needs to be fragmented but DF set. · The packet is bigger than the path MTU
- ECONNREFUSED · Connection refused
- ETIMEDOUT · Connection timed out
- ECONNRESET · Connection reset by peer
- EHOSTUNREACH · No route to host
- getaddrinfo ENOTFOUND · The hostname doesn't exist in DNS
- getaddrinfo EAI_AGAIN · Temporary DNS failure
- ENETUNREACH · Network is unreachable