virtualbox.org

I've done a bit of research, and I can't seem to find the right post, with the answer to my problem.

To start, I successfully run a Linux Host, with a Linux Guest connected to a VPN. However, once I try to replicate the exact Linux Guest setup on a Windows (7 64bit) Host machine, and I connect to the VPN, all host lookups are REFUSED. All DNS/Networking seems to just go away once the VPN is connected. Host lookup result in (REFUSED) errors. Seems like DNS just dies. I've tried with both NAT and Bridged. FWIW, both NAT and Bridged work with my Linux Host machine. And, of course, once I close the VPN, all my connections work just fine again.

Is there something special about Windows Host machines that won't allow a VM Guest to open a VPN connection?; I am running the Windows Host VBox as Administrator.

If you need any relevant logs or system information please feel free to ask.

Bump.

Somehow DNS resolution just completely goes away once the Linux Guest (windows host) is connected to the VPN. Can not ping hosts nor IP addresses.

The closest I've gotten to VPNs is LogMeIn Hamachi, so I don't know the ins and outs of network settings to establish a VPN. But it could be that in some way you missed one important setting or other when trying to replicate the guest on the Windows 7 host.
In Virtualbox version 4 the guest files (.vbox, .vdi, etc.) default to all being in the same folder. If your guest was made on a Virtualbox version 4 host, you should be able to simply copy the entire folder to the new Windows 7 host and double-click the .vbox file in the guest folder to register the guest with the new host. All the guest network settings will transfer over like they were on the Linux host, except that you may have to re-attach the network to the correct new host NIC.