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 set up - I can get NAT to work by reset the virtual network editor and then repair workstation 11 install via the same install files. Bridge is still a no go. No AV, No UAC and still nothing.
Using Qualcomm Atheros AR8151 PCI-E Gigabit Ethernet Controller (NDIS 6.30) adapter.
Hell ya - Thanks BruceXiongBruceXiong that worked for me.
In laymen's terms...
1. Open Virtual Network Editor
2. Add Network "VMnet*"
3. Choose "Host only", NOT "Bridged"
4. Check Connect a host virtual adapter to this network
5. Make DHCP unchecked
- no need to write down the Subnet IP as it will be bridged to your physical adapter anyways.
6. Open Windows Network panel
6. Choose "VMware Network Adapter VMnet*" and your physical network card, right click, choose "Bridge" - How to Create a Network Bridge in Windows 7 - YouTube (Same process in Win10TP)
7. Wait for a moment, you will see a "Network Bridge" adapter
8. Configure network in VM to same subnet/gateway as your hosts ipconfig network gateway.
pings for everyone! No need to configure IPs anywhere other than the VM.
What we get for being early adopters...
To be exact... I can ping from guest machines to other guest machines or to other real machines in the net, the inverse is truth too, real to guest... but I can't ping to guest machines from the host machine... that's when I get the "general failure" error....
Hi again Michael..... Nope.... same issue....
- Ping from guest to other real machines in the net,... OK
- Ping from guests to guests...OK
- Ping from other real machines to guests... OK
- Ping from host to real machines,....OK
- Ping from host to guests... "General Failure" error...
A quick test on Windows 10 b10041 with Player7.1.0 confirms that both NAT and Bridging are working out-of-the-box.
So could it be that for the first time ever, we have a Windows 10 version that is capable of running VMware Workstation as intended?
I install 10041 but found it unacceptable to run as my primary OS. I switched to the Slow track to wait for the bugs to be cleaned. Sounds like VMWare is running as normal again. I won't be able to try until the Slow track is pushed out.
I run a 3 monitor setup, with a lot of applications open at any given time, and haven't seen any issues so far. I've only been running it for ~3 hours, but so far so good
I'm having trouble with b10041. Network is working but I cannot configure anything.
First of all I cannot access to my adapter settings; Snip2
Also trying to configure Bridge connection fails too; Snip1
Anyone else having network related issues with 10041?
Tried to install new drivers for 82579LM too, but didn't help. Seems like a 10TP issue huh?
Try running as Administrator. Also: clean install of 10041?
Slightly Off-Topic about 10041, I've been using it for a couple of days. Best build so far, but still not nearly as good as any beta-build from WinVista/Win7.
Workstation works completely as expected, but WinPCAP does not, so Wireshark/nmap/... fail to work. It seems Microsoft is desperately trying to rewrite their TCP/IP stack.
Furthermore, some strangs bugs, drivers not working as expected (touchpad broken), GUI problems (after 10mins of runtime, the startmenu fails, Sysinternals ZoomIT crashes ...)
I can keep on naming, I hope they soon start shipping a Consumer Preview instead of a Tech Preview, which would mean they freeze functionality and start working on stability.