Packets of information travel through and bounce around to multiple different routers as it travels along the network to its final destination. The exact route it takes will vary due to internet traffic conditions and may even fail to get to its intended destination. If a packet fails to get to its destination or you wish to just test or troubleshoot connectivity, you can run a Ping and Traceroute commands in command prompt.
In pinging a US based Google.com, the average round trip time was 7ms and in pinging a Japan based Auone.jp the average was 113ms. Traceroute on Google shows single digit round trip time through nearly all hops but when tracing the Japanese hosted site, single digits until around hop 10 where it jumps to the 100s. The 100ms RTT jump is likely when the packets starting hopping to servers in Japan. Therefore, geographical location plays a big role in round trip time of packets. The closer you are the quicker data will be transmitted between computers.
Ping and Traceroute as also used to troubleshoot internet connectivity. If you were to try and visit Google.com but the webpage didn’t load, you can ping it to see if you get any error messages in the results. If you see a timeout message that means that the request took longer than the limit to acknowledge. This could be caused by network congestion, firewalls, or defective hardware. Pinging multiple sites can help determine if the issue with that specific site or if you need to troubleshoot issues on your side. If you see an error like unknown host, this means that the host name isn’t recognized and you may need to double check spelling. Running Traceroute can help determine where on a route it may have failed to its destination. The first hop should be your own network so if it that first hop has errors you know where to start. If it fails towards the end, it may be an issue with the host.
Comments
Post a Comment