Thomas Wilson
Packets move through networks from one computer to another. These tools are extremely useful when troubleshooting network configurations and if a network is talking or not. They move from devices like switches and routers until they reach the final destination. Packets usually move in specific order to their final destination. A ping and tracert command are different because the ping verifies that a host is reachable or not and the tracert command shows the detail of each stop at the routers and the time it takes to reach each router. When pinging each site, I noticed that the other countries website TTL is greater than google. This makes sense because the TTL is the determined "hop" time between servers before being dropped. When performing a tracert command, it shows each stop to the host's IP and the time it takes to get between each. Each tracert command gets longer in time to each host as it goes down the list. I noticed that google had 16 total stops and the other two sites had 8 and 14 stops. I assume that the amount of time and stops determines how large the site is and how many servers it has until it reaches the final host destination. From personal experience, my company uses an SMTP host and if the network is unavailable, I will ping that IP address and if it is unreachable then I know I do not have connection to the network needed. Then I can begin to troubleshoot why I do not have a connection. There is also an alternate address to ping and verify if the issue is on our side or the host. The ping command could timeout if the destination host does not respond in a certain amount of time. Also, if the network is down, the host will be unreachable until a network is successfully connected. The tracert command is essentially the exact same situation as a ping command except for it makes multiple stops until the final host. One way to troubleshoot the tracert is to look at the report and see where and how many times the server failed to ping.
\
Comments
Post a Comment