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

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 usinghome, 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 machineusing 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.8Tracing 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.8Trace complete.C:\Users\huangjie>tracert -d 8.8.8.8Tracing 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.8Trace complete.C:\Users\huangjie>tracert /?Usage: tracert [-d] [-h maximum_hops] [-j host-list] [-w timeout] [-R] [-S srcaddr] [-4] [-6] target_nameOptions: -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.comTracing 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.68Trace complete.C:\Users\huangjie>tracert -w 300 -4 -d www.facebook.comTracing 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.35Trace complete.C:\Users\huangjie>tracert -w 300 -4 -d 114.114.114.114Tracing 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.114Trace complete.C:\Users\huangjie>tracert -w 300 -4 -d 114.114.114.114Tracing 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.114Trace complete.C:\Users\huangjie>tracert /?Usage: tracert [-d] [-h maximum_hops] [-j host-list] [-w timeout] [-R] [-S srcaddr] [-4] [-6] target_nameOptions: -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.

:)

 

Is it normal to get some request timed out in tracert?

I was wondering if it's normal to have some request timed out in tracert.

For example:
C:>tracert www.google.com

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

1 10 ms 5 ms 5 ms 192.168.0.1

2 * * * Request timed out. <--

3 * 70 ms 65 ms 31.55.185.181

4 76 ms 60 ms 101 ms 31.55.185.188

5 64 ms 69 ms 64 ms core2-hu0-12-0-3.colindale.ukcore.bt.net [195.99.127.120]

6 49 ms 42 ms 50 ms peer2-et-3-0-4.slough.ukcore.bt.net [109.159.252.122]

7 111 ms 122 ms 100 ms 109.159.253.69

8 * * * Request timed out. <--

9 61 ms 58 ms 57 ms 108.170.238.116

10 97 ms 93 ms 96 ms 108.170.232.103

11 174 ms 150 ms 122 ms lhr25s11-in-f4.1e100.net [216.58.210.36]

Trace complete.

C:>tracert 1.1.1.1

Tracing route to one.one.one.one [1.1.1.1]
over a maximum of 30 hops:

1 21 ms 7 ms 10 ms 192.168.0.1

2 * * * Request timed out. <--

3 * 65 ms 54 ms 31.55.185.181

4 103 ms 101 ms 102 ms 31.55.185.188

5 50 ms 57 ms 65 ms core1-hu0-15-0-7.colindale.ukcore.bt.net [213.121.192.10]

6 61 ms 62 ms 63 ms peer7-et-3-1-1.telehouse.ukcore.bt.net [109.159.252.164]

7 150 ms 147 ms 214 ms 109.159.253.95

8 88 ms 64 ms 73 ms one.one.one.one [1.1.1.1]

Trace complete.

 

DNS Server not responding problem

I did the tracert.. but all I got was "request timed out" every hop for 30 hops.

 

nokia belle fp2 700 i hop renew update soft

the last version 1130101506 it,s bad there is a problems in the version i request nokia renew update to

version 1130101507 and fix all problems

no exit in camera and the camera pic is bad

the photo editor is not good and we want mark pic to gallary to send more pic together and there is a more problems i hop fixed soon with new version

thanks