What is causing problems with the VMware Bridged Network?
We investigated this particular issue by looking at various user reports and the repair strategies that are commonly used to fix this problem. Based on what we gathered, there are several common scenarios that are known to lead to this issue:
Method 1: Rebooting Vmnetbridge.sys via admin CMD
VMnetbridge.sys (VMware Bridge Control) can also cause this particular problem in instances where the file is incorrectly started or becomes glitched before it can facilitate communication between the host machine and the guest computer. If this scenario is applicable, chances are you will be able to resolve the issue by essentially restarting the bmnetbridge service via an elevated Command Prompt. Several affected users have reported that this procedure allowed them to fix the problem, as the host and guest machines started communicated the next time a VMware window was launched. Here’s a quick guide on rebooting vmnetbriddge.sys via an admin CMD: If the issue is still not resolved and you’re still encountering the same Bridged Network problem, move down to the next method below.
Method 2: Using a specific virtual network (VMnet0)
Several affected users have reported that for them, the issue was resolved entirely after they configured their WMware workstation to use a specific virtual network (VMnet0). As it turns out, if you leave the Network connection to Bridged, there’s a chance that the program will use the wrong one. In the vast majority of cases, VMnet0 is the correct virtual network that needs to be used in this case. Here’s a short guide on how to program VMware to use a custom virtual network (VMnet0): If the issue is still not resolved and you’re still having issues with the network bridge in VMware Workstation, move down to the next method below.
Method 3: Deselecting all adapters besides the physical network card
If you’re using Workstation Pro, and you’re experiencing no network connectivity inside your virtual machines while using a bridged connection, you will be able to resolve the issue by using the VMWare Virtual Network Editor to deselect all network adapters that are not essential to the network connection. Several affected users have reported that the host machine and the guest machine started sharing the internet connection moments after this modification was conducted. Important: This method will only be applicable if you’re using VMware Workstation Pro. The steps below can’t be replicated on VMware Workstation Player! Here’s a quick guide on how to do this: If you’re still encountering the same problem or this method wasn’t applicable to your particular scenario, move down to the next method below.
Method 4: Removing all unnecessary host network adapters
If you’re using VMware Workstation Player (the free version) and the method above wasn’t applicable, this is how you can do it from the free version. In the vast majority of case, the error occurs because the software has a lot of host network adapters to choose from when having to pick one for the bridged network connection. Often times, the software ends up choosing a network adapter that can’t facilitate a connection to the Internet, which ends up creating the issue that is discussed in this article. If this scenario is applicable, you can resolve the problem quite easily by making sure that the host adapters that are not necessary for this procedure are removed from the Automatic Bridging Settings menu. Here’s a quick guide on how to do this: If you’re still encountering the same problem, move down to the next method below.
Method 5: Removing VPN client from the host machine
As it turns out, this particular issue can also occur if you’re actively using a VPN connection to protect your anonymity on the web. Several affected users have reported that the bridged connection started working as expected as soon as they uninstalled their VPN client. Note: If you’re keen on using a VPN client, you can try different providers until you discover an option that doesn’t conflict with VMware Workstation. In most cases, the VPN client that is reported to conflict with VMware workstation is Endpoint Remote Access VPN, but there could be others. Here’s a quick guide on uninstalling your VPN client in order to resolve the bridged network issue:
Method 6: Disabling all VirtualBox network entries from Networking Connections
If you’ve been previously using Virtual box, keep in mind that you might be encountering issues if you make the switch to VMware (bridged mode). As it turns out, the adapter/s that are left behind by virtual box might cause problems with bridged connection inside VMware. If this scenario is applicable to your current situation and you want to use VMware, there are three ways forward:
Uninstall VirtualBox along with an adapter that was used by the software.Start using NAT with VMWareDisable every network entries belonging to VirtualBox from the Network Connections menu
Since this guide is about helping you use a bridged connection with VMware Workstation, we are going to focus on the third option since it’s the least intrusive. Here’s a quick guide on disabling all VirtualBox network entries to resolve the birding feature on VMware: If you’re still encountering the same problem, move down to the next method below
Method 7: Restoring Virtual Network Editor settings to the defaults
As it turns out, there’s one particular Windows 10 build that breaks the bridged connection feature on VMware Workstation. As it turns out, if you update to Windows 10 built 1703 or above while WMware is installed, the network bridging feature will become unusable unless manual action is conducted. This happens because this update deletes a couple of keys (VMnetDHCP and VMware NAT Service) which ends up effectively breaking the bridging feature inside VMWare Workstation. But as it turns out, you can rectify the damage very easily by forcing VMware to recreate the two registry keys by restoring the settings of the Virtual Network Editor to the default. Note: The steps below are only applicable for Vmware Workstation PRO users and can’t be replicated on VMware Player. Here’s a quick guide on how to do this: If this method wasn’t applicable or you’re still encountering this particular issue, move down to the next method below.
Method 8: Allowing VMware virtual machines from AVG’s firewalls (if applicable)
As it turns out, this particular issue can also occur if you’re using a 3rd party security (which includes a firewall) that is overprotective with the network connections that it manages. Several affected users have reported that they managed to resolve the issue after discovering that AVG firewall ( or a similar security solution) is responsible for their bridged mode problem in VMware. Update: It seems that this issue can also be caused by Bitdefender’s firewall. Since BitDefender doesn’t include an option that will allow virtual networks through their firewall, the only way, in this case, is to disable the firewall completely. If this scenario is applicable to your current situation and you’re using AVG Internet Security, you can resolve the issue swiftly by modifying AVG’s advanced settings to allow all virtual machines and traffic. Here’s how to do this: Note: if you’re using a different security suite and you think this method might be applicable, search online for specific steps on how to allow your virtual networks according to the firewall that you’re using.h
Fix: VMware Authorization Service is not RunningFix: VMware Operating System not FoundFix: VMware Workstation and Device/Credential Guard are not CompatibleNot Enough Physical Memory Error in VMware
