Traveling through a Network

     Observing the ping and traceroute results, I find that the ping commands send back a few important factors that we can observe to troubleshoot any issues we are experiencing with websites. We can see how many packets have been delivered successfully, and how long it took for the ping to travel to and from the pinged website. If we are struggling to connect to a website, this diagnosis would be evident of an issue we would need to look deeper into and notify the website’s administrators. The traceroute results show us which routers our tracert is being sent through. Sometimes a router took too long to respond so the command line just moved on and left a symbol for ‘skipped’ in the command process. We can also tell that when you ping a website, the amount of time it takes to receive the ping back is either faster or slower based upon where the website's server is located. If I pinged a website that was locates in Los Angeles, and I am in Phoenix, the ping would travel very fast and only a few milliseconds but if the server is in Australia, it will take longer to make a complete ping command.  

      We can use the results of ping and traceroute commands to troubleshoot issues we have by identifying which websites are not delivering packets completely or which servers are struggling with their connection speeds. These are just a few of the simple diagnosis examples used with pings and tracerts. If a ping or traceroute command does not execute or complete, a router may have some interference from a foreign object or may have been messed with by local personnel, or maybe a server room’s HVAC system has gone down and was in need of repair. This would lead to the room heating up and the server overheating and losing its reliability.