Using ping

When troubleshooting, you can use ping to verify IP-level connectivity. You should perform the following steps when using ping:

1. Ping the loopback address to verify that TCP/IP is configured correctly on the local computer - ping 127.0.0.1
2. Ping the IP address of the local computer to verify that it was added to the network correctly - ping IP_address_of_local_host
3. Ping the IP address of the default gateway to verify that the default gateway is functioning and that you can communicate with a local host on the local network - ping IP_address_of_default_gateway
4. Ping the IP address of a remote host to verify that you can communicate through a router - ping IP_address_of_remote_host

Can't ping outside IP or name

If you can't ping outside IP, make sure you have correct gateway. If you can't ping outside computer name or web name, check the DNS settings.

Can't use ping

If you cannot use ping successfully at any point, confirm that:

1)The computer was restarted after TCP/IP was configured.
2) The IP address of the local computer is valid and appears correctly on ipconfig /all.
3) IP routing is enabled and the link between routers is operational.
4) For the security reasons, many organizations block the return of ICMP (ping) packets so that ping or tracert may not be possible to obtain a response.

Error code 65, 10043 and 10050, transmit failed

Symptoms: When using ping command, you may receive either of the following: "Transmit failed, error code 65" or "Transmit failed, error code 10050"

Resolutions: make sure your firewall or router doesn't disable ping and to allow ICMP Echo and  Echo Reply packets.

This is name resolution issue if you can ping IP but not computer name

The ping command uses Windows Sockets-style name resolution to resolve a computer name to an IP address, so if pinging by address succeeds, but pinging by name fails, then the problem lies in address or name resolution, not network connectivity.