So, I'm running Windows 10, 64x tech preview. VMware workstation (latest greatest build (10.0.3) installs and it works just fine.
I always link a VMnet to a dedicated physical NIC. (bridge), however, even though I'm able to configure it, it simply doesn't work. The VMnet works fine internally on workstation, but not a single packet seems to be able to transfer to the host.
No firewall running, the VMware bridge drive is installed properly. When I create a host adapter for a virtual network and bridge it with the physical one it works, too. But a direct bridge doesn't work.
Can anyone running Windows 10 64x tech preview confirm this? It's quite simple configured as below.
Same problem as have hit random users. Remove VMware. Uninstall ALL your network adaptors. Don't forget that uninstalling will blow all the networking settings out, and you will need to reenter them after you reinstall . Scan for new hardware allowing your network adaptors to reinstall, and then install VMWare fresh.
similar issue here no network for windows 8.1, 7 nor MINT running windows 10 b10041 w/workstation 10.
resolved the issue by running the "virtual network editor" reset defaults. I did not have to reinstall VMware.
restarted all my vm's connected LAN and Internet.
windows 10 b10041 running smoothly although I run "troubleshoot compatibility" on every new program install.
If you are having issues with VMWare's adaptors than most likely you are having problems accessing the network adaptor settings for your PC. Right click and see if you are able to get to the network settings of every network card. For some reason Windows 10 has a problem with a few systems, and removing the network adaptor and then allowing the OS to detect and install again will resolve the issue.
Hi Vmware Workstation Buddies ,
I think the issues not just happened on Windows 10 but also windows 8 and Windows 2012 , with installed workstation 10 . The status on Bridge connection still no connection status show up. But it works on VM guest which can get ip on the same network segment as for host. My workstation version is 11.1.0 build-2496824 . It is latest build one so far. I hope the product aware this and have the fix on next build .
My screen shot on virtual network editor
Are you saying bridge connections are not working?
I'd look at a different problem then what was happening with 10.
No problems with bridged connection on 8, or 2012, for me anyway.
To go back to the original thread: Windows 10 b10049 HAS THE ORIGINAL PROBLEM.
So VMware bridging does not work, problem with Windows network stack (still): when trying to manually add the VMware Bridge Protocol to my network adapters, Win10 throws me an "interface not supported" error.
So do not upgrade to 10049 if you want full Workstation functionality.
MS really needs to start moving to debugging, especially on the network stack, because e.g. WinPCAP doesn't work either and I can't easily reach half my SMB shares ...
I'm not sure as I switched to the slow track because of Spartan. Still on 10041 and bridging is still working. These types of things are expected with BETA. You might want to roll back to 10041, and go the slow track on this one
This is not only happening with VMWare but the same thing is experienced on Virtual Box. It seems Microsoft is screwing with users that are using virtualization... The is no reason they should be cycling the code that breaks the networking for virtualization between releases.