Question TRACERT (Trace Route) command slow in Windows 10

Toggle sidebar Toggle sidebar
Solution
kerberos_20
Hellsinki said:
You didn't read the information in the link. That's my question, but with details
Before some windows 10 update, everything was fine, now it's not. Need to find the cause and fix it.
Click to expand...
internal timers were changed, you cant fix it
you can work around it, here example:
go to c:\windows\system32 folder
create new text file, label it as tracer.bat (you do need admin rights for making files in system32 folder)
open it in notepad
type in:
Code: 
@echo off
c:\windows\system32\tracert.exe -d -w 1000 %1
save file and in commandline/terminal instead of tracert command, use tracer command
ex:
tracer 8.8.8.8
Sort by date Sort by votes
Hellsinki said:
You didn't read the information in the link. That's my question, but with details
Before some windows 10 update, everything was fine, now it's not. Need to find the cause and fix it.
Click to expand...
internal timers were changed, you cant fix it
you can work around it, here example:
go to c:\windows\system32 folder
create new text file, label it as tracer.bat (you do need admin rights for making files in system32 folder)
open it in notepad
type in:
Code: 
@echo off
c:\windows\system32\tracert.exe -d -w 1000 %1
save file and in commandline/terminal instead of tracert command, use tracer command
ex:
tracer 8.8.8.8
 
  • Like
Reactions: Hellsinki
Upvote 1 Downvote
Solution
kanewolf said:
Are you using the "-d" option to avoid trying to DNS translate addresses?
Click to expand...
tracing with the "-d" parameter is fast, but "tracert (exemple)" that's the standard command I always run.
kanewolf said:
A slow DNS could be contributing to your slowness.
Click to expand...
I'll repeat myself here in this forum thread as well.
There is another Windows 10 LTSC 1809 OS Build 17763.6293 computer nearby and everything is fine there. They are both connected to the same network, use the same DNS that are registered in the router. By the way, Traceroute also works without problems in the router.

If I install a Windows 10 image with older updates (with an older build), then the "tracert (exemple)" tracing goes perfectly, but some days pass (1-7... days), the updates are downloaded (they are downloaded/installed automatically, I only sometimes need to reboot the computer) and the tracing becomes slow.

I specifically deleted my old Windows 10 LTSC 21H2 for testing and installed a new 10 Pro 22H2 OS Build 19045.4780 (currently 19045.4894), at the first launch I connected to the network and made a trace, it was already slow. Therefore, I am sure that some update introduced these "settings". But is it possible to fix this, as kerberos_20 writes, it is not entirely possible. Or maybe these "settings" can somehow be fixed in Windows Defender (what exactly should I check)? Or is this some kind of conflict with the software? Connecting to the network either by cable or by WiFi does not change the results.
 
Upvote 0 Downvote
Hellsinki said:
There is another Windows 10 LTSC 1809 OS Build 17763.6293 computer nearby and everything is fine there. They are both connected to the same network, use the same DNS that are registered in the router. By the way, Traceroute also works without problems in the router.
Click to expand...
The first one of these devices that runs will be slower than the other, since the router will cache data for some period of time.

I still don't understand your issue. You seem to be complaining about something you have no control over.
Find the source code to an alternative and build it, you can then tweak it any way you like.
 
Upvote 0 Downvote
kanewolf said:
What do you expect us to do? That is the part I don't understand ....
Click to expand...
As I understand it, the answer is from "kerberos_20" is the solution. But I would like to know in more detail (where the information is) why this is happening. Why did they do it (if the developers had a hand in it). I just needed the details. Do you understand? :)
 
