More than once, our internet connection seems to develop a will of its own and refuses to cooperate. Restarting all associated devices (modems, routers, PCs, phones) is our first line of defense, but sometimes we have to dig a little deeper, and one of our main resources is the tracert command, also known as traceroute in the Linux universe. With its help, we can learn the path packets follow, determine the number of hops, detect latency issues, and identify other conflicts.
Tracert: How to Use It
In the specific case of Windows, it is enough to open a system console with elevated privileges and type tracert followed by the web address or IP number. This will start a chain of 'hops' with latency reports in milliseconds and information about each router along the way. While the ping command quickly checks whether the destination server is available, tracert seeks to determine the exact route and the time spent on each hop.
Limitations of tracert
Obviously, tracert is far from a perfect tool. One of its most interesting aspects is that it can adopt different protocols. For example, the Windows version works with ICMP Echo Request/reply, while traceroute favors UDP. However, a particularly strict configuration (for security reasons) can interfere with these protocols and lead to confusing results.
At the same time, there is the possibility that a correct tracert does not guarantee connectivity for certain applications, since a firewall may allow ICMP and reject the rest of the protocols. Add to that the concept of load balancing, which in the face of a traceroute command could present a non-existent route.
Alternatives and Correct Reading
If the idea of working with the system console doesn't appeal to you too much, the truth is that there are many programs out there with built-in tracert/traceroute functions. One of the most complete is PingPlotter, with a 14-day trial for its Pro edition and a fairly complete freeware mode that includes the ability to change protocols.
To conclude, we shouldn't get carried away by an overly literal reading of tracert. In addition to considering its limitations, we must not lose sight of the fact that the most important hop is the last one. Although there may be all kinds of problems along a route, ideally our destination shows acceptable latency, without packet loss. Good luck!
