The following steps elaborate how to use the Ping utility to perform progressively more distant tests on your network connectivity.
Ping the loopback address – type ping 127.0.0.1
Successfully pinging the loopback address verifies that TCP/IP is both installed and configured correctly on the local client. If your loopback test fails, then it means IP stack is not answering. If any TCP drivers get corrupted, or if your network adapter is not functioning properly, or if any of the other service is interrupting IP , then lack of response might can occur. Open event viewer, and look for problems reported by setup or by the TCP/IP service.
Ping the local client – type ping
Successfully pinging with the local client's IP address verifies that the client was successfully added to your network. If you cannot successfully ping the local IP address after successfully pinging the loopback address, check that the local client's IP address is a valid IP address, check the routing table, and check network adapter driver.
Ping the default gateway – type ping
Successfully pinging with the default gateway of the local client verifies that you can properly communicate with the local subnet to your local host and your default gateway is also functioning properly. If you cannot successfully ping the default gateway after successfully pinging the local client, check the default gateway.
Ping the IP address of network device located on a remote network – type ping
Successfully pinging with the IP address of the remote host verifies that the local client can communicate with the remote host through a router. if the remote host is located across a high delay link such as satellite link, try using the -w (wait) parameter to specify a longer time out period than the default time out of four seconds.
If you cannot successfully ping the remote host IP address after successfully pinging the default gateway, this indicates that there is no respond from the remote host, or if there is any network hardware problem between the source host and the destination host. To rule out the possibility of a problem in the work hardware, ping to a different remote host on the same subnet where the first remote host is located.
Ping the host name of another host on a remote network – type ping
Successfully pinging with the name of the remote host verifies that ping can resolve the remote host name to an IP address. If you cannot successfully ping the remote host name after successfully pinging the IP address of the remote host, the problem is with host name resolution, but not with network connectivity. When pinging the host name of the target host, ping attempts to resolve the name to an address (first through a DNS server, and next through a WINS server, if one is configured), and then attempts a local broadcast. Check TCP/IP properties to see whether the client has DNS server and WINS server addresses configured, either typed manually or assigned automatically. If DNS and WINS server addresses are configured in TCP/IP properties, and if they appear when you type ipconfig/all, then try pinging with server addresses to ascertain whether they are accessible.
On a network that uses DNS for name resolution, if the name entered is not a Fully Qualified Domain Name (FQDN), the DNS name resolver appends the computer's domain name or name to generate the FQDN. Name resolution might fail if you do not use an FQDN for a remote name. These requests fail because the DNS name resolver appends the local domain suffix to a name that resides elsewhere in the domain hierarchy.
Link to this articule from your own website; just copy/paste this HTML:
Subscribe
