Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

Troubleshooting network connection failures (1008367)

Symptoms

You are experiencing these issues:

  • No network connectivity for a virtual machine
  • Cannot connect to the Internet from the guest operating system
  • Bridged, Host-only or Network Address Translation (NAT) networking fails

Purpose

This article helps you to determine the cause of networking problems affecting one or more virtual machines. The steps in this article address whether the networking has been misconfigured on the host operating system, guest operating system or virtual machine.

Resolution

Each step below provides instructions and a link to a document, for performing the step and taking corrective action as necessary. The steps are ordered in the most appropriate sequence to isolate the issue and to identify the proper resolution. They are also ordered in the most appropriate sequence to minimize data loss. After completing each step, check network connectivity again. Work through each troubleshooting step in order, and do not skip a step.
 
To troubleshoot a lack of network connectivity in a virtual machine:
  1. Verify that your virtual machine is using the right type of virtual networking (either Bridged, Host-only, or Network Address Translation (NAT)). For more information, see Understanding networking types in hosted products (1006480).

    Note: If a host machine is connected to a network using managed switches or routers, these devices may be configured to block unregistered MAC addresses. In this circumstance, any virtual machine using bridged networking is not able to communicate on the physical network. To resolve the issue, reconfigure the host machine, router, or use NAT networking instead.

  2. If automatic bridging is enabled in a bridged network, virtual network adapters may be binding to the wrong physical adapter or an adapter that is not connected to a valid network. To resolve the issue, manually assign an active physical network adapter to virtual network adapters. For more information see, Bridged networking does not work when loopback adapter is installed on host (1007250).

  3. Ensure that these processes are running. If not then start them manually
    • /usr/bin/vmnet-bridge on Linux hosts using Bridged networking.
    • /usr/bin/vmnet-natd and /usr/bin/dhcpd on Linux hosts using NAT networking.
    • vmnat.exe and vmnetdhcp.exe on Windows hosts using NAT or Bridged networking.

  4. Verify that the host and guest operating systems do not have any services or programs enabled or installed on them that may interfere with network connectivity. These services and programs include, but are not limited to:
    • Firewalls – Some firewalls may see network traffic from virtual machines as foreign to the host and block the traffic from reaching the physical network. To troubleshoot the connection issue, create exceptions for the virtual machine traffic in the firewall or disable or uninstall it.
    • Virtual Private Network (VPN) software – To troubleshoot the connection issue, disable or uninstall it.
    • Internet Protocol Security (IPsec) – To troubleshoot the connection issue, disable or uninstall it.

  5. On Windows host machines, reinstall the VMware Bridge Protocol:
    1. In Windows XP Click Start > Settings > Network and Dial-up Connections.
      In Windows Vista/7 Click Start > Control Panel > Network and Internet > View Network status and tasks > Change adapter settings.
    2. Right-click any network adapter icon and click Properties.
    3. Select VMware Bridge Protocol and click Uninstall.
    4. Click Install.
    5. Select Service and click Add.
    6. Select VMware Bridge Protocol and click OK.

  6. On Linux host machines using VMware Workstation version 6.5.0 or lower, reconfigure the network adapters by executing this command in a terminal window:

    /usr/bin/vmware-config.pl


  7. If your network does not provide Dynamic Host Configuration Protocol (DHCP), confirm that the static IP settings on the virtual machines are consistent with the addressing scheme on the physical LAN.
  8. For Workstation, restore the networking defaults. 

    To restore the networking defaults, click Edit > Virtual Network Editor and then click Restore defaults.

  9. Rebuild your virtual networking stack by reinstalling the VMware product.

If the issue continues to exist after trying the steps in this article:

Additional Information

The Internet connectivity may not work correctly in the virtual machines, if the host machine is set to use static IP address for the DNS servers. Ensure to use the same static DNS server IP on the virtual machine as the host machine.

See Also

Update History

01/20/2011 - Re-wrote and re-ordered steps. 03/27/2012 - Added step to restore networking default in Workstation 08/03/2012 - Added information to use the same static DNS server IP on the virtual machine and the host machine

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.

Feedback

  • 155 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)
  • 155 Ratings
Actions
KB: