Traveling Through a Network (POST 4)

 

For this week's assignment we explored Ping and Traceroute commands through different websites to see how information is transferred from one source to another. As we learned through the guideline, packets travel through the network when the PING or "Packet Internet Groper"/ Traceroute sends small pockets of information out to a specific IP address and requests responses from the recipient. As far as the PING and Traceroute results I had somewhat of a similar experience.

For the Ping commands I used three websites on my personal laptop which included Google, Apple (Japan), and Yahoo (Australia). The first Ping command for Google resulted in 4 packets being sent to the server and receiving 0 back which came up to a 100% loss meaning total failure. The second Ping command for Apple (Japan) resulted in 4 packets being sent to the server and receiving 0 packets back as well which came to another 100% loss. Finally, the last Ping command I sent which was for Yahoo (Australia), 4 packets were sent out and 0 was received back meaning another 100% loss. 

In regard to the Traceroutes, I had encountered the same issues I did when I used the Ping commands for the three websites. For the Traceroutes, I used the same three websites I used for the Ping commands. As far as Yahoo (Australia) and Google servers, the trace completed for 30 hops, but each hop had the request time out. For the Apple (Japan) server the request timed out for 18 hops of the trace. At the 19th hop there was a transmit error code message. As far as the roundtrip time and geographical location, I was not able to receive any information whatsoever for the Ping and Traceroute commands.

Ping and Traceroute commands can be used to troubleshoot internet connection problems when the packets of data are sent out and received back as a result of how long they take. Two possible reasons a ping request or traceroute command may fail is because the ISP may not receive the request at all or because the request timed out. Another reason could be the entire trace not completing as mine did in the Apple (Japan) traceroute.

Ping

 

Trace