![]() This should get you exactly the same results as pinging 127.0.0.1: Next, ping the server's network IP address from itself. etc/hosts on a Unix system) that the name service is using to resolve addresses to ensure that the entry is corrected.ĩ.2.2.3 Testing the networking hardware with ping If you get "ping: no answer," or "100% packet loss," but pinging 127.0.0.1 worked, then name services is resolving to an address, but it isn't the correct one. Section 9.2.8, Troubleshooting Name Services." Hosts file.) From here, skip down to the section (This may be as simple as a missing entry in a local If you get "unknown host: localhost," there is a problem resolving the host name localhost into a valid IP address. If this succeeds, try the same test on the client. Localhost, you should see output similar to the following: Localhost is the conventional hostname for the 127.0.0.1 loopback, and it should resolve to that address. Windows NT TCP/IP Network Administration, both published by O'Reilly.ĩ.2.2.2 Testing local name services with ping TCP/IP Network Administration, Chapter 11, and Craig Hunt & Robert Bruce Thompson's new book, You're the network manager, some good references are Craig Hunt's If it is a Windows client, follow the instructions in Chapter 3,Ĭonfiguring Windows Clients, to install networking support. See your operating system documentation if it is a Unix server. TCP/IP either isn't installed or is seriously misconfigured. If this test fails, you have a serious local problem. The addressġ27.0.0.1 is the internal loopback address and doesn't depend on the computer being physically connected to a network. If you get "ping: no answer from." or "100% packet loss," you have no IP networking at all installed on the machine. ms 64 bytes from localhost (127.0.0.1):ģ packets transmitted, 3 packets received, 0% packet loss round-trip (ms) ![]() PING localhost: 56 data bytes 64 bytes from localhost (127.0.0.1): ![]() On Sun workstations, the command is typicallyġ27.0.0.1 in an MS-DOS window and it will stop by itself after four lines. On Unix, you can useġ27.0.0.1 with the statistics option and interrupt it after a few lines. The first command to enter on both the server and the client isĪddress and testing it will indicate whether any networking support is functioning at all. 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.9.2.2.1 Testing the networking software with ping 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 |