Hi continuum, I will post some info. But can you be more specific what part of those files I should post?
Thanks,
See attached file - it shows .vmx settings, vmnetdhcp.conf, and Virtual Network editor.
Also, see these log lines from the vmware.log for this VM.
It is a mystery, and probably a hard-coded bug. No combination of changing .vmx, dhcp conf and restarting Windows VMWare DHCP service had any effect.
As soon as I either 1) changed any other VM setting in the GUI, or 2) launched the VM, the network would change immediately from NAT to Bridged, and that new setting would be overwritten and saved in my .vmx setting file.
019-03-18T15:14:51.044-04:00| vmx| I125: ConfigCheck: No rules file found. Checks are disabled.
2019-03-18T15:14:51.044-04:00| vmx| I125: changing directory to D:\VMs\dev02\.
2019-03-18T15:14:51.044-04:00| vmx| I125: Config file: D:\VMs\dev02\dev02.vmx
2019-03-18T15:14:51.045-04:00| vmx| I125: Vix: [mainDispatch.c:4233]: VMAutomation_ReportPowerOpFinished: statevar=1, newAppState=1873, success=1 additionalError=0
2019-03-18T15:14:51.045-04:00| vmx| I125: Vix: [mainDispatch.c:4233]: VMAutomation_ReportPowerOpFinished: statevar=2, newAppState=1878, success=1 additionalError=0
2019-03-18T15:14:51.065-04:00| vmx| A100: ConfigDB: Setting ethernet0.connectionType = "bridged"
2019-03-18T15:14:51.089-04:00| vmx| I125: VMXVmdbCbVmVmxExecState: Exec state change requested to state poweredOn without reset, soft, softOptionTimeout: 0.
2019-03-18T15:14:51.089-04:00| vmx| I125: Tools: sending 'OS_PowerOn' (state = 3) state change request
2019-03-18T15:14:51.089-04:00| vmx| I125: Tools: Delaying state change request to state 3.
2019-03-18T15:14:51.089-04:00| vmx| W115: PowerOn
