I'm running Window 10 Pro Technical Preview Build 9926 with updates installed today. I have VMware Workstation 11 running with a Win7 guest OS. I can't connect using NAT or Bridge to the host machine network. Tried all suggestions in this thread, no luck. If anyone came across updated information, would appreciate passing it along. Thanks.
Hi, I tried nested virtualisation today:
Win8.1x64 with Workstation 11 with Win10 b9926 with Player 7 with Debian 7 and the network inside the Debian works when using NAT.
Trying Bridged now ...
However something strange is happening inside my Win10TP, some letters are not quit correct ... (see attachment).
screenshot.png 18.5 K
I have the same problem resolved in Virtual Network Editor with restore default settings: now it works.
Does not help here. Installed it natively, NAT has always worked, but Bridged adapter does not seem to work (get APIPA inside VM).
Restore Defaults does not work.
thanks for the suggestion. It worked for me. I couldn't get NAT or bridged to work but after setting to default values as you suggested, it is working fine.
Still no luck here, using build 9226.
NAT always works but bridging does not
Restoring default does not work and even manually setting the Bridge to one of my network adapters does not help.
I do see that the bridge installed correctly on my native adapters.
Running VMware Workstation as Administrator does not help either.
Same here, build 9226 - NAT works but bridged will not function on Linux/Windows. Hoping for a resolution.
This is happening to me too. Nat is working but Bridged is not. I spent several hours making every kind of configuration change that was posted here. Still no luck, and back to 8.1 until a fix is in place.
I wish I would have found this topic several days ago.
same here, bridged not working:
- windows 10 9926
- vmware 11 (build 2305329)
things i've tried:
- repair install
- linux and windows guest
- reset network config
As of 2/4/2015 with the latest Microsoft Windows 10 updates the Bridged network connection is STILL not working.
Is this a Microsoft problem or is it a VMWare issue?
1 person found this helpful
Hi, I have found a WORKAROUND here:
you can use windows' bridge feature, instead of VMware's.
1. Open Virtual Network Editor
2. Add Network "VMnet*"
3. Choose "NAT" or "Host only", NOT "Bridged"
4. Check Connect a host virtual adapter to this network
5. Make DHCP unchecked
4. Open Windows Network panel
6. Choose "VMware Network Adapter VMnet*" and your physical network card, right click, choose "Bridge"
7. Wait for a moment, you will see a "Network Bridge" adapter
8. Configure network in VM, DONE!
- 打开 Workstation 的“编辑”菜单中的“虚拟网络编辑器”
- 打开“控制面板\网络和 Internet\网络连接”
- 复选中对应的“VMware Network Adapter VMnet*”和物理网卡适配器（如“以太网”），右击“桥接”
- 出现“Network Bridge”适配器，桥接成功
BruceXiong - you are a legend. Your workaround worked a treat for me. Thanks!
I'm unable to add NAT as a new network, as there is already one created (VMnet8). Is it possible to use the existing NAT (VMnet8) connection and disable DHCP and then bridge that connection? The guide says to create one but it's not possible when there is one already created.
It appears that you can only create another HOST network, and then bridge that.
Correct if you already have a NAT than you won't be able to create another one in VNE however you can simply just select Host Only instead & continue to follow the previous poster's instructions.
I'm not sure of at what point you can create a NAT connection in the instructions as it appears you can only create a HOST.
I did find out that it messes with the RDP, and for some reason my network bandwidth monitor quits monitoring that specific adaptor. I didn't look for a solution.
I had an extra NIC installed and just bridged the new VMnet2 connection to the extra NIC.
Still not real sure; are we waiting on VMware or Microsoft to fix the problem?