Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

Skip to main content

My Subscriptions

Loading

Knowledge Base

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

Last Updated: 3/23/2024Categories: How toTotal Views: 75566Language:
English

4 like this article

Subscribe to get an email
newsletter with new updates

4 people found this helpful Please provide article feedback:

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.

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 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:

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.

Related 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 或更高版本上排除阻塞的入站网络流量的故障

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Workstation Pro

VMware Workstation Player

VMware Workstation

VMware Player

Related Versions:

VMware Workstation Pro 14.x (for Windows)

VMware Workstation Pro 12.x (Windows)

VMware Workstation Player 14.x (Windows)

VMware Workstation Player 12.x (Windows)

VMware Workstation 9.x (Windows)

VMware Workstation 8.x (Windows)

VMware Workstation 7.x (Windows)

VMware Workstation 6.x (Windows)

VMware Workstation 11.x (for Windows)

VMware Workstation 10.x (Windows)

VMware Player Pro 7.x (Windows)

VMware Player 7.x (Windows)

VMware Player 6.x (Windows)

VMware Player 5.x (Windows)

VMware Player 4.x (Windows)

VMware Player 3.x (Windows )

VMware Player 2.x (Windows)

view all

Take Our Survey

Was this article helpful?

YES

NO

Copyright © 2005-2024 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.

Terms of Use

Your California Privacy Rights

Privacy

Accessibility

Cookie Settings

Support Assistant