I am inferring that what is happening here is that the post-UAC-prompt version of the Virtual Network Editor is storing its changed settings - or at least some of them - in a place where the rest of VMWare Workstation Pro, as run from my own (no-UAC-prompt-involved) user account, does not know to look for them. On that attempt, in the grayed-out version of the VNE, the resulting adapter did not even appear in the list of displayed networks at all. I have also gone through a version of this in which I selected vmnet0 instead. * Observe that the network is set to "Bridged", with the VPN's adapter specified. * Click "Change Settings", and approve the UAC prompt, as before. * Observe that the network is displayed as being configured as "Host-only". * After it finishes initializing and launches, click "vmnet2" in the list of configured virtual networks. * Go back to Edit -> Virtual Network Editor. (If I now configure a VM's network adapter to point to the newly-added virtual network, the result is that within the VM, networking does not function I get DHCP timeouts, et cetera.) * Set the new network to "Bridged", and use the drop-down to select the name of the VPN's adapter. * After the Virtual Network Editor finishes re-initializing and re-launches, observe that the interface is not grayed out. * After it finishes initializing and launches, observe that nearly all of the parts of the interface are grayed out. * From within VMWare Workstation Pro, go to Edit -> Virtual Network Editor. To do this, I need to use the Virtual Network Editor. (I could be wrong about this, and if I am I'd appreciate being pointed to the correct solution, but this is the approach that led me to the behavior which I want to talk about.) What I think needs to happen in order to make that work is to create a new virtual network, set it as Bridged, point it to the network adapter that's created by the VPN connection (rather than letting it default to the physical network adapter that points to the host's immediate network environment), and configure the VM-settings network adapter to use that virtual network. When that happens, I need to be able to get some, but not all, of my VMs to connect (and, importantly, get DHCP) across the VPN, rather than using the host's immediate network environment. Other times, I am connecting the host computer to my workplace's network across a VPN. Some of the time, I am physically present (with the host computer) at my workplace, and virtual-machine networking works fine, using the Bridged option on the VM-settings network adapter. I log into the host computer (and run VMWare Workstation) as a domain account, which is a member of the local Administrators group on this computer. I'm running VMWare Workstation Pro 16.2.3, under Windows 10.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |