Tracert requests all timing out for one specific server

Question

Tracert requests all timing out for one specific server

Kyle Grady 0

Hey,

I was recommended this forum from the official microsoft forums -

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 case) Which I have done but they can see no issues at all and are 'looking into it' for the foreseeable which makes sense since every other part of the network and all internet connections are brilliant and stable.

The control I'm using to test this bug is the tracert command, now over the 30 hops it tests, only 1, 2 and 5 work every time without fail, every single other hop is shown a 'request timed out' even with the wait time before a ping timeout increased to 10 seconds.

Results below:

I am completely stuffed with what to do as I believe I have tried everything.

Attempted fixes:

Miscellaneous fixes such as mouse polling rate adjustments / In-game settings etc.

Updating all possible drivers including graphics, network drivers etc.

Deleting and re-installing all associated programs with the game using RevoUninstaller to ensure all registry items are deleted too.

sfc /scannow (no issues)

Network reset

IP reset / refresh

Changing DNS settings around

Changing configuration from IPv6 to IPv4 and back

Adding exceptions for all game services into antivirus/firewall settings

Port forwarding

Changing ethernet ports used from router

Enabling Inbound/outbound rules on firewall settings page relating to ICMP echo requests

Completely resetting PC

Reverting windows updates / using a previous system restore from when it was working

Changing protocol to WPA2 and back

I have changed absolutely nothing from my last address apart from the network provider, and in every other aspect the internet is brilliant, even in game there is no packet loss shown or connectivity issues indicated and the bug can only be seen when the game is being played with random stuttering. It seems to be an issue with only my PC too, not the server itself as millions connect and use it every day with no issues.

Now I am really no advanced user / developer at all but I have tried every tutorial/video/blog I can find for any advice and I am really hoping someone here can guide me into any sort of reason why just this one server won't connect as it's driving me nuts..

(And it is also stopping / has stopped me playing this game I enjoy for the last 6 months!)

1 answer

Your answer

Answer 1

Geoff McKenzie 865

Hi Kyle,

You will get limited value from tools like Tracert and ping in this situation. Many internet routers, gateways, etc. block/drop ICMP for security and performance reasons. You may be better off with some sort of TCP ping tool. Test-NetConnection in powershell is a basic one but there are options that will give you ping.exe like output for a tcp connection.

However, for your situation I would start with a simpler test (assuming it is 'simpler' in your circumstances).
If you have a relative or friend who plays the same game and uses the same server at their home and do not have any issues, then, invite them over, have them plug in to your network and see if they have the same problem.
If they do then it may be something environmental (to do with your location or network).
If they don't then it may be something to do with your machine or configuration.
Eitherway, you will know where to focus your investigation.

Good luck

Kyle Grady 0 Reputation points

2025-03-13T16:32:26.4866667+00:00

Hey Geoff, thanks for the reply,

I don't have anyone I can bring round to test this unfortunately, I have tried test-netconnection in powershell also to no avail as per image.

failed with timed out status.

I'm in the realms now of having no clue where else to look within my machine or configuration as this is beyond my technical knowledge by a landslide...
Geoff McKenzie 865 Reputation points

2025-03-13T22:24:07.3166667+00:00

Hi Kyle,

It looks like Riot Games has some tools and guides which may help - I am assuming riot games based on an IP lookup.

Have a look at these URLs - again assuming it is riot games.

https://support-leagueoflegends.riotgames.com/hc/en-us?rg_ref=supportLP&utm_source=support.riotgames.com&utm_medium=referral&utm_term=https%3A%2F%2Fsupport.riotgames.com%2Fhc%2Fen-us

https://support-leagueoflegends.riotgames.com/hc/en-us/articles/201752664-Basic-Connections-Troubleshooting-Guide

https://support-leagueoflegends.riotgames.com/hc/en-us/articles/4407290569747-Advanced-Connections-Troubleshooting-Guide

https://support-leagueoflegends.riotgames.com/hc/en-us/articles/201752674-Network-System-and-League-of-Legends-Logs#wq4

Each page has instructions and links to instruction which may help.

I note that the pages also tell you about riot client logs which may be very revealing,

I don't use any Riot software so I cannot check the contents to see if they are actually helpful but it is a good place to start.

Good luck
Kyle Grady 0 Reputation points

2025-03-14T16:05:37.1366667+00:00

Hey,

Thanks for the advice,

I have already went through all of these menus with the Riot support team through a few tickets etc, used the ping plotter tool and provided riot with all logs to no avail, tried Riot's Repair Tool also to no avail.

In the end they told me to contact my ISP to resolve the issue a they couldn't see any issues with it.

Now my ISP has no clue what's causing the issue either so I'm rather stuck.. however I will keep trying, all problems must have a solution right?

K
MotoX80 36,401 Reputation points

2025-03-14T17:38:27.7533333+00:00
I don't know how they have their network configured, but from my experience the "dot one" address is normally the gateway.

Launch your game and then open a command prompt and run this. What do you get back?

netstat -aon | findstr 162.249.72

My thought would be to use Powershell to test network connectivity to the game server and also another well known internet address periodically to see if you lose all connectivity or if it's just that one address.

I want to verify the IP and get the port number that you're connecting to.

Do they use a VPN? Would they block all access from the US?
Kyle Grady 0 Reputation points

2025-03-15T09:52:18.18+00:00

Hi,

Thank you for the reply ☺

I ran the netstat -aon cmd, the findstr 162.249.72 isn't showing anything however..

