![]() ![]() The timeout message indicates that your machine believes it successfully sent ping queries to the destination. Both of these indicate a failure, but did you know that you can use these two results to predict where the network problem lies? The two most common results to watch for are timeout and unknown host. Results and techniquesĭelving a little deeper into the results, the ping output displays the hostname and IP address information, packet loss, response times, etc. This is because ping could not resolve the given hostname to an IP address in the second test. If you ping the same destination by hostname, and it fails, you know name resolution is not working. If you ping a destination by IP address, and the ping succeeds, you know you have basic connectivity. You can use the ping command to test name resolution services, too. I've used the continuous ping during reboots trick more than any other, however. I particularly like the ability do a quick name resolution query. I've already uncovered some good uses for ping with the above options. This is a quick name resolution query: # ping -c 1 server01įigure 4: Using the quiet mode with ping. ![]() ![]() You can use a variation of this to simply display the IP address of the destination by sending a single ping to a hostname. For example, to send five pings, type: # ping -c 5 192.168.2.200 You can adjust the number of pings by using the -c option, followed by the desired number of ping messages. I can even use an audible cue with ping, letting me know when the pings are successful. Plan for this if you work with both platforms. Note: The options for ping vary somewhat between Linux and Windows. In the meantime, I can work on other projects. When the ping results show success, I know the reboot process on the remote machine has been completed. I can issue the reboot command and then set up a continuous ping from my laptop to the server. The server needs to be rebooted before I can continue with its configurations. For example, imagine I'm remotely connected to a Windows server from my Linux laptop. One of my favorite uses of ping is to inform me when a remote server or network device has restarted. A practical introduction to container terminologyīy default, Linux sends continuous pings.That address is always 127.0.0.1, and pinging it successfully lets you know that the network adapter on your computer (and the networking software in your OS) is working properly. If you can't successfully ping your router, but your router appears to be turned on and working, you can try pinging what's known as a loopback address. Ping your loopback address (127.0.0.1).A successful response lets you know that your local network is working okay, and that the problem reaching the internet location is somewhere out of your control. If you can't successfully ping an internet location, you can then try pinging your router. Ping your router to see if you can reach it.The ping tool shows you right at the top the IP address it's working with. If you want know the IP address for a particular URL, you can ping the URL. And if you're interested in exploring those routes further, you can use another networking tool named tracert to do just that. If you get a successful response, you know that all the networking devices between you and that destination are working, including the network adapter in your computer, your router, and whatever devices exist on the internet between your router and the destination. Ping a URL (like or IP address to see if you can reach an internet destination.Now that you know how to use the command, here are some interesting things you can do with it: The time it takes packets to return to you can help you identify a slow connection, or if you're experiencing packet loss. This can help you determine if a network problem is somewhere on your local network, or somewhere beyond. You can test whether your computer can reach another device - like your router - on your local network, or whether it can reach a device on the Internet. When it gets the response, the ping tool shows you how long each packet took to make the round trip - or tells you there was no reply. Your computer sends several packets of information out to that device, and then waits for a response. You issue the ping command along with a specific URL or IP address. On a computer network, a ping tool is built into most operating systems that works in much the same way. Ping comes from a term used in sonar technology that sends out pulses of sound, and then listens for the echo to return. It's a handy tool that you can use to quickly test various points of your network. The ping command sends packets of data to a specific IP address on a network, and then lets you know how long it took to transmit that data and get a response. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |