Network Bridge Mode Not Working Windows 10 Host

[twistedau]

Running VMware Workstation Pro 14 (14.1.1 build-7528167). None of my guest VM's can contact my host machine, and my host machine cannot contact the guest machines. This occurs when I'm using bridged mode for the guest NIC's. Other machines on my network can contact the guest VM's and the guest VM's can contact other machines on my network; they also have Internet access. This seems to just be guest to host and host to guest communication issues. If I switch from bridged to host only or NAT it works OK. I've tried to uninstall>reboot>reinstall VMware workstation. I've tried resetting the network settings to default in the Virtual network app. I can see the VMware bridge driver on my host machines physical NIC. I've tried uninstalling and reinstalling it. I've turned off the firewalls on both machines.

[admin]

Open a cmd as admin and run

net stop vmnetbridge

net start vmnetbridge

Sometimes that helps

Regards,

Randhir

If you found my answers useful please consider marking them as Correct OR Helpful

[twistedau]

Thanks for the tip, it did not work unfortunately :smileysad:

[cloudsuresh]

Hi ,

May I know   ip configuration details about  your physical and virtual configuration details.

If possible any filters or policies or vlan details.

I believe that the problem is related to network address mostly.

For example ip address, subnetmask, default gateway,network address, vlan address.

The next step will be related to updates, patches, compatibility, hardware issues.

If you apply firewall you can ping but you can't access internet or other networks.

[joseef]

Thanks very helpful! 

[zzzhhh1]

These commands are invalid.

Don't fill up the forum with misinformation, especially if you are an admin.

[Mo Alhroub]

The poster said open a cmd as admin (i.e a windows cmd terminal) . You opened a Linux terminal. Those commands are valid.

[MacFred]

Try this

1. Add Administrator to the local rights group "Network Configuration Operators"

2. And start Virtual Network Editor" and "Restore Defaults"

Good Luck

Fredrik

[mrkurvaa]

Bridged network not working , can't find any working solution.

i'am having pretty much the same probleme .
I have tryed to repair the install of my vmware 12 pro then re install , then upgrade to vmware 14 pro and re install open-vm-tools . Still no connection

I have tryed to set my network cart from automatic to      PCIe .. didnt work .
Everything work well on NAT network but bridge is broken , cause of the last update of win 10 ?
Vmnet0 dont get any connection ither

when i ping on google dns that's what i'm getting

If any one is having the same probleme please help me to solve this probleme , i have been looking for the solution during the two last days it's very ennoying .

[Michal Malanowski]

Hi, this is something I lost my respect to VMWare and Microsoft to.

But I found the resolution.

It works when you have installed Workstation, not Player, but I undrestand you have Workstation.

So: if you need bridged connection, simply: remove all others: VMnet1 and VMnet8. Leave VMnet0 and... voila!

Now I am looking for resolution in Player, not Workstation, but I am enormously less stressed :smileyhappy:

Good Luck!

[Alan49]

I fixed this issue by changing the settings in the VMWare Virtual Network Editor for the bridged VMnet0 port from Automatic Settings to the manually choosing the wired Ethernet connection for my computer.  

[grexdevops]

I had a similar problem and found the solution.  I had created a VM with vmware player trial on windows 10 and it worked.  I purchased workstation pro and installed.  When I ran the same VM with workstation, there was no network connectivity at all.  I had network access if I changed to NAT, but not as bridged.  However, I need bridge.

Thanks to GreckiSAS​​I was able to find the solution.

-- Be sure your vm is stopped.

--Run the VMWare Virtual Network Editor

(click start and search for Virtual Network Editor)

-- Run it as administrator (or click the button at the bottom of the screen that says, "change settings." VMNet0 will dislpay when running as administrator. Otherwise, it will not be visible)

-- Highlight VMNet0 and click on "Automatic Settings"

-- You will see a list of adapters. De-select all but the physical network card. (When I set up up with player, I had selected only the 1.  After install of workstation, all of the items were checked.)

-- Click "OK"

-- Click "Ok"

-- Start the VM and test.

[byunkook0]

Some of my VMs were created 10 years ago and I have been upgrading VMware workstation version.

In version 12, restore default fixed the bridge issue.

in version 14, following GreckiSASI's instruction fixed the issue.

[monkeynut]

These things are difficult to diagnose without actually being in front of the machines as important things can be missed. From what you have said the problem is with only the one machine not being reachable. Now if I understand correctly if you use NAT mode everything works but with bridged mode it doesn't. What jumps out at me is 'Firewall rules' as with NAT mode you are using existing addresses but with bridged you'll get new IP addresses via DHCP. So Maybe you need a Firewall rule on the 'host' to allow your new IP addresses through it.

Have fun,

MN

[TedChurch]

Thanks.  I had a similar problem when I moved my lab PC to a new location with a different IP DHCP network to bridge within.  Also compounding my issue was that my Win10 onboard 1Gb ethernet adaptor failed.  I added a new 2.5 Gb ethernet nic and everything works great again.

[qwanzaden]

grexdevops​ answer [solved] it for me.
Host: Windows 10 Version 1803

Guest: Fedora 29

VMware Workstation 15 Pro, version 15.0.2

[mtk]

not for me.  i'm on 1809 and just installed and removed the march cumulative update.  now my lenovo with an attached usb keyboard drops keys or repeats keys.  and nothing i do gets bridged networking back on for my fedora 29 guest.  before this, everything was working.  sigh.

[mtk]

they fixed the stuttering problem but i still don't have networking ("network is unreachable").  this is true for both a fedora 29 guest and a centos 7 guest.  so the problem isn't OS-specific.  i've done all the typical stuff (reset the virtual interfaces) but it had no effect.  i haven't tried to reinstall workstation yet.  in addition to the networking problem, booting fedora 29 doesn't work smoothly.  the login screen doesn't show up unless i pause & restart the VM.  centos 7 works without a problem.

/mark

[farahJm]

oh gush .. you are the saver hahhaha thank you 

[jeffbagwell]

It seems in my case I had a lot of virtual adapters messing up everything. Doing the suggested solution by Grexdevops and only checking the physical adapters was the right solution to my bridge mode issues. Thanks

[davidmillsom]

Thanks. That worked for me.

 

[RafaelBR2]

Thank you for the answer! Today I had this problem, tried everything and nothing worked! Thanks to you finally worked!

[SD_Tech]

I have been banging my head against the wall for many hours trying to fix this issue, I tried everything in this post more than once and still was unable to fix it... UNTIL NOW!

 

For me the problem was the DHCP server from my home network wasn't serving the VM an IP address.  Setting the IP address manually was the final thing that fixed it for me.  Keep in mind, I also did everything else on the list, so it could also have been one of those things in conjunction with the manual IP address.

After all the time I spent on this, I HAD to share, because no guide or post I read mentioned manually setting the IP address.

[shinnok27]

WIshed I had found this two hours ago. 

[randomguy2]

This is the answer.  Beware of other hypervisors and their adapters.  In my case, I also had VirtualBox installed and I had to uncheck its adapter in the VMware Virtual Network Editor program.

[PaulVenice]

I had the same problem. Bridge mode didn't work on my Win10 host. None of the solutions listed here or mentioned elsewhere worked. Here is how I got it working. The Ethernet network adapter on my host computer was configured for a static IP. When I changed it to DHCP bridge mode worked. The strange thing is that my host was connected to the LAN with WIfi which was using DHCP.  The Ethernet was disconnected but using static IP. I had even set Workstation bridge mode to use the wireless adapter but the unconnected Ethernet with it's static IP was keeping bridge mode from working. I hope this solution helps some others.

Paul

[ifly3years]

maybe help someone,

i have the diferent thing.......

host is  wifi (dhcp)， and the bridged mode cant work when vm net use dhcp,

but ,when i change the vm net to a static ip, i can use the internet.

[shawarma_man]

Wow after I tried for several hours and trying all solutions, your solution was the last one I was gonna try AND IT WORKED, Thanks a lot.

[mekkano]

I’m glad it helped you. Digging’ deeper the issue is caused by a SonicWall filter (DNE LIghtweight Filter) on the NIC adapter you use for bridging. So you can just open NIC’s properties and uncheck that filter so you do not have to uninstall SonicWall client and when you need vpn connectivity just check it again of course this will bring back the issue. 

I hope this helps too. 

Greetings 

[Gustavo Giampaoli]

This was the cause of the problem in my case:

[mekkano]

I’m glad it helped you. Digging’ deeper the issue is caused by a SonicWall filter (DNE LIghtweight Filter) on the NIC adapter you use for bridging. So you can just open NIC’s properties and uncheck that filter so you do not have to uninstall SonicWall client and when you need vpn connectivity just check it again of course this will bring back the issue. 

I guess this issue can be also caused by another filter installed by antivirus or another vpn client.

I hope this helps too. 

Greetings 

[FLimaK]

Thanks  ,

I had walked all the solutions on this thread and my solution was based on your post.

 

"I’m glad it helped you. Digging’ deeper the issue is caused by a SonicWall filter (DNE LIghtweight Filter) on the NIC adapter you use for bridging. So you can just open NIC’s properties and uncheck that filter so you do not have to uninstall SonicWall client and when you need vpn connectivity just check it again of course this will bring back the issue. 

I guess this issue can be also caused by another filter installed by antivirus or another vpn client."

 

I work with several VPN clients, and they make some mess with my connections, even Checkpoint or other VPN clients does not work when Forcepoint client is active.

Unchecking the Forcepoint VPN driver on my real physical wi-fi adapter resolved the problem.

 

 

Below is a link to other bridge network problems I've found that could help others too, wich summarizes various solutions.

https://www.minitool.com/backup-tips/vmware-bridged-network-not-working.html

[Keeper306]

Tried a lot of things, but eventually i resolved this problem by removing checkpoint vpn client from my Host. Then i restarted host and it started working.

Now i can ping my VM from host and vice versa with bridged network.

Maybe it can help somenone else.

[sthomas170]

I found the following worked in Windows 10 and Vmware Workstation Version 10. I had to add vmware.exe to the allowed applications in the FW. I then reset the network back and then NAT addressing worked on a CentOS Version 7 VM.

[mekkano]

In my case I had SonicWall VPN client installed on my W10, removing it solved the problem

[guilhbernardes]

this worked for me! Thank you!

[mlopez2305]

