I recently upgraded my Workstation Pro and Player from 17.0.0 to 17.0.1 and on both occasions, updating the software broke the network bridge functionality. I think the network bridge driver is broken for this latest update and needs to be urgently addressed.
Yes, I can confirm, Workstation Player 17.0.1 is broken.
On all VM's the vmxnet3 driver works, but no "Bridged: Connection directly to the physical network"
- Windows 10 Pro N (22H2)
- Intel(R) Centrino(R) Wireless-N 2230
Downgraded to 17.0.0 and it works again.
I can also confirm that 17.0.0 bridge mode works and 17.0.1 breaks it. Went back and forth to confirm. Host is Win 10 version: Pro 22H2, os: 19045.2604, Windows Feature Experience Pack 120.2212.3030.0. Guests are Debian 11.6 and Ubuntu 22.04.2 LTS. NAT mode works on both versions.
That's 6 wasted hours I am never getting back. Geez, how is this kind of a massive bug even possible with mature regression testing.
We will be looking into this issue. Could you please help us answering the following queries.
Wireless for me, Intel AX210NGW module. Did not test wired.
IPv4 DHCP local network, did not test IPv6. I’ll point out that your known IPv6 is documented for Win 11, this issue is also on Win 10 not 11.
Already provided guest and host details.
I have this issue when bridging to a wired network adapter. Moreover, I cannot get to the internet on NAT mode either. I'm looking for how to downgrade to 17.0. This is an IPv4 setup. Thank you
Apologies for the inconvenience caused.
As a workaround, could you please try out setting static IP for your VM. Please make sure to configure the default gw to bridge gateway and DNS name server for name resolution.
@gj1, thanks, but for myself and for the record, I won't be trying that, but would be curious to know for completeness if this helps (i.e. a DHCP client problem in 17.0.1?). Reasons: a) spent too much time on this already, b) have real work to do, c) not a paid VMware employee tasked with QA.
In my case, all my VMs are set as static IPs and I'm having problems (seems to be more with Windows VMs though and Ubuntu 22 seems fine). In my case, I have an Active Directory VM doing the DNS (and forwarding if it can't resolve).
I'm going to try using a wired connection on my host instead of Wifi to see if it makes any difference.
More reports, they are all saying it appears to be DHCP only, but my VMs are all static. My problems with bridged seem to be intermittent, odd and I haven't put my finger on it just yet.
Same here - the frustrating bit beyond the actual issue is that you can still download this corrupt piece of software - why isn't it pulled? I just went thru the motions last week and screwed with numerous machine configurations - only to find out its not me... Also, the replies of the VMware team are mildly frustrating when they evidently don't use their own products... this issue is so obvious it is hard to fathom how it got missed or not even being acknowledged despite we are telling them...
I am having issues with NAT also, dhcp and static both are not working.
Exactly the same issue I am experiencing as well. However, Windows Server 2022 bridges as a DHCP client works fine as well. CentOS and Ubuntu VM’s do not work as DHCP clients as bridged.