Does this mean that the 162.249.72 server isn't actually what I'm connecting to? Would it be one of these servers causing the stuttering issue?

I am connecting from the UK to the servers which I believe are all based in the US but millions connect from here also so highly unlikely that is the issue if it's only affecting me.

The results are below:

C:\Windows\System32>netstat -aon

Active Connections

Proto Local Address Foreign Address State PID

TCP 0.0.0.0:135 0.0.0.0:0 LISTENING 1544

TCP 0.0.0.0:445 0.0.0.0:0 LISTENING 4

TCP 0.0.0.0:5040 0.0.0.0:0 LISTENING 8216

TCP 0.0.0.0:5357 0.0.0.0:0 LISTENING 4

TCP 0.0.0.0:7680 0.0.0.0:0 LISTENING 14684

TCP 0.0.0.0:49664 0.0.0.0:0 LISTENING 1208

TCP 0.0.0.0:49665 0.0.0.0:0 LISTENING 1124

TCP 0.0.0.0:49666 0.0.0.0:0 LISTENING 1940

TCP 0.0.0.0:49667 0.0.0.0:0 LISTENING 2656

TCP 0.0.0.0:49668 0.0.0.0:0 LISTENING 4132

TCP 0.0.0.0:49669 0.0.0.0:0 LISTENING 1200

TCP 0.0.0.0:52270 0.0.0.0:0 LISTENING 8344

TCP 127.0.0.1:9010 0.0.0.0:0 LISTENING 14104

TCP 127.0.0.1:9010 127.0.0.1:49773 ESTABLISHED 14104

TCP 127.0.0.1:9080 0.0.0.0:0 LISTENING 14104

TCP 127.0.0.1:9100 0.0.0.0:0 LISTENING 4720

TCP 127.0.0.1:9100 127.0.0.1:49787 ESTABLISHED 4720

TCP 127.0.0.1:9180 0.0.0.0:0 LISTENING 4720

TCP 127.0.0.1:15292 0.0.0.0:0 LISTENING 12468

TCP 127.0.0.1:15393 0.0.0.0:0 LISTENING 12468

TCP 127.0.0.1:16494 0.0.0.0:0 LISTENING 12468

TCP 127.0.0.1:45654 0.0.0.0:0 LISTENING 14104

TCP 127.0.0.1:49773 127.0.0.1:9010 ESTABLISHED 14036

TCP 127.0.0.1:49787 127.0.0.1:9100 ESTABLISHED 14104

TCP 127.0.0.1:52216 0.0.0.0:0 LISTENING 1724

TCP 127.0.0.1:52216 127.0.0.1:52274 ESTABLISHED 1724

TCP 127.0.0.1:52216 127.0.0.1:52290 ESTABLISHED 1724

TCP 127.0.0.1:52216 127.0.0.1:52291 ESTABLISHED 1724

TCP 127.0.0.1:52216 127.0.0.1:53911 ESTABLISHED 1724

TCP 127.0.0.1:52274 127.0.0.1:52216 ESTABLISHED 8344

TCP 127.0.0.1:52290 127.0.0.1:52216 ESTABLISHED 1796

TCP 127.0.0.1:52291 127.0.0.1:52216 ESTABLISHED 1796

TCP 127.0.0.1:53911 127.0.0.1:52216 ESTABLISHED 14128

TCP 127.0.0.1:54098 127.0.0.1:28194 SYN_SENT 14104

TCP 127.0.0.1:54100 127.0.0.1:6469 SYN_SENT 14104

TCP 192.168.0.222:139 0.0.0.0:0 LISTENING 4

TCP 192.168.0.222:49754 104.18.41.183:443 ESTABLISHED 1724

TCP 192.168.0.222:51750 52.209.121.172:443 ESTABLISHED 17376

TCP 192.168.0.222:52374 172.65.252.238:5223 ESTABLISHED 1724

TCP 192.168.0.222:52384 143.204.176.64:443 CLOSE_WAIT 12132

TCP 192.168.0.222:52614 172.65.252.238:5223 ESTABLISHED 14128

TCP 192.168.0.222:52616 104.18.40.25:443 ESTABLISHED 14128

TCP 192.168.0.222:52619 104.18.34.210:443 ESTABLISHED 14128

TCP 192.168.0.222:52645 143.204.176.24:443 CLOSE_WAIT 12132

TCP 192.168.0.222:52825 172.64.147.231:443 ESTABLISHED 1724

TCP 192.168.0.222:52875 3.216.172.79:443 ESTABLISHED 17376

TCP 192.168.0.222:53082 104.18.41.183:443 ESTABLISHED 1724

TCP 192.168.0.222:53113 52.97.129.242:443 FIN_WAIT_1 10036

TCP 192.168.0.222:53384 52.168.117.170:443 TIME_WAIT 0

TCP 192.168.0.222:53771 199.232.208.194:443 ESTABLISHED 11864

TCP 192.168.0.222:53772 3.166.67.176:443 ESTABLISHED 11864

TCP 192.168.0.222:53782 34.36.151.3:443 ESTABLISHED 11864

TCP 192.168.0.222:53787 130.211.23.194:443 TIME_WAIT 0

TCP 192.168.0.222:53790 142.250.178.2:443 ESTABLISHED 11864

TCP 192.168.0.222:53809 74.120.189.195:443 TIME_WAIT 0

TCP 192.168.0.222:53820 3.124.64.248:443 ESTABLISHED 11864

