Support > Knowledge Base
Knowledge Base

Search the Knowledge Base: |
Search the Knowledge Base: |
Testing network connectivity with the Ping command
Purpose
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
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
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:
C:\>ping server
Pinging server with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
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),
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
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]$
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 the following:
[root@server]$ ping server
PING server (10.0.0.1) 56(84) bytes of data.
PING server (10.0.0.1) 56(84) bytes of data.
--- server ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3017ms
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
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]$
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 the following:
[root@server]$ ping server
PING server (10.0.0.1) 56(84) bytes of data.
PING server (10.0.0.1) 56(84) bytes of data.
--- server ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3017ms
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.
Feedback
Actions
- KB Article: 1003486
- Updated: Aug 14, 2009
- Products:
VMware ACE
VMware Converter
VMware ESX
VMware ESXi
VMware Server
VMware VirtualCenter
VMware Workstation
VMware vCenter Lab Manager
VMware vCenter Server
VMware vCenter Stage Manager - Product Versions:
VMware Converter 3.0.x
VMware ESX 2.5.x
VMware ESX 3.0.x
VMware ESX 3.5.x
VMware ESX 4.0.x
VMware ESXi 3.5.x Embedded
VMware ESXi 3.5.x Installable
VMware ESXi 4.0.x Embedded
VMware ESXi 4.0.x Installable
VMware Server 1.0.x (Linux)
VMware Server 1.0.x (Windows)
VMware Server 2.0.x (Linux)
VMware Server 2.0.x (Windows)
VMware VirtualCenter 2.0.x
VMware VirtualCenter 2.5.x
VMware Workstation 5.x (Linux)
VMware Workstation 5.x (Windows)
VMware Workstation 6.x (Linux)
VMware Workstation 6.x (Windows)
VMware vCenter Converter 4.0.x
VMware vCenter Converter Standalone 4.0.x
VMware vCenter Lab Manager 2.5.x
VMware vCenter Lab Manager 3.0.x
VMware vCenter Lab Manager 4.0.x
VMware vCenter Server 4.0.x
VMware vCenter Stage Manager 1.0.x

