When TCP/IP protocol is used, incorrect TCP/IP settings (such as an incorrect IP address or an incorrect subnet mask) can cause communication problems. For example, a virtual machine may not be able to ping its own IP address.
If you are having communication problems, verify your TCP/IP settings.
To verify TCP/IP settings:
To determine basic TCP/IP settings for Windows, run the command:
ipconfig
To determine basic TCP/IP settings for Linux, run the command:
Note: If the ipconfig or theifconfig command does not produce any output, ensure that the NIC is enabled.
From the output of the ipconfig or theifconfig command, verify that the IP address and subnet mask are correct.
Note: If you are unsure of the correct values, contact your network administrator.
If DHCP is configured, confirm that DHCP is assigning the IP address correctly by renewing the IP address. F rom the command prompt in Windows or from a Linux terminal, run the command:
ipconfig /renew
Pinging the virtual machine IP address
If you can successfully ping the loopback address, try to ping your own IP address. From a command prompt, run the command:
ping <IP address>, where <IP address> is your computer's IP address
For example:
ping 10.10.10.30
The output of the ping looks similar to:
Pinging 10.10.10.30 with 32 bytes of data: Reply from 10.10.10.30: bytes=32 time=2ms TTL=128 Reply from 10.10.10.30: bytes=32 time<1ms TTL=128 Reply from 10.10.10.30: bytes=32 time<1ms TTL=128 Reply from 10.10.10.30: bytes=32 time<1ms TTL=128
