Tracert on Windows Returns Slower than on Linux?

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 TCP 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.

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 TCP 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.

As an addition to this, I believe there is a traceroute plugin for cygwin, so you can get linuxesque traceroutes on windows. – richzilla Apr 6 at 23:45 Nice! I have always wondered about this!

– lunchmeat317 Jul 2 at 3:49.

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.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.