Knowledge Base
The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides

|
Testing network connectivity with the ping command (1003486)
Purpose
Resolution
Testing with Ping from a Windows Host
To initiate a ping test from a Windows host:
-
Click Start > Run, type cmd, then click OK.
-
At the command prompt window, run:
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:
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:
C:\>ping server
Pinging server with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
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:
[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
--- server ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3092ms
rtt min/avg/max/mdev = 0.025/0.028/0.032/0.005 ms, pipe 2
[root@server]$
An unsuccessful ping response is similar to:
[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/ESXi host:
To initiate a ping test from the console of an ESX/ESXi host:
-
Log in as root to the ESX/ESXi service console through iLO/DRAC. To log in to ESXi hosts using SSH, see Tech Support Mode for Emergency Support (1003677) and Using Tech Support Mode in ESXi 4.1 and 5.0 (1017910).
-
Press Alt + F1 to access the ESX login prompt.
-
Log in to the ESX host as root.
-
In the command shell, type ping <server>
W here <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:
[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
--- server ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3092ms
rtt min/avg/max/mdev = 0.025/0.028/0.032/0.005 ms, pipe 2
[root@server]$
An unsuccessful ping response is similar to:
[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.
Additional Information
For further troubleshooting, see:
Tags
See Also
- Verifying network links
- Verifying ESX host networking configuration on the service console
- Diagnosing the vSphere/Virtual Infrastructure Client when it fails to connect to vCenter Server/VirtualCenter
- Troubleshooting virtual machine network connection issues
- Verifying the networking within a Windows based guest operating system
- ESX/ESXi hosts have intermittent or no network connectivity
- Troubleshooting VMware Data Recovery connectivity
- Testar a conectividade da rede com o comando ping
- Verifying the networking within a Linux based guest operating system
Request a Product Feature
To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.
Actions
KB:
- Updated:
- Categories:
- Languages:
- Product Family:
- Product(s):
- Product Version(s):

