vEthernet adapters cause VM to not have connection on startup

[ChrisKraut]

Windows 10 host, Linux guests. Whenever I boot a guest VM, various 'vEthernet' Hyper-V Virtual Ethernet Adapters are enabled in the network configuration and I have to manually disable them in order for the guest to connect to the real adapter that actually has a connection. This is how the bridge configuration looks like by default:

I can disable the "Hyper-V" adapters here and it is retained across sessions, but after I reboot the host, they turn back to being enabled again.

Is there any way to blacklist them for VMware Workstation?

[ChrisKraut]

*bump* (updated my question). Anyone?

[RDPetruska]

Not a direct answer to your question, but an alternative...

Don't use automatic bridging.  Specify in the Virtual Network Editor which physical NIC to bridge to VMnet0.  If you have multiple physical NICs, assign each one to an unused VMnet switch.  For the VMs you wish to use those, select "Custom" network connection instead of "Bridged", and select the appropriate VMnet you want.

[ChrisKraut]

Thanks, but this appears to be a Workstation Pro only feature. I am using Workstation Player, hence me posting in this board.

[RDPetruska]

Search the forum for posts on extracting the Virtual Network Editor from the Workstation Pro package.  You could even just install the pro version and leave it unlicensed -- the pro version includes the Player UI.

[ChrisKraut]

This worked, thanks! Nice workaround to the bug of not keeping de-selected network adapters. Is there any place where one can report this?

[cb831]

Any real solutions to this ?

I don't want to set interface to a fixed value as I would need to change it everytime I change between WiFi, USB Wired (dock) and Wired (directly to laptop). 

I would like to set the automatic selection settings to exactly these three adaptors and VMWare Desktop should not wipe/reset these on boot!

Is there a good reason for resetting at boot or is it just a bug ?

Thanks

PS: Now I set my VM's to use NAT which always works but it hinders me connecting to the VM's from outside the host without letting the host relay (e.g. ssh)

[RDPetruska]

Well, the 'automatic' bridging is *supposed* to be the answer to this... but historically, it has never worked consistently.  That's why us long-timers recommend setting a different VMnet adapter to bridge to each host NIC, using the Virtual Network Editor.  When you change host physical adapters, just use the network icon in Player's menu bar and disconnect, then change to the appropriate VMnet for whichever physical adapter you are using.

[bobchang]

Have you solve this issue?

After Hyper-v enabled, vEthernet interfaces are created and "take control" of your original ethernet card. For me, it is Intel(R) Ethernet Connection (6) I219-LM and is bridged to vEthernet (bridge) which is displayed as Hyper-V Virtual Ethernet Adapter #5 in wmware network setting. It works for me to select this one. I didn't try to "select all", it may not useful.

So you have to select the network card like this. Open properties of your real network card, you will see the IPv4 setting is lost. Check properties of all vEthernet interfaces and find the one has IPv4 setting, it is the one.