TCP 192.168.0.222:53821 143.244.197.139:443 ESTABLISHED 11864

TCP 192.168.0.222:53824 103.231.98.76:443 ESTABLISHED 11864

TCP 192.168.0.222:53825 35.227.252.103:443 TIME_WAIT 0

TCP 192.168.0.222:53827 13.74.129.92:443 TIME_WAIT 0

TCP 192.168.0.222:53860 18.165.242.110:443 ESTABLISHED 11864

TCP 192.168.0.222:53861 34.198.128.205:443 TIME_WAIT 0

TCP 192.168.0.222:53867 20.50.201.205:443 TIME_WAIT 0

TCP 192.168.0.222:53872 34.1.242.226:443 ESTABLISHED 11864

TCP 192.168.0.222:53914 104.18.34.210:443 TIME_WAIT 0

TCP 192.168.0.222:53933 104.16.55.40:443 ESTABLISHED 14128

TCP 192.168.0.222:53943 104.18.34.210:443 TIME_WAIT 0

TCP 192.168.0.222:53947 188.42.95.245:443 ESTABLISHED 14128

TCP 192.168.0.222:53964 104.18.34.210:443 ESTABLISHED 14128

TCP 192.168.0.222:53966 52.105.47.39:443 TIME_WAIT 0

TCP 192.168.0.222:53986 172.64.153.46:443 ESTABLISHED 14128

TCP 192.168.0.222:53992 104.16.55.40:443 ESTABLISHED 14128

TCP 192.168.0.222:53993 8.8.8.8:53 TIME_WAIT 0

TCP 192.168.0.222:54006 8.8.8.8:53 TIME_WAIT 0

TCP 192.168.0.222:54015 8.8.8.8:53 TIME_WAIT 0

TCP 192.168.0.222:54024 8.8.8.8:53 TIME_WAIT 0

TCP 192.168.0.222:54027 104.18.41.168:8443 TIME_WAIT 0

TCP 192.168.0.222:54034 8.8.8.8:53 TIME_WAIT 0

TCP 192.168.0.222:54042 8.8.8.8:53 TIME_WAIT 0

TCP 192.168.0.222:54050 8.8.8.8:53 TIME_WAIT 0

TCP 192.168.0.222:54057 8.8.8.8:53 TIME_WAIT 0

TCP 192.168.0.222:54065 8.8.8.8:53 TIME_WAIT 0

TCP 192.168.0.222:54073 8.8.8.8:53 TIME_WAIT 0

TCP 192.168.0.222:54080 8.8.8.8:53 TIME_WAIT 0

TCP 192.168.0.222:54086 52.97.129.242:443 ESTABLISHED 10036

TCP 192.168.0.222:54093 52.178.17.233:443 ESTABLISHED 10036

TCP 192.168.0.222:54099 8.8.8.8:53 TIME_WAIT 0

TCP [::]:135 [::]:0 LISTENING 1544

TCP [::]:445 [::]:0 LISTENING 4

TCP [::]:5357 [::]:0 LISTENING 4

TCP [::]:7680 [::]:0 LISTENING 14684

TCP [::]:49664 [::]:0 LISTENING 1208

TCP [::]:49665 [::]:0 LISTENING 1124

TCP [::]:49666 [::]:0 LISTENING 1940

TCP [::]:49667 [::]:0 LISTENING 2656

TCP [::]:49668 [::]:0 LISTENING 4132

TCP [::]:49669 [::]:0 LISTENING 1200

TCP [::]:52270 [::]:0 LISTENING 8344

TCP [2a06:5906:33c0:2a00:c0b3:b7db:b78c:3f19]:49699 [2603:1020:705:8::402]:443 ESTABLISHED 4672

TCP [2a06:5906:33c0:2a00:c0b3:b7db:b78c:3f19]:49913 [2603:1020:705:8::402]:443 ESTABLISHED 17272

TCP [2a06:5906:33c0:2a00:c0b3:b7db:b78c:3f19]:50142 [2a00:1450:400c:c0d::bc]:5228 ESTABLISHED 11864

TCP [2a06:5906:33c0:2a00:c0b3:b7db:b78c:3f19]:52304 [2606:4700::6811:ad05]:443 TIME_WAIT 0

TCP [2a06:5906:33c0:2a00:c0b3:b7db:b78c:3f19]:53112 [2a02:26f0:fd00:8::58dd:78d7]:443 LAST_ACK 10036

TCP [2a06:5906:33c0:2a00:c0b3:b7db:b78c:3f19]:53363 [2606:4700::6811:ad05]:443 TIME_WAIT 0

TCP [2a06:5906:33c0:2a00:c0b3:b7db:b78c:3f19]:53366 [2606:4700::6811:ad05]:443 TIME_WAIT 0

TCP [2a06:5906:33c0:2a00:c0b3:b7db:b78c:3f19]:53773 [2600:1f13:800:7781:6eae:777:a01:d531]:443 ESTABLISHED 11864

TCP [2a06:5906:33c0:2a00:c0b3:b7db:b78c:3f19]:53774 [2600:1f13:800:7781:6eae:777:a01:d531]:443 ESTABLISHED 11864

TCP [2a06:5906:33c0:2a00:c0b3:b7db:b78c:3f19]:53793 [2600:9000:2111:2600:2:cecb:23c0:93a1]:443 ESTABLISHED 11864

TCP [2a06:5906:33c0:2a00:c0b3:b7db:b78c:3f19]:53796 [2a04:4e42:600::396]:443 ESTABLISHED 11864