I have the same issue working with windows 10 host and several virtual machines bridging over the wifi adapter of my laptop. Doing troubleshooting I install wireshark to see the packets detail. The problem is that the mac address of any virtual machine is using the host mac address (I don't know why) maybe a bug. So for all other pc's working in the same LAN arp mapping for any VM correspond to the mac address of the host. I will try the advice posted here to see if this help and let you know.

[mlopez2305]

nothing works, still has the same problem.

[mlopez2305]

I has disabled windows firewall and worked for me, now I can see the right mac address for the virtual machines

[TheQuestion]

I has disabled windows firewall and worked for me, now I can see the right mac address for the virtual machines

So then what would be the solution to this problem?

[cnhi]

I am testing Workstation Player (non-commercial) 14.1.2 and 15.5 on Windows 10 and Windows Server 2012 R2.

I chose Bridge mode and everywhere virtual machines assigned DHCP IP from workstation player = 192.168.200.xxx so it is like NAT setting. Bridge mode not working.

I don't know why VMs don't assigned IP from router/gateway - same class address like host.

[GB998877]

I had what I think is the same problems as you, NAT fine to external, but bridged only connection is to other VMs on the same subnet, nothing outside the physical host.

Using VM Workstation 15.5.0 build-14665864

What I found was that there was crap in the .vmx file left over from a previous version of workstation, resulting in  god knows what entries for the ethernet adapter.

What I had to do was

1 - Shut the VM down

2 - Edit and remove all network cards from the VM within VMworkstation

3 - Remove the VM from the inventory

4 - Edit the .vmx file of the guest using notepad and delete all lines with reference to ethernet0. (there were about 6)  (maybe make a copy of the .vmx file first just in case)

5 - Reattach the VM to the inventory

6 - Add a new network card

After then powering up the VM it got an IP from the DHCP server on the router and was able to ping out to the router.

Hope that's of some help

[cnhi]

Thank you very much - this is solution for my issue!!!

[DannyDannyDan]

Thank you very much  !

 

[ptsdon]

I have struggled with this issue, intermittently, for a long time. I have read several posts. Your remedy nailed it! Thank you so much! I rate your post 10 out of 10 for helpfulness.

[SHoldgaard]

Hi,

I had a similar problem and tried uninstallation VMware Workstation, updating VMware tools, resetting the network settings for both the virtual machine, VMware Workstation under Edit => Virtual Network Editor and lots of other thing.

The solution was:

Added a new VMware virtual appliance with the old disk and after that the network was running smoth again. 

/Sören

[eminempt]

Guys, for me it worked just fine by defining the IP address, the gatway and the DNS servers (as per my router's configurations)

[Alan49]

Please explain with a little more detail.  Thanks.

[ryanman]

I have been reading and trying solutions posted but I am having the same or similar problems. My VM's are obtaining an IP from the router's DHCP on a bridged connection. I also have only selected the one network card for the bridge (physical ethernet). My VM's can connect to the internet. I cannot connect to any of the VMs from the host machine using the IP address assigned by the router, for any port (80, 22, 3389, etc.) and I cannot ping them either. They also cannot talk to each other. This issue seems to be bidirectional (host and guest). 

 

If I switch them to a NAT or host-only, they can talk to each other but still cannot reach the host machine and the host machine cannot reach any of the guest VMs over IPv4. I am not bothering with IPv6 right now. One thing at a time.

[Spleanify_AT]

i have excactly the same Problem aus Ryanman. Do you have any solution therfore?

[robertstritzing]

solution was (for vmware workstation 16 player):
- configure bridge network adapters (only leave your real used NIC enabled)
- delete network adapter from VM config
- add network adapter again

then i got a real ip address and network/internet was working.

vm was taken 1:1 from an ESXI server

[Sofoniyas Teklegiorgis]

https://appuals.com/fix-vmware-bridged-network-not-working/

 

this URL helps a bit

[lmartini80]

I had the same problem in vmware player free with Ubuntu 22 as host and Windows 10 as guest.
I got stucked for few days until I find this video that explain a working solution on vmware workstation. 

Until I was on free player, I adapted the solution to my case by doing the following steps (in windows should be the same):

Run Virtual Network Editor GUI, in Ubuntu (free player) you can stop the VM, open a terminal and run vmware-netcfg or in case you're using workstation version using the right menu option.

On Windows/Ubuntu workstation version:
- click on change settings (if apply)
- click restore defaults
- start the Vm

On Windows/Ubuntu free player version:
- Until the button "reset to defaults" does not exist, just delete the bridge network item and recreate it with default setting
- start the Vm

Hope it helps someone.

 

[cyberbabe]

The culprit for my situation, with VMWare Workstation Pro on Windows 10 Pro, was the vSwitch adapter installed as a feature under Programs and Features. I unchecked the Hyper-V feature and did not uncheck Virtual Machine Platform and Windows Hypervisor Platform, and all was good.  The correct IP address and subnet was as it should be on my network, performed a couple pings, success

[Marco_Luvisi]

I have solved with removing Network Adapter from VM settings and add Network Adapter.

After I see NIC added are disabled and I have enabled.
Now bridge work.