Reputation: 9183
I have two computers, one Windows and one Linux sitting side by side on my desk, both connecting to the same internet. If I run a tracert on www.stackoverflow.com and traceroute www.stackoverflow.com, both return the same data. However, tracert on Windows takes 3x as long (with the same params) as traceroute on Linux (linux tr is almost instantaneous)
I tried tracert -d but no real difference to speak of.
How can I get Windows tracert to return at the same speed?
Thanks
Upvotes: 14
Views: 10980
Reputation: 101
Stumbled upon this old thread and wanted to say that there is an option to speed up tracert in Windows.
tracert -d -w 100
-d prevents hostname resolution
-w 100 sets the response timeout to 100ms.
You may get a missed ping reply if your pinging slow network gear over a VPN or distant MPLS, but it speeds up the tracert to about 40 seconds.
Upvotes: 10
Reputation: 31
tracert
sends the probes one by one, traceroute
sends 16 at a time (can be changed with the -N argument).
Upvotes: 2
Reputation: 7062
As a tip, you can speed up traceroute in Windows by disabling resolving with tracert -d
.
Upvotes: 4
Reputation: 104110
The Windows tracert
tool sends ICMP echo requests; many routers will just DROP
ICMP echo requests. Thus the tool must wait for an internal timeout before declaring that route dead.
The Linux traceroute
tool sends UDP connection attempts; routers have to forward these packets, so it works pretty reliably. This means the tool won't have to wait for timeouts from most of the routers along the way.
Upvotes: 11
Reputation: 1919
The Windows tracert
waits about 1 second between hops. The Linux traceroute
does not wait between hops. There is no documented option for the Windows tracert
to disable this delay.
Upvotes: 13