Upvote 0 Downvote
Hellsinki said:
As I understand it, the answer is from "kerberos_20" is the solution. But I would like to know in more detail (where the information is) why this is happening. Why did they do it (if the developers had a hand in it). I just needed the details. Do you understand? :)
Click to expand...
Unless you have the source code (I definitely don't) then there is no way to know what was done. That is why I suggested you get an open source replacement and then you can see what is done. What Windows did internally, is an MS proprietary thing.
 
  • Like
Reactions: Hellsinki
Upvote 1 Downvote
Try using Powershell's Test-NetConnection and Test-Connection cmdlets.

Are the results still slow?

From my computer, Powershell (Admin):

PS C:\WINDOWS\system32> Test-NetConnection 8.8.8.8 -traceRoute


ComputerName : 8.8.8.8
RemoteAddress : 8.8.8.8
InterfaceAlias : My network name was here
SourceAddress : 192.168.1.201
PingSucceeded : True
PingReplyDetails (RTT) : 13 ms
TraceRoute : 192.168.1.1
172.27.219.2
68.86.252.17
96.216.84.61
162.151.61.121
96.110.235.69
96.110.40.29
68.86.166.222
71.25.197.130
209.85.245.207
142.251.64.101
8.8.8.8

Reference (and other references are easily found):

https://lazyadmin.nl/powershell/test-netconnection/
 
Upvote 0 Downvote
It looks like a dns delay but that would make no sense if you use the -d option.

If you are really ambitious you can do some research and tell us if this is some strange delay in the command or maybe it is referencing dns server even whe you told it not to.

It is even better that you have a second machine that performs differently to compare.

What I would do is load wireshark and capture all the data. A tracert command sends out multiple packets with the ttl increasing by 1 each time. This done to cause the device the decrements it to zero to send a special message back. It is this message that lets your pc know the IP that sent the message.

What it then does next is to look the IP in a DNS. If you set the -d option it should not talk to a dns server.

It has been a while since I have done this myself. What has changed is DNS is now many times encrypted and it looks like https traffic. was simpler to just set the wireshark filter for port 53 now it might take more looking through the raw data if the IP of the DNS server is not really known.

It might also be interesting to manually set the IP you see in a trace to some silly names in the HOSTS file. This would override the DNS and use the local names which should not cause the delay. I do not think it looks in the HOSTS file when you set the -d option either.
 
Upvote 0 Downvote
kerberos_20
I've written about this before, I'll say it again.
The interesting thing is that if the "hop" has the form:
YY ms YY ms YY ms - Domain-name [IPxx.xx.xx.xx.xx]
are executed quickly. But "hops" that look like:
YY ms YY ms YY ms - IPxx.xx.xx.xx.xx
are slow.
By the way, ping works fast.
Check it out, I think you'll have the same thing.
What could that mean? Is it really some kind of “internal timer”? A bug in the code?
 
Upvote 0 Downvote
Hellsinki said:
kerberos_20
I've written about this before, I'll say it again.
The interesting thing is that if the "hop" has the form:
YY ms YY ms YY ms - Domain-name [IPxx.xx.xx.xx.xx]
are executed quickly. But "hops" that look like:
YY ms YY ms YY ms - IPxx.xx.xx.xx.xx
are slow.
By the way, ping works fast.
Check it out, I think you'll have the same thing.
What could that mean? Is it really some kind of “internal timer”? A bug in the code?
Click to expand...
That says that a DNS request for the IP was sent out but a name was not returned. The software waited a while for a name resolution, then moved on. Totally reasonable.
 
Upvote 0 Downvote
Hellsinki said:
kerberos_20
I've written about this before, I'll say it again.
The interesting thing is that if the "hop" has the form:
YY ms YY ms YY ms - Domain-name [IPxx.xx.xx.xx.xx]
are executed quickly. But "hops" that look like:
YY ms YY ms YY ms - IPxx.xx.xx.xx.xx
are slow.
By the way, ping works fast.
Check it out, I think you'll have the same thing.
What could that mean? Is it really some kind of “internal timer”? A bug in the code?
Click to expand...
yes i checked youtube old videos win xp/7 and it was always slow
but i did provide workaround to make it fast, like 1second is more than enough
 
Upvote 0 Downvote

kerberos_20​

As I wrote earlier (maybe on another forum). I had LTSC 21H2 and everything was fine with it until some updates were installed. I have a hard drive (which is stored in a dark closet 😀) with the same LTSC 21H2 but there is nothing on it, that is, the system is just installed (not even activated yet), nothing is configured and there are no new updates. I put this hard drive instead of my main one, and you know what? As soon as it loaded, I connected to the Internet and ran the "tracert" command. It was just as slow. Strange.
Here are the updates that were installed in the system (the windows iso file had these updates)
KB5004331 Installed on 10/6/2021
KB5003791 Installed on 10/6/2021
KB5006670 Installed on 10/6/2021
KB5005699 Installed on 10/6/2021
and drivers update
ASUS - System - 1.0.0.13 Installed on 12.04.2024 (This is the date of installation of windows 10)
 
Upvote 0 Downvote
Hellsinki said:

kerberos_20​

As I wrote earlier (maybe on another forum). I had LTSC 21H2 and everything was fine with it until some updates were installed. I have a hard drive (which is stored in a dark closet 😀) with the same LTSC 21H2 but there is nothing on it, that is, the system is just installed (not even activated yet), nothing is configured and there are no new updates. I put this hard drive instead of my main one, and you know what? As soon as it loaded, I connected to the Internet and ran the "tracert" command. It was just as slow. Strange.
Here are the updates that were installed in the system (the windows iso file had these updates)
KB5004331 Installed on 10/6/2021
KB5003791 Installed on 10/6/2021
KB5006670 Installed on 10/6/2021
KB5005699 Installed on 10/6/2021
and drivers update
ASUS - System - 1.0.0.13 Installed on 12.04.2024 (This is the date of installation of windows 10)
Click to expand...
you can watch youtube tracert video from any windows version
if adress doesnt contain hostname, but only ip, it will be waiting for timeout (~5secs)
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom