Search the VMware Knowledge Base (KB)
View by Article ID

Troubleshooting virtual machine network connection issues (1003893)

  • 42 Ratings
Language Editions


  • Virtual machines fail to connect to the network
  • There is no network connectivity to or from a single virtual machine
  • You cannot connect to the Internet
  • A TCP/IP connection fails to and from a single virtual machine
  • You may see one or more of the following errors:

    • Destination Host Unreachable
    • Network error: Connection Refused
    • Network cable is unplugged
    • Ping request could not find host (IP address/hostname). Please check the name and try again.
    • Unable to resolve target system name (IP address/hostname).


Validate that each troubleshooting step below is true for your environment. The steps provide instructions or a link to a document, for validating the step and taking corrective action as necessary. The steps are ordered in the most appropriate sequence to isolate the issue and identify the proper resolution. Do not skip a step.

  1. Ensure that the Port Group name(s) associated with the virtual machine's network adapter(s) exists in your vSwitch or Virtual Distributed Switch and is spelled correctly. If not, correct it using Edit Settings on the virtual machine and ensure that the Connected checkbox is selected.

  2. Ensure that the virtual machine has no underlying issues with storage or it is not in resource contention, as this might result in networking issues with the virtual machine. You can do this by logging into ESX/ESXi or Virtual Center/vCenter Server using the VI/vSphere Client and logging into the virtual machine console. For more information, see Troubleshooting a virtual machine that has stopped responding (1007819).

    Note: If you are experiencing network connectivity issues with the ESX/ESXi host or with multiple virtual machines, see ESX/ESXi hosts have intermittent or no network connectivity (1004109).

  3. Verify that the virtual network adapter is present and connected. For more information, see Verifying virtual network adapter is present and connected to the virtual machine (1003786).

  4. Verify that the networking within the virtual machine's guest operating system is correct. For more information, see Verifying the networking within a Windows based guest operating system (1003899) for Windows and Verifying the networking within a Linux based guest operating system (2022022) for Linux.

  5. Verify that the TCP/IP stack is functioning correctly. For more information, see Troubleshooting virtual machine TCP/IP connection issues (1007842).

  6. If this virtual machine was converted from a physical system, verify that there are no hidden network adapters present. For more information, see Networking Error: IP address already assigned to another adapter (1179).

  7. Verify that the vSwitch has enough ports for the virtual machine. For more information, see Network cable of a virtual machine appears unplugged (1004883) and No network connectivity if all ports are in use (1009103).

  8. Verify that the virtual machine's IPSec configuration is configured correctly and that it is not corrupted. For more information, see IPSec error within a Windows virtual machine (1000797).

  9. Verify that the virtual machine is configured with two vNICs to eliminate a NIC or a physical configuration issue. To isolate a possible issue:

    • If the load balancing policy is set to Default Virtual Port ID at the vSwitch or vDS level:

      • Leave one vNIC connected with one uplink on the vSwitch or vDS, then try different vNIC and pNIC combinations until you determine which virtual machine is losing connectivity.

    • If the load balancing policy is set to IP Hash:

      1. Ensure the physical switch ports are configured as port-channel. For more information on verifying the configuration on the physical switch, see Sample configuration of EtherChannel / Link aggregation with ESX/ESXi and Cisco/HP switches (1004048).
      2. Shut down all but one of the physical ports the NICs are connected to, and toggle this between all the ports by keeping only one port connected at a time. Take note of the port/NIC combination where the virtual machines lose network connectivity.

    • You can also check esxtop output using the n option (for networking) to see which pNIC the virtual machine is using. Try shutting down the ports on the physical switch one at at time to determine where the virtual machine is losing network connectivity. This also rules out any misconfiguration on the physical switch port(s).
If the problem persists after you have completed these steps:

Additional Information

To be alerted when this article is updated, click Subscribe to Document in the Actions box.


cannot-access-vm connect-vm manage-vm no-connectivity

See Also

Update History

11/11/2013 - Added vCenter Server 5.5 to product versions. 06/25/2012 - Added link to 2022022 for Linux operating systems 06/19/2012 - Updated for 5.x. Added error messages. 12/09/2011 - Added step to ensure that the Port Group name(s) associated with the virtual machine's network adapter(s) exists in the vSwitch or vDS 03/13/2015 - Added ESXi 6.0 and vCenter Server 6.0 to Products.

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.


  • 42 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? (4000 or fewer characters)

Please enter the Captcha code before clicking Submit.
  • 42 Ratings