donod
Contributor
Contributor

Windows 10, Workstation 10, no LAN bridge

Hi!

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.

Schermafdruk 2014-10-03 15.55.01.png

182 Replies
keithlammersBFS
Enthusiast
Enthusiast

Just piping in to say that I'm running into this issue with Workstation 10, and Workstation 11 on Win 10 9926 as well, and that BruceXiong's workaround works.

0 Kudos
tonster76
Contributor
Contributor

Thanks BruceXiong you nailed it

0 Kudos
osterluk
Contributor
Contributor

Should the VM Guest network be configured for bridged or host?

0 Kudos
DivConsulting
Contributor
Contributor

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.

0 Kudos
DivConsulting
Contributor
Contributor

Hell ya - Thanks BruceXiongBruceXiong that worked for me.

In laymen's terms...

Steps:

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...

JHAres
Contributor
Contributor

Hi everyone,

Yes, BruceXiong method works great... but I can get ping between machines to work... says "General Failure" error.... Firewalls are down... weird...

0 Kudos
VM_Michael
Contributor
Contributor

You'll have to disable (uncheck) the VMware Bridge Protocol in Networking if you want to be able to disable the adaptor.

0 Kudos
JHAres
Contributor
Contributor

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....

0 Kudos
VM_Michael
Contributor
Contributor

Try removing or disabeling the VMware Bridged Protocol from the network adaptor.

0 Kudos
JHAres
Contributor
Contributor

Hi Michael... Which one ? The new VM adaptor bridged with the physical card ????

0 Kudos
VM_Michael
Contributor
Contributor

Go to the physical card and disable the VMware Bridge Protocol. This protocol is what is broken between VMware and Windows 10. I'm not sure it will fix the problem?

0 Kudos
JHAres
Contributor
Contributor

Hi again Michael..... Nope.... same issue....

Detail:

- 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...

0 Kudos
Photubias
Enthusiast
Enthusiast

Hi guys,

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?

Regards

0 Kudos
VM_Michael
Contributor
Contributor

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.

0 Kudos
keithlammersBFS
Enthusiast
Enthusiast

Just installed 10041 here as well, and I can confirm that Bridged networking is working again in VMware Workstation Smiley Happy

0 Kudos
osterluk
Contributor
Contributor

Hi Keith, I don't mean to turn this into a Windows 10 discussion, but did you find 10041 to be worse than 9926, or just that it's not on the Slow Update track?

0 Kudos
JHAres
Contributor
Contributor

Hi Michael,

Glad to hear bridge is working again.... but... what nasty bugs do you encounter in 10041 ?

Kind regards !

Javier.

P.S: Sorry because the slight OT... 🙂

0 Kudos
keithlammersBFS
Enthusiast
Enthusiast

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 Smiley Happy

yackson
Contributor
Contributor

Hi guys,

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

Running vmw11.1

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?

0 Kudos
Photubias
Enthusiast
Enthusiast

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.

Regards

0 Kudos