Troubleshooting blocked inbound network traffic on Windows Vista or later after installing a VMware product
search cancel

Troubleshooting blocked inbound network traffic on Windows Vista or later after installing a VMware product

book

Article ID: 309968

calendar_today

Updated On:

Products

VMware Desktop Hypervisor

Issue/Introduction

This article describes how to re-establish inbound network traffic to a computer running Microsoft Vista SP1, Server 2008, or Windows 7 that used to receive this traffic but is no longer able to after a VMware product was installed.

Symptoms:
  • Inbound network traffic stops after installing a VMware product.
  • Networking fails.
  • Blocked TCP/IP ports.
  • Problems with networking on a Windows Vista, Server 2008, or Windows 7 host.


Environment

VMware Player 6.x (Windows)
VMware Workstation Player 14.x (Windows)
VMware Player 2.x (Windows)
VMware Workstation Player 12.x (Windows)
VMware Workstation 9.x (Windows)
VMware Player 7.x (Windows)
VMware Workstation 7.x (Windows)
VMware Player 3.x (Windows )
VMware Player Pro 7.x (Windows)
VMware Player 5.x (Windows)
VMware Workstation Pro 14.x (for Windows)
VMware Workstation 11.x (for Windows)
VMware Workstation 6.x (Windows)
VMware Workstation 10.x (Windows)
VMware Workstation 8.x (Windows)
VMware Player 4.x (Windows)
VMware Workstation Pro 12.x (Windows)

Resolution

In some cases, the installation of a VMware product to a computer with a Microsoft Vista or later operating system prevents all inbound networking traffic from reaching the computer. This is caused by the Windows Firewall assigning the VMware virtual NICs to the Public network.

Reconfigure the Windows Firewall

This procedure requires extensive knowledge of the Windows operating system and its implementation of the Windows Firewall. Doing this ensures a permanent solution resulting in no unexpected behaviour in either the Windows operating system or the VMware product in use. Any description of the tasks required are beyond the scope of this article. For more information, refer to the Windows operating system documentation.

Notes:

  • Only perform this if you have an in-depth understanding of Windows Firewall.
  • Modifying the access rules for the Public network will affect all NICs that belong to the Public network.

Move the VMware virtual NICs to the Private network

This procedure is simple to perform and has the least impact on both the Windows operating system and the VMware product in use. However, after any reboot of the operating system the NICs are moved back to the Public network again. Using this procedure requires supervision of the operating system to ensure that it is performed after every reboot.

Note: This solution does not apply to Windows 7.

To move the VMware virtual NICs to a Private network:

  1. Click the Start globe and go to Control Panel > Network and Internet > Network and Sharing Center.
  2. Click Customize.
  3. Select Private.
  4. Click Next.
  5. Click Close.

Disable the VMware virtual NICs

This procedure is simple to perform, but it prevents Host Only networking from functioning in any virtual machine. If Host only networking is not required, this is the simplest and most permanent procedure.

Note: This procedure must be performed on the host machine.
 
To disable the VMware virtual NICs:
  1. Click Start > Control Panel > Network and Sharing Center.
  2. Click Manage network connections.
  3. Click VMware Network Adapter / VMnet1 / Unidentified network.
  4. Click Disable this network device.
  5. Click VMware Network Adapter / VMnet8 / Unidentified network.
  6. Click Disable this network device.

Redefine the VMware virtual NICs as endpoint devices

This procedure is permanent and allows for the continued use of Bridged, NAT, and Host Only networking. However, doing this causes the VMware virtual NICs to disappear from the Network and Sharing Center, even though they remain visible under Network Connections. This also causes the VMware virtual NICs to be exempt from all Windows Firewall access rules. When implemented, the control of virtual machine network access must be done from the guest operating system of each virtual machine. This bypasses the default security model of Windows with respect to the the VMware virtual NICs, and the implications of using this procedure must be carefully considered.

To redefine the VMware virtual NICs as endpoint devices:

  1. Click Start > Run, type regedit and, click OK.
  2. Navigate to HKEY_LOCAL_MACHINE > System > CurrentControlSet > Control > Class > {4D36E972-E325-11CE-BFC1-08002BE10318}.

    Caution: VMware recommends that you back up this registry key before proceeding. To backup the registry:
     
    1. If {4D36E972-E325-11CE-BFC1-08002BE10318} is not still highlighted, click it.
    2. Go to File > Export.
    3. Pick a location and name for the Registration File (*.reg) .
    4. Click Save.
       
  3. Click 0000.
  4. Look at the content of the Data field associated with the DriverDescentry.
  5. If you see VMware Virtual Ethernet Adapter for VMnet<x>, where<x> is replaced by a number, then:
     
    1. Right-click an empty space in the right content pane.
    2. Click New > Dword.
    3. Type *NdisDeviceType and press Enter.

      Note: Be sure to include the asterisk (*) at the beginning of the entry.
       
    4. Double-click *NdisDeviceType.
    5. Type 1 and press Enter.
       
  6. Repeat steps 4-6, replacing 0000 in step 4 with the next entry in numerical order, until you have reached the end of all numerical entries.
  7. Follow the Disable the VMware virtual NICs section of this article above.
  8. Repeat step 7 but click Enable this network device instead.

THE CONTENT OF THIS ARTICLE IS PROVIDED "AS-IS," AND TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, VMWARE DISCLAIMS ALL OTHER REPRESENTATIONS AND WARRANTIES, EXPRESS OR IMPLIED, REGARDING THIS CONTENT, INCLUDING THEIR FITNESS FOR A PARTICULAR PURPOSE, THEIR MERCHANTABILITY, OR THEIR NONINFRINGEMENT. VMWARE SHALL NOT BE LIABLE FOR ANY DAMAGES ARISING OUT OF OR IN CONNECTION WITH THE USE OF THIS CONTENT, INCLUDING DIRECT, INDIRECT, CONSEQUENTIAL DAMAGES, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF VMWARE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.


Additional Information

For more information about Windows Vista or 2008, endpoint devices and how they relate to the Windows Firewall, see the Microsoft article Keywords Not Displayed in the User Interface.
 
Note: This link was correct as of September 5, 2013. If you find the link is broken, please provide feedback and a VMware employee will update the link.
Solução de problemas de tráfego de rede de entrada bloqueado no Windows Vista ou posterior, após a instalação de um produto VMware
Resolución de problemas de bloqueo del tráfico de red entrante en Windows Vista o posteriores luego de instalar un producto VMware
VMware 製品のインストール後に Windows Vista 以降で受信ネットワーク トラフィックがブロックされる問題のトラブルシューティング
安装 VMware 产品之后，在 Windows Vista 或更高版本上排除阻塞的入站网络流量的故障

Powered by Wolken Software