Traveling Through a Network

 For the ping activity, I choose the three sites, Google.com. the ping recorded times show  31.649MS, 74.016MS, 41.197MS,25.438MS, with a 20.0% packet loss.

Then for my second site I did a ping for Google.JP; the times for this site show 46.010MS, 27.880MS, 40.781MS and 35.667MS with a 26.7% packet loss and a TTL of 118.

 

For my last ping, I searched for a site I searched was yahoo.eu. This site had times of 453.095MS, 71.769MS,55.400MS with the TTL of 53 and a 0.0% packet loss.

The Traceroute activity I did for Google showed around nine hops with none failed.

For my next traceroute I did google.jp, which also had around nine hops with one failed.

The last traceroute activity I checked on the last site, which was Google.eu had around 9 hops and one that had failed (line 5). 

 

This activity taught me something new before starting this activity, and I followed the adobe reader guide. At the same time, my computer is a little older; it took a little time to find the Network Utility app on my laptop because it was my first time using it. Once I found the app, I started using the ping and traceroute on my chosen three websites. This activity gave me a more hands-on approach to learning how Packets are transmitted through different websites and how Data moves through the internet. Understanding how the ping and traceroute can identify troubleshooting, with Ping it determines how long it will take to connect to a website while traceroute checks the paths the computer is using to connect. There are a few reasons why a trace would return with an error response, such as the length and hop limit; with a ping failure, it could be network connection issues, or the network could be unreachable. Another reason for a ping failure could be that security software blocks the ping packet.