TCP [2a06:5906:33c0:2a00:c0b3:b7db:b78c:3f19]:53798 [2600:1901:0:47fc::]:443 ESTABLISHED 11864

TCP [2a06:5906:33c0:2a00:c0b3:b7db:b78c:3f19]:53805 [2600:9000:2362:b800:1b:6b7c:c940:93a1]:443 ESTABLISHED 11864

TCP [2a06:5906:33c0:2a00:c0b3:b7db:b78c:3f19]:53823 [2606:4700::6812:bf8]:443 ESTABLISHED 11864

TCP [2a06:5906:33c0:2a00:c0b3:b7db:b78c:3f19]:53845 [2600:9000:2686:3600:1c:d13c:df40:93a1]:443 ESTABLISHED 11864

TCP [2a06:5906:33c0:2a00:c0b3:b7db:b78c:3f19]:53847 [2600:9000:23d3:c600:1d:d7f6:39d4:e6e1]:443 TIME_WAIT 0

TCP [2a06:5906:33c0:2a00:c0b3:b7db:b78c:3f19]:53848 [2600:9000:2686:3600:1c:d13c:df40:93a1]:443 ESTABLISHED 11864

TCP [2a06:5906:33c0:2a00:c0b3:b7db:b78c:3f19]:53849 [2600:9000:2686:3600:1c:d13c:df40:93a1]:443 ESTABLISHED 11864

TCP [2a06:5906:33c0:2a00:c0b3:b7db:b78c:3f19]:53850 [2600:9000:2686:3600:1c:d13c:df40:93a1]:443 ESTABLISHED 11864

TCP [2a06:5906:33c0:2a00:c0b3:b7db:b78c:3f19]:53851 [2600:9000:2686:3600:1c:d13c:df40:93a1]:443 ESTABLISHED 11864

TCP [2a06:5906:33c0:2a00:c0b3:b7db:b78c:3f19]:53852 [2600:9000:2686:3600:1c:d13c:df40:93a1]:443 ESTABLISHED 11864

TCP [2a06:5906:33c0:2a00:c0b3:b7db:b78c:3f19]:53854 [2600:9000:225d:0:18:63d:81c0:93a1]:443 ESTABLISHED 11864

TCP [2a06:5906:33c0:2a00:c0b3:b7db:b78c:3f19]:53855 [2600:9000:2362:7800:7:6e80:9580:93a1]:443 ESTABLISHED 11864

TCP [2a06:5906:33c0:2a00:c0b3:b7db:b78c:3f19]:53856 [2a05:d011:f6d:8c02:762f:6fc4:6233:ae7f]:443 TIME_WAIT 0

TCP [2a06:5906:33c0:2a00:c0b3:b7db:b78c:3f19]:53858 [2600:9000:2362:7800:7:6e80:9580:93a1]:443 ESTABLISHED 11864

TCP [2a06:5906:33c0:2a00:c0b3:b7db:b78c:3f19]:53862 [2600:9000:2680:3400:13:6a46:aa00:93a1]:443 ESTABLISHED 11864

TCP [2a06:5906:33c0:2a00:c0b3:b7db:b78c:3f19]:53894 [2606:4700::6812:af8]:443 ESTABLISHED 11864

TCP [2a06:5906:33c0:2a00:c0b3:b7db:b78c:3f19]:53897 [2001:4860:4802:34::36]:443 ESTABLISHED 11864

TCP [2a06:5906:33c0:2a00:c0b3:b7db:b78c:3f19]:53898 [2a00:1450:400c:c04::9d]:443 ESTABLISHED 11864

TCP [2a06:5906:33c0:2a00:c0b3:b7db:b78c:3f19]:53899 [2606:4700:10::6816:4ad8]:443 ESTABLISHED 11864

TCP [2a06:5906:33c0:2a00:c0b3:b7db:b78c:3f19]:53900 [2606:4700:10::6816:4bd8]:443 ESTABLISHED 11864

TCP [2a06:5906:33c0:2a00:c0b3:b7db:b78c:3f19]:53925 [2a00:1450:4009:822::2003]:443 ESTABLISHED 11864

TCP [2a06:5906:33c0:2a00:c0b3:b7db:b78c:3f19]:53932 [2606:4700:4400::ac40:9249]:443 ESTABLISHED 14128

TCP [2a06:5906:33c0:2a00:c0b3:b7db:b78c:3f19]:53946 [2606:4700:4400::ac40:9249]:443 ESTABLISHED 14128

TCP [2a06:5906:33c0:2a00:c0b3:b7db:b78c:3f19]:53981 [2a00:1450:4028:80a::2003]:443 ESTABLISHED 11864

TCP [2a06:5906:33c0:2a00:c0b3:b7db:b78c:3f19]:53989 [2a02:26f0:fd00:2a::217:d223]:443 ESTABLISHED 11864

TCP [2a06:5906:33c0:2a00:c0b3:b7db:b78c:3f19]:54000 [2606:4700::6811:ae05]:443 ESTABLISHED 1724

TCP [2a06:5906:33c0:2a00:c0b3:b7db:b78c:3f19]:54003 [2606:4700::6811:ad05]:443 ESTABLISHED 1724

TCP [2a06:5906:33c0:2a00:c0b3:b7db:b78c:3f19]:54013 [2a02:26f0:fd00:2a::217:d223]:443 ESTABLISHED 11864

