Skip to main content

How to Solve Destination Net Unreachable - Ping Error Message

Destination Net Unreachable is one of the common ICMP error messages when you ping to a remote address. This tutorial explains the meaning of the ICMP error message Destination Net Unreachable and teaches how to fix it. The first part of this tutorial explains why do you receive Destinationation Net Unreachable error while you ping a web address. The second part of the tutorial explains how to solve this error. Let us check what does the error message means?

What is The Meaning of Destination Net Unreachable Message?
This error message tells the ping request from your computer failed to find the route to the destination network.


Reasons for the ICMP echo Destination net unreachable
The ping packet couldn't find the destination network due to any one of the following reasons.
  • Packet Routing issue
  • Destination network path might be down
  • An outdated Routing table on the default gateway with no route to the destination


Technical Explanation of Destination Net Unreachable
When you ping to an IP address from your computer, ping packet goes to the default gateway. The default gateway will send the ping packet to the destination address.

However, if the default gateway does not know the path to the desired network, your computer will get a Destination Net Unreachable message.

Have a look at the screenshot I uploaded below. I send ping packets to the global DNS address 4.2.2.2 from your computer.

However, the process went wrong, and the ping error Destination net unreachable is on the command prompt.
How to solve Destination Net Unreachable

I will explain why I have received the reply from the IP address 192.168.42.129 when I send ping packets to 4.2.2.2.

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\sijugk>ping 4.2.2.2

Pinging 4.2.2.2 with 32 bytes of data:
Reply from 192.168.42.129: Destination net unreachable.
Reply from 192.168.42.129: Destination net unreachable.
Reply from 192.168.42.129: Destination net unreachable.
Reply from 192.168.42.129: Destination net unreachable.

Ping statistics for 4.2.2.2:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

C:\Users\sijugk>

Here I pinged to the address 4.2.2.2 from my computer. The ping request went to the default gateway.

In my network, Modem is the default gateway and its IP address is192.168.42.129.

Modem failed to find a route to the destination network and replied to my computer with the Destination net unreachable message.



How to troubleshoot the error Destination net unreachable
If you see the Destination net unreachable error message on your device, I suggest you perform the steps mentioned below.

  1. Power Cycle Modem:
    I don't think it is a standard solution, but it worked for me. If the reason for getting the error is the outdated routing table on the default gateway, a power cycle can refresh it. To learn how to do it, click on the link below.
    How to Power Cycle a Modem

  2. Check the local host configuration on your computer

  3. Disconnect and reconnect the connection to the default gateway

  4. Disable Firewall and check for the issue

  5. Refresh routing table information and ping again

I hope this tutorial has helped you to resolve Destination net unreachable ICMP Error on your computer.

CoreNetworkZ has many tutorials covering similar ICMP error messages. Some of the are below.

  1. ICMP Error Request Timed Out

  2. ICMP Error Destination Host Unreachable

Comments

Nice explanation...

http://sankar-information-security.blogspot.com/
Siju George said…
Thanks for your comment.
Anonymous said…
Hi.. Can you please help me to configure my router. It's TP Link WR740N Every time i use my router and ping the default gateway. it says Destination net unreachable. Im using a Broadband Connection. Please help me. Thanks..
Admin said…
I recommend you to perform a power cycle on your modem and router.

http://www.corenetworkz.com/how-to-perform-power-cycle-power-cycle.html
Anonymous said…
If pinging a FQDN which resolves to an ip (a.a.a.a), why then would the ping results show a different reply ip address (b.b.b.b) with "destination net unreachable"?

This also happens when I try pinging the resolved ip (a.a.a.a) directly, it replies from the ip (b.b.b.b) address with result "destination net unreachable"..

BUT, if I ping the ip address (b.b.b.b) directly, I get a good response..

*scratches head confused*
Alex George said…
@Anonymous

It is exactly the way Destination Net Unreachable works. In your scenario you ping a.a.a.a

(say an external IP address like 8.8.8.8)

Here b.b.b.b is the gateway address (like 192.168.1.1)

If the gateway does not know route to the external ip address a.a.a.a , you will get destination net unreachable error message from gateway address (b.b.b.b).
Time Warner email started having a stroke, and I did a PING which resulted in, "Request timed out." I did a TRACERT which resulted in, "13 * * 75.180.131.161 reports: Destination net unreachable." A cold reboot of modem and router did no good. A chat with TW blamed my Outlook, which I interpret as the old Down The Primrose Path treatment. So, with no Network Status Information from TW, what would be my next step for concrete answers? I'm contemplating going to ARIN with the last IP and calling the results, except they may be the NSA.
Alex said…
With no network status information from Time Warner means, do you have issues with connecting to Internet ? Could you give more information about the issue ?