Post #4 Travelling Through a Network

 I pinged Google, a website from Japan, and a website from Germany. Both the websites from Japan and Germany averaged at 21ms, while Google averaged at 23ms. I am not sure how this happened. Logically, it should taken longer for the pings to go to the domains that are farther away than Google, yet somehow they were both 2ms faster on average. Other times where I have used ping and traceroute, the geographical location and distance directly and proportionately affected the speed of the pings and traceroutes. The more distance they had to go, the longer average time it took. The results I have gotten here are very peculiar to me and I will have to look more into why Google was the slowest. Ping and traceroute can be used to troubleshoot servers or websites if you cannot reach what you are trying to reach. Using the ping command will simply let you know whether or not a host is reachable or to give you latency times about that host. You can use traceroute if you need a more detailed answer as to where the packets are getting stuck or how many "hops" are needed to get from you to the destination. For example, let's say to get to Google, it is four hops, but it is not working. You can ping Google to see if Google is reachable. If so, then you can use traceroute to make sure the packets are successfully hitting all the hops. If the packets get stuck on one of the hops, then you have located the problem on what is stopping you from reaching Google. This can be used if you work in IT and have access to each of those hops' locations to fix the issue. Two reasons for an error or timeout response would be either the host being unreachable (down), or if the network has a lot of traffic and not enough bandwidth to carry the packets.




Comments

Popular Posts

Post #7 E-commerce Sites

Post #1 Programming Languages