VMware
 

Knowledge Base

Search the Knowledge Base:
Products:
Search In:
 

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:
  1. Click Start>Run.
  2. Type cmd in the run field.
  3. Click OK.
  4. In the command prompt window, type ping <server> , where <server> is the hostname or IP address of the server that you want to ping.
  5. 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:
 
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:
  1. Open a Terminal to the Linux command shell.
  2. In the command shell window type ping <server> , where <server> is the hostname or IP address of the server that you want to ping.
  3. 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
--- 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 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:
  1. Press Alt + F1 to access the ESX Server login prompt.
  2. Login to the ESX Server as root .
  3. In the command shell type ping <server> , where <server> is the hostname or IP address of the server that you want to ping.
  4. 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
--- 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 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.

Feedback

Rating: 1 - Lowest 2 3 4 5 - Highest (3 Ratings)   

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (2000 or fewer characters)
Submit
Rating: 1 - Lowest 2 3 4 5 - Highest (3 Ratings)   
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