Ping Activity
Trace
Packets are little chunks of data moving through a network in a series of hops. They are routed through a series of routers and switches until they reach their final destination. The results of the ping and trace are as follows:
Google.com – 4 packets were sent, and 4 were received with 0 lost. The approximate round trip time in milli-seconds was Minimum 48 Maximum 70ms Average 58ms
Amazon.co.uk – 4 packets were sent and 4 were received with 0 lost. The approximate round trip time in milli-seconds was Minimum 171ms Maximum 182ms Average 177ms
New.com.au -4 packets were sent and 4 were received with 0 lost. The approximate round trip time in milli-seconds was Minimum 31 Maximum 57ms Average 39ms
The traceroute were longer and much different. The traceroute displays the path the packet took and reports the IP addresses of all the routers it pinged along the way. A successful traceroute would end with the IP address specified. The traceroute I completed on google.com and new.com.au were successful. The traceroute on amazon.co.uk timed out after 30 hops and was not successful.
When troubleshooting internet connection problems, the Ping command allows you to verify the network connection and whether you have a good connection. A longer response time on pings indicates a poor connection. If an error is received, it could mean a network connectivity problem on the computer. The Tracert command will show all routers along the way. Those with longer connection times indicate an issue with that router.
A ping or traceroute might time out or return with an error message if a firewall blocks the connectivity or if that server is offline and unreachable.
Comments
Post a Comment