Traveling Through a Network

I've known about ping, but never heard of traceroute. The ping activity was pretty surprising to me. I used the google website for here in the USA, Australia, and China. However, the ping difference had little to no difference between the three. The United States website is the one I thought would be much faster, but was only a few points lower. 
Screenshot (6).pngScreenshot (5).pngScreenshot (2).png
Each trial had 4 packets sent and each one had 4 packets received with 0% loss. Each trial went through one IP address four times. But each of the four times had different ms. It makes me wonder if a different website than google would bring up different routes and more packets. More packets could play a factor in possible packet loss. Each of the servers passed without any failure.
The traceroute activity I had a common server failure as seen below. 
Screenshot (10).pngScreenshot (11).png
Screenshot (12).png
For each of the trials, number 2, the request timed out. However, each of the three traceroutes went through 13 different servers. This is suprising to me. I figured there would be more servers to go through to get to the au goole and cn google. But maybe this is because it is all the same google website. After further research, changing up websites from google to other au and cn websites did have an affect. But with expected results. For foreign websites, it has to go through more servers. Which makes sense due to being farther away from foreign servers. The closer to the server, the better ping. 
Ping and traceroute can be used to troubleshoot problems by showing what server or router is failing. Possible reason may be due to loss of power or damaged hardware. Overall, it's quite amazing how fast the servers communicate and cover so much ground over so little of time. 



Comments

Popular posts from this blog

Computers in the Workplace

Network Security