TCP [2a06:5906:33c0:2a00:c0b3:b7db:b78c:3f19]:54022 [2a02:26f0:30::58dd:580b]:443 ESTABLISHED 11864

TCP [2a06:5906:33c0:2a00:c0b3:b7db:b78c:3f19]:54082 [2a02:26f0:fd00:8::58dd:78d7]:443 ESTABLISHED 10036

TCP [2a06:5906:33c0:2a00:c0b3:b7db:b78c:3f19]:54083 [2a02:26f0:fd00:8::58dd:78d7]:443 ESTABLISHED 10036

TCP [2a06:5906:33c0:2a00:c0b3:b7db:b78c:3f19]:54084 [2a02:26f0:fd00:8::58dd:78d7]:443 ESTABLISHED 10036

TCP [2a06:5906:33c0:2a00:c0b3:b7db:b78c:3f19]:54087 [2a02:26f0:fd00:8::58dd:78df]:443 ESTABLISHED 10036

TCP [2a06:5906:33c0:2a00:c0b3:b7db:b78c:3f19]:54088 [2a02:26f0:fd00:8::58dd:78df]:443 ESTABLISHED 10036

TCP [2a06:5906:33c0:2a00:c0b3:b7db:b78c:3f19]:54089 [2a02:26f0:fd00:8::58dd:78df]:443 ESTABLISHED 10036

TCP [2a06:5906:33c0:2a00:c0b3:b7db:b78c:3f19]:54090 [2a02:26f0:fd00:8::58dd:78df]:443 ESTABLISHED 10036

TCP [2a06:5906:33c0:2a00:c0b3:b7db:b78c:3f19]:54091 [2a02:26f0:fd00:8::58dd:78df]:443 ESTABLISHED 10036

TCP [2a06:5906:33c0:2a00:c0b3:b7db:b78c:3f19]:54092 [2a02:26f0:fd00:8::58dd:78df]:443 ESTABLISHED 10036

UDP 0.0.0.0:500 : 4644

UDP 0.0.0.0:3702 : 2232

UDP 0.0.0.0:3702 : 2232

UDP 0.0.0.0:4500 : 4644

UDP 0.0.0.0:5050 : 8216

UDP 0.0.0.0:5353 : 2404

UDP 0.0.0.0:5353 : 6300

UDP 0.0.0.0:5353 : 6300

UDP 0.0.0.0:5355 : 2404

UDP 0.0.0.0:51634 0.0.32.10:443 11864

UDP 0.0.0.0:51816 : 2232

UDP 0.0.0.0:53026 0.0.0.3:443 11864

UDP 0.0.0.0:55442 : 14128

UDP 0.0.0.0:55463 : 2404

UDP 0.0.0.0:58278 : 2404

UDP 0.0.0.0:58286 : 14128

UDP 0.0.0.0:63466 : 2404

UDP 127.0.0.1:1900 : 6532

UDP 127.0.0.1:50514 : 6532

UDP 127.0.0.1:55260 127.0.0.1:55260 4612

UDP 192.168.0.222:137 : 4

UDP 192.168.0.222:138 : 4

UDP 192.168.0.222:1900 : 6532

UDP 192.168.0.222:50513 : 6532

UDP [::]:500 : 4644

UDP [::]:3702 : 2232

UDP [::]:3702 : 2232

UDP [::]:4500 : 4644

UDP [::]:5353 : 6300

UDP [::]:5353 : 2404

UDP [::]:5355 : 2404

UDP [::]:51634 [2a00:1450:4009:821::200a]:443 11864

UDP [::]:51817 : 2232

UDP [::]:53026 [2a06:98c1:52::3]:443 11864

UDP [::]:55463 : 2404

UDP [::]:58278 : 2404

UDP [::]:63466 : 2404

UDP [::1]:1900 : 6532

UDP [::1]:50512 : 6532

UDP [fe80::15:c236:56f9:e780%14]:1900 : 6532

UDP [fe80::15:c236:56f9:e780%14]:50511 : 6532
MotoX80 36,401 Reputation points

2025-03-15T12:12:13.6466667+00:00
Download and run Tcpview.

https://learn.microsoft.com/en-us/sysinternals/downloads/tcpview

Click on the Process Name column to sort it. Look for the .exe name of your game. Hit the spacebar to pause the update.

If you don't see any connections, then one possibility is that the game launches sub processes to connect to the remote servers.

Download and run Process Explorer.

https://learn.microsoft.com/en-us/sysinternals/downloads/process-explorer

The default view is to show the process tree. Here Powertoys.exe launched other programs. If your game launches other programs, look for those names in tcpview.

You can test network connectivity with these Powershell statements. Just copy/paste into a Powershell prompt.

