tracert shows request time out for all the hops except the last hop.

Anonymous
2020-06-29T11:29:27+00:00

tracert shows request time out for all the hops except the last hop no matter what hostname/ip I am tracing and what kind of network I am using(home, corpnetwork, vpn.) and which city I am in. Ping works fine. They all use ICMP .

When I try to capture the packets of the tracert process, I CAN see the ip address of the hops tracert was going though. And traceroute command works fine on my Linux virtual machine(using Hyper-V).

I had tried to reset my computer network, but it is not working. 

Please, anyone has any clues about this issue?

C:\Users\huangjie>tracert -d 8.8.8.8

Tracing route to 8.8.8.8 over a maximum of 30 hops

  1     *        *        *     Request timed out.
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *      155 ms   136 ms  8.8.8.8

Trace complete.

C:\Users\huangjie>tracert -d 8.8.8.8

Tracing route to 8.8.8.8 over a maximum of 30 hops

  1     *        *        *     Request timed out.
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11   161 ms   155 ms   152 ms  8.8.8.8

Trace complete.

C:\Users\huangjie>tracert /?

Usage: tracert [-d] [-h maximum_hops] [-j host-list] [-w timeout]
               [-R] [-S srcaddr] [-4] [-6] target_name

Options:
    -d                 Do not resolve addresses to hostnames.
    -h maximum_hops    Maximum number of hops to search for target.
    -j host-list       Loose source route along host-list (IPv4-only).
    -w timeout         Wait timeout milliseconds for each reply.
    -R                 Trace round-trip path (IPv6-only).
    -S srcaddr         Source address to use (IPv6-only).
    -4                 Force using IPv4.
    -6                 Force using IPv6.

C:\Users\huangjie>tracert -w 300 -4 -d www.google.com

Tracing route to www.google.com [172.217.24.68]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14   157 ms   142 ms   159 ms  172.217.24.68

Trace complete.

C:\Users\huangjie>tracert -w 300 -4 -d www.facebook.com

Tracing route to star-mini.c10r.facebook.com [31.13.66.35]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15   400 ms     *      350 ms  31.13.66.35

Trace complete.

C:\Users\huangjie>tracert -w 300 -4 -d 114.114.114.114

Tracing route to 114.114.114.114 over a maximum of 30 hops

  1     *        *        *     Request timed out.
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9    55 ms    50 ms    45 ms  114.114.114.114

Trace complete.

C:\Users\huangjie>tracert -w 300 -4 -d 114.114.114.114

Tracing route to 114.114.114.114 over a maximum of 30 hops

  1     *        *        *     Request timed out.
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9    56 ms    45 ms    40 ms  114.114.114.114

Trace complete.

C:\Users\huangjie>tracert /?

Usage: tracert [-d] [-h maximum_hops] [-j host-list] [-w timeout]
               [-R] [-S srcaddr] [-4] [-6] target_name

Options:
    -d                 Do not resolve addresses to hostnames.
    -h maximum_hops    Maximum number of hops to search for target.
    -j host-list       Loose source route along host-list (IPv4-only).
    -w timeout         Wait timeout milliseconds for each reply.
    -R                 Trace round-trip path (IPv6-only).
    -S srcaddr         Source address to use (IPv6-only).
    -4                 Force using IPv4.
    -6                 Force using IPv6.

Windows for home | Windows 10 | Internet and connectivity

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

7 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Sjaak Ketting 7,635 Reputation points
    2020-06-29T13:12:46+00:00

    Hallo August,

    Traceroute request timed out? Why traceroute is broken

    https://community.spiceworks.com/networking/articles/2531-traceroute-request-timed-out-why-traceroute-is-broken

    Mabey the article can help you any further.

    Best Regards,

    Jacquito.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments
  2. Anonymous
    2020-06-29T12:50:32+00:00

    Hello August,

    Thank you for reaching out. I am Harun an Independent Advisor and Microsoft User. I will gladly help you out.

    It is possible that you have a firewall configuration issue that prevents the packets from either getting out or getting back.

    Try again turning off your firewall (temporarily!). The other option is that your ISP may drop ICMP traffic as a matter of course, or only when they are busy with other traffic.

    ICMP (the protocol used by traceroute) is of the lowest priority, and when higher priority traffic is ongoing the router may be configured to simply drop ICMP packets. There is also the possibility that the ISP drops all ICMP packets as a matter of security since many DOS (Denial of Service) attacks are based on probing done with ICMP packets.

    Please feel free to ask for more Information and let me know if this helps.

    Sincerely

    Independent Advisor

    Harun

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments
  3. Anonymous
    2020-07-01T12:54:29+00:00

    The part with firewalls is that it can be set to let packets in but not out or vise versa, sometimes even both but still the PC will forward the tracert to the next destination. So all the midway stations can have a firewall set to not let tracert call return with info.

    Sincerely

    Independent Advisor
    Harun i

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  4. Anonymous
    2020-06-30T03:41:00+00:00

    Thank you Jacquito.

    I took a quick look at the url you shared. And I find something I really interested in, which is a tcp based trace route. I suppose it will work for me sometimes. But I dont know is there any software tools providing this function.  From the comments I see a linux command line tool "tcptraceroute", but I am on Windows.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  5. Anonymous
    2020-06-30T03:33:38+00:00

    Thank you Harun for your advice. 

    If the firewall blocked the traffic, why it is not blocking Wireshark because wireshark captured the packets and i can see the IPs of all of the middle hops as you can see in the screenshot.

    As for the ISP blocking, I can trace without issue using mobile phone connected to the same Wifi or my colleagues can trace when we are in office and connected to the same wifi.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments