Also, running ipconfig /all in windows doesn't show that a VMnet0 actually exists. I assume you would normally see a VMnet0 adapter in ipconfig's output
No, VMnet0 is not an adapter, but a client. In your physical NIC configuration settings, you should see the "VMware Bridge Protocol" or similar setting.
Are you sure the VM is still connected when you change from NAT to Bridged? Many newer Linux OSs cache the network adapter settings, and if you are changing the subnet, etc. it is connected to on the host, you have to do some reconfiguration in the guest.
Thanks for the reply and sorry for the delay. Never received any notification that I had a reply, sorry about that.
Correct, in my Windows 10 host, if I check the Properties page of my Physical Network Adapters I can see that protocol your talking about, which is enabled.
So currently, the VM's Network Adapter in VMware Player shows "Bridged", as you can see below.
Then, looking on the VM itself running ifconfig, it shows the following, which is not our Wired network's subnet:
eth0 Link encap:Ethernet HWaddr 00:0C:29:2B:09:45
inet addr:192.168.153.129 Bcast:192.168.153.255 Mask:255.255.255.0
inet6 addr: fe80::20c:29ff:fe2b:945/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:243 errors:0 dropped:0 overruns:0 frame:0
TX packets:232 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:22586 (22.0 Kb) TX bytes:22368 (21.8 Kb)
Interrupt:18 Base address:0x2024
On my Windows host, ipconfig shows:
Ethernet adapter VMware Network Adapter VMnet8:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet8
Physical Address. . . . . . . . . : 00-50-56-C0-00-08
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::547d:7daf:4bdf:1b1e%24(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.153.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 402673750
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-21-CA-90-87-54-E1-AD-4C-97-1E
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
Primary WINS Server . . . . . . . : 192.168.153.2
NetBIOS over Tcpip. . . . . . . . : Enabled
And then the Virtual Network Editor is showing the following:
So I'm not really sure what the problem is. But, it won't work with vmnet0... I even just upgraded VMware Player to 14.1.6 build-12368378 and the issue is still happening after the update finished.
However, if in the Virtual Network Editor I change VMnet8 to a Bridged connection, and then manually select the Ethernet adapter, it appears to work and my VM gets an IP Address on the Wired subnet. But, if I change it to bridge the Wi-Fi adapter, it doesn't work.
Is there any kind of log somewhere host or guest, that would say if and why VMnet0 is failing?
I also just read a few posts saying that wireless isn't available to the Guest VM unless you do a USB Wi-Fi adapter and connect it to the VM...?
Is that true, or is that more for connecting the Guest to a different SSID then then Host is connected to?
Folks - I just encountered this exact same thing. Running Windows 10 host with Windows Server 2016 guest. I have bridged networking enabled for the guest which should be bound to VMnet0 and getting an IP address from my home router. However, the guest is not getting an IP address from my router but from an address range configured in VMnet8 and it's DHCP settings. I also tried to force a static IP that I know should work with the network but that doesn't work and the guest has NO network connectivity. I am running VMWare Workstation 15 and just upgraded with the latest updates. Any advice is welcome.
Thanks for the verification Stuart. Those are my exact same symptoms.
If you run the Virtual Network Editor, are you also able to change VMnet8 to Bridged protocol and manually set it to use the Ethernet adapter? If I do that I can get bridged working. However, it doesn't work with the Wi-Fi adapter, only Ethernet.
So it appears the issue is with VMnet0 itself, as far as I can tell...
I have the same problem. There is def a bug here. So what I did was remove the default VMNet1 and VMNet8 adapter from the Virtual Network Editor. Then I set VMNet0 to Host only (this is just temporary, I needed to free up my external network adapter as I only have one). Then I recreated VMNet8 manually and set it to bridged mode and selected the external network adapter I am using. Removed the VMNet0, and VIOLA!.
20190817_122050.jpg 615.3 K