Testing network connectivity with the Ping command
Purpose
For troubleshooting purposes, it may be necessary to test network connectivity between different components of your network. This article provides you with the steps to perform a ping test on your network from Windows, Linux, and ESX Server hosts.
Resolution
Testing with Ping from a Windows Host
To initiate a ping test from a Windows host:
Click Start>Run.
Type cmd in the run field.
Click OK.
In the command prompt window, type ping <server> , where <server> is the hostname or IP address of the server that you want to ping.
Press Enter.
A successful ping response is similar to the following:
C:\>ping server
Pinging server with 32 bytes of data:
Reply from server: bytes=32 time<1ms TTL=64 Reply from server: bytes=32 time<1ms TTL=64 Reply from server: bytes=32 time<1ms TTL=64 Reply from server: bytes=32 time<1ms TTL=64
Ping statistics for server: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms
C:\>
An unsuccessful ping response is similar to the following:
Ping statistics for server: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\>
Note: If you do not see a response when pinging by the hostname of the server, initiate a ping to the IP address. Initiating a ping to the IP address allows you to determine if the problem is a result of an issue with hostname resolution.
Testing with Ping from a Linux Host
To initiate a ping test from a Linux host:
Open a Terminal to the Linux command shell.
In the command shell window type ping <server> , where <server> is the hostname or IP address of the server that you want to ping.
Press Enter.
Note: To stop the ping, press Ctrl + C.
A successful ping response is similar to the following:
[root@server]$ ping server PING server (10.0.0.1) 56(84) bytes of data. 64 bytes from server (10.0.0.1): icmp_seq=0 ttl=64 time=0.025 ms 64 bytes from server (10.0.0.1): icmp_seq=1 ttl=64 time=0.029 ms 64 bytes from server (10.0.0.1): icmp_seq=2 ttl=64 time=0.032 ms 64 bytes from server (10.0.0.1): icmp_seq=3 ttl=64 time=0.028 ms
An unsuccessful ping response is similar to the following:
[root@server]$ ping server PING server (10.0.0.1) 56(84) bytes of data.
--- server ping statistics --- 4 packets transmitted, 0 received, 100% packet loss, time 3017ms
[root@server]$
Note: If you do not see a response when pinging by the hostname of the server, initiate a ping to the IP address. Initiating a ping to the IP address allows you to determine if the problem is a result of an issue with hostname resolution.
Testing with Ping from an ESX Server Console
To initiate a ping test from the console of an ESX Server host:
Press Alt + F1 to access the ESX Server login prompt.
Login to the ESX Server as root .
In the command shell type ping <server> , where <server> is the hostname or IP address of the server that you want to ping.
Press Enter.
Note: To stop the ping, press Ctrl + C.
A successful ping response is similar to the following:
[root@server]$ ping server PING server (10.0.0.1) 56(84) bytes of data. 64 bytes from server (10.0.0.1): icmp_seq=0 ttl=64 time=0.025 ms 64 bytes from server (10.0.0.1): icmp_seq=1 ttl=64 time=0.029 ms 64 bytes from server (10.0.0.1): icmp_seq=2 ttl=64 time=0.032 ms 64 bytes from server (10.0.0.1): icmp_seq=3 ttl=64 time=0.028 ms
An unsuccessful ping response is similar to the following:
[root@server]$ ping server PING server (10.0.0.1) 56(84) bytes of data.
--- server ping statistics --- 4 packets transmitted, 0 received, 100% packet loss, time 3017ms
[root@server]$
Note: If you do not see a response when pinging by the hostname of the server, initiate a ping to the IP address. Initiating a ping to the IP address allows you to determine if the problem is a result of an issue with hostname resolution.
