In Windows OS, you can use this from the command prompt. For example, when you want to check a route from your PC to Google's IP address, at the command prompt> hit the tracert "188.8.131.52". It should be noted, "184.108.40.206" is the IP address of Google public DNS server.
- Windows key + R
- Type "cmd" in the name input field of the "Run", press the Enter
- Input "tracert 220.127.116.11", press the Enter
The first displays the default gateway of the Windows PC running the tracert. Then we follow the 18.104.22.168 ⇒ 22.214.171.124 ⇒ ···, you can see that you have arrived finally traced to 126.96.36.199.
When I am running seen I think, but the display is slow.This is, for the middle of the obtained route IP, is due to perform a reverse lookup of the DNS.If you want to display early, and give it a -d.This will no longer run the reverse of the DNS.
How tracert works
tracert does NOT display all of the IP address on the path that passes through to the destination. You need to know what to make of tracert in order to understand this. Consider as an example addressed to previous 188.8.131.52.
When you run the tracert 184.108.40.206, "addressed to 220.127.116.11 ICMP Echo Request the" Send in the TTL = 1.However DGW routers at next TTL = 0 at the timing when trying to routing, from the router the source IP = 192.168.31.1 (DGW of PC), "Destination IP = [PC of IP] ICMP Time Exceeded is sent" you.What is displayed as the first route on the command prompt, will this source IP = 192.168.31.1.The following was sent in TTL = 2, TTL becomes 0 at the ISP router, as the source IP to 18.104.22.168 is the IP address of better interface close to the PC ICMP Time Exceeded is sent.To the next because sent in TTL = 3 ,,, to reach the destination, or you repeatedly until TTL = 30.
As can be seen from the above, not all IP on the path that passes is displayed, among the NW device passing, I side interface IP is gradually displayed in the order closer to the transmitting terminal.
In other words, the side interface closer to the destination, but there is a path, IP address of the interface is not displayed.
Linux and Cisco system of traceroute
You can use traceroute on Linux and Cisco equipment.It is not tracert.
There is no difference in the role, but a slightly different implementation.The transmission will continue to increase from UDP Higher port 33434 instead of ICMP Echo Request by one every time of transmission.So if you are at an ICMP on the FW, can not be the Linux traceroute although it is tracert of Windows, it will state that.
To reach the destination will receive the same ICMP Time Exceeded, and reach the destination, ICMP Destination Unreachable (Port Unreachable) will assume that is returned.
But, I mean -I in options like the Windows of tracert, it will be in operation in the ICMP Echo Request.