Knowledge Base

|
Troubleshooting blocked inbound network traffic on Windows Vista or later after installing a VMware product
Purpose
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.
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:
- Click the Start globe and go to Control Panel > Network and Internet > Network and Sharing Center.
- Click Customize.
- Select Private.
- Click Next.
- Click Close.
Disable the VMware virtual NICs
This procedure is simple to perform, but it prevents both NAT and Host Only networking from functioning in any virtual machine. Only Bridged networking is available. If neither NAT nor Host only networking is required, this is the simplest and most permanent procedure.
To disable the VMware virtual NICs:
- Click Start > Control Panel > Network and Sharing Center.
- Click Manage network connections.
- Click VMware Network Adapter / VMnet1 / Unidentified network.
- Click Disable this network device.
- Click VMware Network Adapter / VMnet8 / Unidentified network.
- 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:
- Click Start > Run, type regedit and, click OK.
- 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:
- If {4D36E972-E325-11CE-BFC1-08002BE10318} is not still highlighted, click it.
- Go to File > Export.
- Pick a location and name for the Registration File (*.reg) .
- Click Save.
- Click 0000.
- Look at the content of the Data field associated with the DriverDescentry.
- If you see VMware Virtual Ethernet Adapter for VMnet<x>, where<x> is replaced by a number, then:
- Right-click an empty space in the right content pane.
- Click New > Dword.
- Type *NdisDeviceType and press Enter.
Note: Be sure to include the asterisk (*) at the beginning of the entry.
- Double-click *NdisDeviceType.
- Type 1 and press Enter.
- 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.
- Follow the Disable the VMware virtual NICs section of this article above.
- 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
Tags
accessing-network connection-fails-network connect-network faulty-network-adapter firewall-policy incompatible-network-adapter misconfigured-firewall network-connection network-connection-fails network-connectivity-issues reconfigure-networking separate-network windows-firewall windows-registry windows-7
Update History
Request a Product Feature
- KB Article:
- Updated:
- Categories:
- Product Family:
- Products:
- Product Versions:

