📒 

Traceroute (or Tracert in Windows) are network diagnostic tools used to track the path that data packets take from one device (like your computer) to a destination server. These utilities help you understand the route data travels over the internet and can pinpoint where network delays or connection problems are occurring.

In this article, we will explain what Traceroute and Tracert are, how they work, and how to use them to troubleshoot network issues.


What Are Traceroute and Tracert?

Traceroute (in Linux and macOS) and Tracert (in Windows) are command-line utilities that show the path data packets take to reach their destination. Along the way, the data passes through multiple network devices called hops (typically routers), and Traceroute/Tracert measures the time it takes for data to pass through each hop.

These tools provide:

  • The IP address or domain name of each hop the data passes through.
  • The response time (in milliseconds) for each hop, indicating how long it takes for data to move from one point to another.

By analyzing the path, network administrators can identify where bottlenecks or connection issues are happening in the network.


How Do Traceroute and Tracert Work?

Traceroute and Tracert work by sending small data packets with varying Time-to-Live (TTL) values. TTL is a value that limits the lifespan of the packet as it travels across the network. Each router that receives the packet decreases its TTL by one. Once the TTL reaches zero, the router discards the packet and sends an error message back to the sender, providing its information (IP address and response time).

The tools increase the TTL with each new packet sent, allowing you to trace the path of the packet, hop by hop, until it reaches the final destination.


How to Use Traceroute in Linux and macOS

On Linux and macOS, the command traceroute is used. Here’s how to run it:

Step 1: Open the Terminal

  • On macOS, press Command + Space, type Terminal, and press Enter.
  • On Linux, open the terminal by pressing Ctrl + Alt + T.

Step 2: Run the Traceroute Command

To use traceroute, type the following command and press Enter:

traceroute [destination]

For example, to trace the route to example.com, you would type:

traceroute example.com

The output will display each hop, showing its IP address (or hostname) and the time it took for the packet to reach that hop.

Sample Output:

traceroute to example.com (93.184.216.34), 64 hops max, 52 byte packets 1 192.168.1.1 (192.168.1.1) 1.123 ms 0.884 ms 0.757 ms 2 10.1.1.1 (10.1.1.1) 5.340 ms 5.232 ms 5.130 ms 3 isp.example.net (203.0.113.1) 30.543 ms 30.321 ms 30.189 ms …

Each line shows a hop along the route, with its IP address (or domain name) and the time taken in milliseconds.


How to Use Tracert in Windows

On Windows, the Tracert command is used instead of Traceroute.

Step 1: Open Command Prompt

  • Press Windows + R, type cmd, and press Enter.

Step 2: Run the Tracert Command

To run tracert, type the following command and press Enter:

tracert [destination]

For example, to trace the route to example.com, type:

tracert example.com

Sample Output:

Tracing route to example.com [93.184.216.34] over a maximum of 30 hops: 1 1 ms 1 ms 1 ms 192.168.1.1 2 5 ms 5 ms 5 ms 10.1.1.1 3 30 ms 30 ms 30 ms isp.example.net [203.0.113.1] …

Like the traceroute command, each line shows the IP address (or hostname) of each hop along the route, as well as the time taken for the packet to reach each hop.


Understanding the Traceroute/Tracert Output

The output from Traceroute/Tracert provides valuable information for diagnosing network issues.

  1. Hop Number: Each line corresponds to a hop, showing the packet’s journey from one router to the next.
  2. IP Address/Hostname: The IP address (or domain name) of the device at each hop.
  3. Response Time: The time it took for the packet to reach the hop and return. Typically measured in milliseconds (ms), it shows three values per hop, each representing a separate attempt.
  4. Asterisks (*): If a hop shows asterisks instead of a response time, it means the packet timed out or the device at that hop isn’t responding.

Common Uses of Traceroute and Tracert

Traceroute and Tracert are essential for troubleshooting various network problems, including:

1. Identifying Network Bottlenecks

If one or more hops have high response times, it indicates a possible congestion or slow connection at that hop. This can help you determine where the slowdown is happening in the network.

2. Locating Connection Failures

If the data packets fail to reach the destination, Traceroute or Tracert will show where the connection fails. You can use this to locate problematic routers or network segments.

3. Analyzing Network Paths

Traceroute helps map out the exact path data takes to reach a server, which can help administrators understand how traffic flows through the network and identify inefficient routes.

4. Diagnosing Routing Issues

Traceroute can reveal misconfigured routes or issues with routing protocols, allowing network administrators to correct routing tables or adjust traffic flow.


Troubleshooting Traceroute and Tracert Issues

Here are some common issues and how to troubleshoot them when using Traceroute or Tracert:

1. No Response from a Hop (Asterisks)

If a hop shows * * *, it means that device is not responding to the Traceroute request. This could happen due to:

  • Firewall blocking ICMP packets: Some routers or firewalls may block the packets sent by Traceroute, leading to no response.
  • Device prioritizing other tasks: Some network devices deprioritize Traceroute requests in favor of other network traffic.

2. Slow Response Times

High response times in the output suggest that a particular hop may be experiencing high traffic or performance issues. You can use this information to pinpoint slowdowns in the network.

3. Traceroute Hangs or Fails

If Traceroute gets stuck or fails to complete, it could be due to network issues like:

  • DNS resolution problems
  • Routing errors
  • Firewalls blocking the connection

Conclusion

Traceroute and Tracert are invaluable tools for diagnosing and troubleshooting network issues. They allow you to trace the path of data packets and identify where bottlenecks or connection problems are occurring in the network. Whether you’re troubleshooting slow internet connections, diagnosing network outages, or simply analyzing traffic routes, understanding how to use these utilities can significantly improve your ability to manage and maintain a healthy network.