LAN Segment is not persisting after shutdown and when starting up the VM. The lan segment changes to bridge mode during both events. Any help would be greatly appreciated.
Thanks not trying to use custom. Trying to use Lan Segments. You can only launch Virtual Network Editor as Administrator to make changes (at least in this version).
So, I just got it working. Resolution:
Step 1: Delete: Network Adapters from VM
Step 2: Edit VMX file and delete all references to Ethernet. e.g. Ethernet0., Ethernet1., etc
Step 3: Re-add Network adapters.
Guest OS in the VM?
Host OS?
Workstation version?
Just downloaded Trial copy of Workstation Pro 16.2
Host O/S = Windows 10 Enterprise
Guest O/S = Windows Server 2016 Standard
Also, to add more to the details. No matter what Network Adapter change I make it always reverts to Bridged. I am dead in the water. Could use some guidance.
These VMs operated fine on Workstation 12, looking to upgrade and now they will not run correctly. The VMX file always get overwritten on startup and shutdown to Bridged.
ethernet0.present = "TRUE"
ethernet0.pciSlotNumber = "192"
ethernet0.virtualDev = "e1000e"
ethernet0.networkName = "MDM"
ethernet0.addressType = "static"
ethernet0.address = "00:50:56:2B:CF:1A"
ethernet0.connectionType = "bridged"
ethernet0.displayName = "VMnet1"
ethernet0.pvnID = "52 74 f1 e9 79 44 0e 29-90 b2 a0 36 04 f5 5c 24"
What is crazy is my Lan Segment name is "MDM". My Custom VMnet1 is separate and not configured.
I have tried deleting the references in the VMX file for ehternet0 and having the editor recreate, but it always writes bridged.
Help!!!
Grasping at straws here but -- have you launched the Virtual Network Editor "As Administrator"?
Also, if you are going to use a custom network, it's a good idea NOT to re-use the default VMNet0, 1, or 8, which are the defaults for bridged, host-only, and NAT. Use one of the other unused ones (2-7, 9).
Thanks not trying to use custom. Trying to use Lan Segments. You can only launch Virtual Network Editor as Administrator to make changes (at least in this version).
So, I just got it working. Resolution:
Step 1: Delete: Network Adapters from VM
Step 2: Edit VMX file and delete all references to Ethernet. e.g. Ethernet0., Ethernet1., etc
Step 3: Re-add Network adapters.