1..300 | foreach { $nc = Test-NetConnection -ComputerName microsoft.com -Port 443 # 443 is HTTPS "{0} - Address = {1} Success = {2}" -f (get-date), $nc.RemoteAddress, $nc.TcpTestSucceeded start-sleep -Seconds 10 }

You can launch that to test MS.com while you play your game for a while, and then check the window to see if it failed to connect at any point.

If it doesn't have any problems, then you know that the path from PC-->router-->ISP appears to be ok.
Kyle Grady 0 Reputation points

2025-03-15T13:23:29.35+00:00

Hey, I appreciate you taking the time to comment

In TCPView I get this:

14 instances with the same name, only 12 have a remote address and port, the other 2 don't - could this be an issue?

Also using Process explorer shows 4 'UnrealCEFSubProcess' instances, whereas TCPView shows 5, is this something to have a look at too? the 'taskhostw.exe' instances don't appear on my TCPView either, neither does the 'unsecapp.exe'
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
MotoX80 36,401 Reputation points

2025-03-15T14:28:58.2433333+00:00
Tcpview will only show processes that have network connections. Ignore taskhostw.exe and unsecapp.exe, they are part of Windows.

You commented "The issue is with major packet loss to a specific server (162.249.72.1)". Were you able to find a log file that contained an error message when you experienced connectivity problems? Is that where you saw 162.249.72.1 referenced? Can you post whatever message you found. Maybe someone will recognize the error.

I have no idea how those programs work. I guess that we can just pick an address or 2 and monitor connectivity and see if it fails at some point.

Start by rebooting your pc to get a fresh start. Then launch the game and after it's initialized, pause it.

Launch task manager and make note of available memory and the number of handles.

Run this PS to test connectivity. That will run for 50 minutes. Go play your game and when it dies, check the task manager values, and the PS window to see if it too had connectivity problems.

1..300 | foreach { $ms = Test-NetConnection -ComputerName microsoft.com -Port 443 # 443 is HTTPS "{0} - Microsoft - Address = {1} Success = {2}" -f (get-date), $ms.RemoteAddress, $ms.TcpTestSucceeded $va = Test-NetConnection -ComputerName 104.18.34.210 -Port 443 # 443 is HTTPS "{0} - Valorant - Address = {1} Success = {2}" -f (get-date), $va.RemoteAddress, $va.TcpTestSucceeded $un = Test-NetConnection -ComputerName 88.221.88.41 -Port 443 # 443 is HTTPS "{0} - UnrealCF - Address = {1} Success = {2}" -f (get-date), $un.RemoteAddress, $un.TcpTestSucceeded start-sleep -Seconds 10 }
Kyle Grady 0 Reputation points

2025-03-15T14:51:44.8833333+00:00

Okay,

I got this server from both the game's support team and also their website with FAQs etc.

This is the IP for the EU game servers which I apparently connect to, see reply below from support team:

There was no error message anywhere, as the issue is only visible in game, by means of random stuttering. My game doesn't 'die' as in crash or anything, just random stuttering happens causing the game to be unplayable as it's fast paced and accurate etc. (first-person tac shooter). Though I will check when a stutter happens if anything changes. I have tried monitoring task manager whilst playing too, but nothing unusual happens at all, everything stays smooth with barely any fluctuations.

Very strange though as every single other thing connects perfectly, I've not had a single drop in my internet or connectivity to anything else on this network as of yet.
Kyle Grady 0 Reputation points

2025-03-15T15:08:41.48+00:00

Aditionally, Following the above,

I have 9.5/31.9GB available whilst in game, with very little fluctuation (going up to 9.6 and back sometimes that's all) And that powershell test is 'true' on every connection success instance.

I also have around 89500 handles fluctuating by a few hundred up and down whilst playing if this means anything..
Kyle Grady 0 Reputation points

2025-03-15T15:30:02.49+00:00

Just to add too,

These are all the in-game graphs after a good 50 minutes of being in game too, all completely normal and stable, but plenty of stuttering still.
MotoX80 36,401 Reputation points

2025-03-15T16:09:20.47+00:00
I'd love to help you, but my Magic Crystal Ball is in the repair shop at the moment. Sorry, lame attempt at some humor.

Going back to the "usual suspects", do you have any 3rd party antivirus software installed? Or do you just use Defender?

Does your game write to files in your Documents folder? I wonder if OneDrive is trying to copy them to the cloud.

How about stopping everything that isn't absolutely required when you play the game? Windows has become rather bloated these days. Start by killing Edge with Powershell.

get-process msedge | stop-process

I would also stop services, but I don't have a good way to tell you what to stop. My Dell laptop has something called Smartbyte which appears to do something with the network. I also have a service from Intel called "Thunderbolt(TM) Peer to Peer Shortcut". I have no idea what it does! I didn't know it was there.

Here's a thought, use Process Monitor to do a high level network trace.

https://learn.microsoft.com/en-us/sysinternals/downloads/procmon

Under the Options menu, select History Depth, enable ring buffer, and limit it to 1024 MB.

Under the Filter menu select Drop filtered events.

Then add a filter entry for "Operation begins with TCP".

Start the capture and then go play the game. When it stutters, switch back to procmon and immediately stop the capture. Look to see if any processes other than your game are doing network calls.

It should look like this.
MotoX80 36,401 Reputation points

2025-03-15T17:01:22.4766667+00:00
Here's a trick that you could try. If some other process is temporarily using a lot of cpu, it may be getting dispatched before your game processes causing the stuttering.

Get-Process -Name unreal* | ForEach { $_.PriorityClass = "AboveNormal"} Get-Process -Name valorant* | ForEach { $_.PriorityClass = "AboveNormal"}

You would need to run that every time you launch the game. It only applies to the running instances of the programs.
Kyle Grady 0 Reputation points

2025-03-16T10:06:54.02+00:00

Hey,

I only run Avast free antivirus as extra,

I have tried switching to AVG also to no avail, I have allowed every process through as exceptions to those antiviruses aswell as defender too.

I have tried clean boots before play testing too.

I have also deleted as much bloatware as possible after a full windows reset. I also uninstalled every other possible program at one point too including any registry leftovers for each. (I have been at this issue for 7 months now...)

I have tried changing all Valorant related processes priority to 'above normal' and 'high' and back.

MS edge is permanently stopped.

Valorant writes nothing to my documents folder, I have also entirely deleted OneDrive as I have all files backed up to a separate hard drive through FileTransfer.

During this process monitor test, the only other service apart from the game / game client / svchost that was doing a network call was 'lghubagent.exe' which is background from my mouse software (Logitech G Hub) however I have now uninstalled G Hub and only using the On board memory mode on my mouse which has no background services running, after testing still nothing changed..

After running these commands in powershell though, I've had a new error pop up causing my game to crash and show error code: VAN 1067, which after some research should be fixed with a full re-install, but it didn't. I heard updating BIOS might help so I've just been trying to update my BIOS as it's on f16d and the latest is f19d - but I can't do it because apparently I don't have a flash drive less than 32GB to format as fat32 to update from.. Currently resisting the urge to smash my PC.So hopefully I don't need to update my BIOS.
Kyle Grady 0 Reputation points

2025-03-16T10:25:56.9866667+00:00

Hey, update sorry, managed to update the BIOS anyways..

However now I'm still getting the VAN 1067 error causing my game to crash after a few minutes, I will try and sort this as today's project before continuing troubleshooting the stuttering.
MotoX80 36,401 Reputation points

2025-03-16T12:07:04.07+00:00

Sorry Kyle, I've about run out of ideas.

Have you tried tweaking the graphics frame rate or resolution?
Kyle Grady 0 Reputation points

2025-03-16T12:45:20.2333333+00:00

Hi,

Yes I have configured all graphics settings to the lowest, highest and in between, along with running in both fullscreen + windowed modes etc.

A slight change though since I fixed the VAN 1067 error just now... -My network RTT (Round trip time) graph in game is now throwing up minor peaks roughly around when I'm experiencing the stutters..

Does this confirm it is a network issue with packet loss do you think?

I may also try somehow switching back to windows 10 to see if that helps. (if I can figure out how to online)

No worries mate I appreciate your insight massively, it might just be a problem that can't be fixed and i'll have to live with it.
MotoX80 36,401 Reputation points

2025-03-16T15:40:44.8366667+00:00

Does this confirm it is a network issue with packet loss do you think?

It would sure look like they are related. The obvious problem is that you don't know which device is causing that. Your pc, your router, your ISP, the hundreds of other devices/cables between you and the game server.

There is a tool named iperf that I used years ago to test network throughput.

https://iperf.fr/iperf-doc.php

Its been a while since I played with it, but the thought would be to run it and test against one of their public servers and see if spikes at the same time as your monitor tool. If it does not spike, then that would appear to indicate that the problem is not with your PC/router/ISP but somewhere else out the internet.

If nothing else, it might tell you that you are wasting your time trying to "fix" your pc.
Geoff McKenzie 865 Reputation points

2025-03-18T00:46:51.3866667+00:00

Last thoughts...

To rule in / out network.

Install Wireshark - There are inbuilt options in windows, some of which, I see, have been discussed already. But Wireshark will also help with analysis.

My thinking is you can run wireshark, play the game, then analyse the network trace. If it is indeed related to network latencey you may get clear information as to the reason (even if not the source), e,g, retransmits, out of sequence, etc.. From memory Wireshark even includes tools to specifically analyse for such patterns. Bonus points if you can install wireshark on a machine between your PC and router - most people do not have that option so on the machine with issues is usually good enough.

Look for other environmetals

E.g. I can't remember if you mentioned or not whether you are Wireless or wired (ethernet) between your PC and Router. If wireless try wired. Maybe you have a neighbour who turns on a microwave or whose Wifi intrudes on yours ??? Have a think outside the boxes - even time of day may be relevant.

Is anyone else sharing your network (including the uninvited)

Router stats and tools

Logon to your router, check if you have access (some ISPs lock them down if they provide them as part of your plan). If you can, then, check your router's Logs, statistics, tools, etc. etc. There may be a hint in there. You may even be able to turn up logging. Check CPU, Memory, throughput, unidentified clients, etc. on the router.

I hope you work it out I would be interested to see what it ends up being.

Remeber, if you can find another player to try from your house it may be revealing.

Good luck
Kyle Grady 0 Reputation points

2025-03-22T11:42:40.2066667+00:00

Hey,

I've installed wireshark and ran a packet capture (this program is pretty cool by the way)

I've pinpointed the conversation between my ip (192.168.0.222) and the server connected to (162.249.72.1) and I notice that after just a few minutes of playing, the packets from A-B are 4194 but from B-A are only 3907, this means packet loss, yes?

The other statistics I'm not too sure about what they all mean so I will have to do some research...

I also re-connected to a game with a different server (185.40.64.1) and got the same stuttering result however..

I am also connected via ethernet cable directly to the router
Geoff McKenzie 865 Reputation points

2025-03-25T22:43:20.7733333+00:00

Hi Kyle,

Life gets in the way of follow up sometimes.

That looks like a stats/summary screen. The difference in packes does not necessarily mean packet loss - Some protocols streamline traffic e.g. one acknowledgement packet for mutiple recieved packets.

What you want to look at is the actual traffic rather than the stats/summary. In the main view you can apply a display filter to focus on the IP(s) of interest. In that view you should be able to see each packet in each direction. This will show things like latency, retranmits, out of order, etc. more easily. Wireshark usually highlights some of these to make them eaasier to identify in that view as well.

Have a look at some of the wireshark help information online and see what works for you.
Kyle Grady 0 Reputation points

2025-03-29T08:43:10.6766667+00:00

Hey,

Of course, I know all too well haha I work a lot of hours and find it difficult to have time to mess about with my computer during the week, hence I only really reply on weekends..

I certainly will dive deeper later on today and maybe tomorrow when I get time, it's just frustrating as I feel like I'm going nuts with trying all this stuff with no tangible results.

There has to be a simple reason and solution, it's just finding it that is killing me lol!
Kyle Grady 0 Reputation points

2025-04-05T14:38:34.9166667+00:00

Hi,

Just to update if anyone is keeping tabs, I have installed a clean, fresh installation of windows 10 now, only services running are for the game and only programme installed apart from chrome is the game itself..

Still the issue persists, I have tried looking into wireshark's analysis before I did this, yet all packets seem to travel both to and from the server perfectly fine?? however I can't ping it with cmd? I find this really odd.
MotoX80 36,401 Reputation points

2025-04-05T17:23:05.0766667+00:00

It's not unusual for admins to block ping packets to their servers. If you know the port number that the game uses, then you can try Powershell's Test-NetConnection or Invoke-WebRequest to connect to that port.

I doubt very much that forum users can provide you with an "ah-ha!" moment where you can run one command and suddenly your problem is solved. We have no (easy) way to recreate the issue, and there are too many network devices between your pc and the server out on the internet to effectively troubleshoot.

Some random thoughts here.... mainly a process of elimination to see if you can identify where the root problem might be...

Do you have a different game that you can try? Preferably to a different software host (different servers). That might indicate the problem is with either your router or your ISP.

Do you have any friends who play the same game? Do they also have the problem?

Can you take your pc to a friend's house and see if you have the same problem using their ISP?

Can you have a friend bring their pc to your house and try your game using their pc?

What about a VPN? If you can route the network traffic down a different path over the internet, that might make a difference.

This might be a long shot... Open a command prompt and run "ipconfig /flushdns", launch the game, then run "ipconfig /displaydns". Look for DNS entries for Riot Games. Then do an nslookup for those names and see if you get multiple IPv4 addresses back. Example "nslookup yahoo.com" returns multiple addresses for me. If these guys are a big game provider, then I would expect them to have multiple servers or some content distribution network. My thought is to see if you can force your pc to use a specific IP address, or to try each address one by one. If nslookup only returns one address, then this won't work. If it does return multiple entries, then you can update the Windows hosts file (C:\Windows\System32\drivers\etc\hosts) to force the use of a specific IP. I think that should work as long as they don't hardcode IP addresses in their game configurations.

https://www.bing.com/search?q=how+to+update+the+windows+hosts+file
Kyle Grady 0 Reputation points

2025-04-06T18:56:05.1366667+00:00

Hi,

All other games run perfect buttery smooth apart from this one.

I don't have anyone I can bring here to test their connections, however when I was at my old place, I had this same exact PC and setup with no changes and it worked perfectly like everything else.

I have tried playing on a VPN and it made 0 difference, even trying a few different VPN servers.

I am currently doing this nslookup, however there are at least 10 different DNS entries relating to riot games / valorant with different names, is it a case of going through every single one, getting an ip address if there are multiple and then force the use of each ip for each individual dns entry do you think?

for example I got 2 returned for this one:

and also DNS timeouts, hopefully unrelated but I wouldn't know
MotoX80 36,401 Reputation points

2025-04-07T12:33:13.3566667+00:00

I wonder if you are trying to use one of the game servers as a DNS server.

My router (192.168.1.1) serves as my DNS server so that I can register local names. It then queries internet based DNS servers for everything else. I can also force nslookup to use Google's DNS servers.

however when I was at my old place, I had this same exact PC and setup with no changes and it worked perfectly like everything else.

That would tell me that we are likely wasting time messing with DNS and should focus on your router.

Are there any firmware updates available for your router? Do you use WIFI or a cable?

Have you tried any of the speed tests?

https://www.bing.com/search?q=how+to+test+my+router+performance
Kyle Grady 0 Reputation points

2025-04-13T19:01:31.15+00:00

Hi, I am connected via ethernet cable directly to the router. My speeds are below:

This is pretty much bang on what I pay for, I'm on a 150mbps plan, 30 upload is fine too, unsure if there are any other types of tests apart from internet speed I could check?

My router firmware is up to date with the latest version on sky's info for my hub (Sky Max Hub) and everything else is buttery smooth..
MotoX80 36,401 Reputation points

2025-04-14T13:35:42.9633333+00:00

If you have a Wireshark trace, you can look for retransmits and other errors.

https://learn.microsoft.com/en-us/troubleshoot/windows-client/networking/tcp-ip-connectivity-issues-troubleshooting?source=recommendations

Have you tried using a different cable? Or plug it into a different port on the router?
Kyle Grady 0 Reputation points

2025-04-21T12:47:51.3166667+00:00

I have tried a different cable, I have also tried plugging it into all available ports with no difference at all..

I may have a look again at wireshark in future when I have more time, however I feel like this has turned in to something way too advanced for my knowledge and with real life responsibilities I'm not sure I have the effort anymore, it's been a fun run with the game but I suppose I'll have to give it up for good and take the money loss I've spent in game.

Maybe I'll just upgrade and get a new PC one day and see if that fixes something, or swap internet provider in a couple years.

All help has been massively appreciated though, unfortunately life doesn't want to play ball with me on this.

Share via

Tracert requests all timing out for one specific server

1 answer

Your answer