Windows 10: Tracert requests all timing out for one specific server

Hey,So I've been having this issue for about 6 months now since I moved to a new address and switched networks from Virgin Media to Sky.The issue is with major packet loss to a specific server 162.249.72.1 This server is for the EU servers of an online game played on this PC and is causing big problems within the game itself causing random stuttering. I have tried with other random servers like google and they all work perfectly.After being in contact with the game's support staff, I tried every fix they showed me and none could solve it, so they suggested I contacted my ISP Sky in this cas

:)

 

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 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?

 

does tracert command have port option

Hi Advaya,

I am Dave, I will help you with this.

The tracert command does not have a switch to specify a port, here is a list of all available switches on that command:

https://learn.microsoft.com/en-us/windows-serve...

 

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.