Guest VPN no longer working

[Rune B]

Hi,

I have a Windows 10 guest running on a Mac host (MacOS Sierra 10.12.1). On the guest I have several VPN connections that have all been working fine using a Bridged Adapter setting in VB. After upgrading to 5.1.10 none of the VPN connections will connect anymore. They all give an error message saying "A connection to the remote computer could not be established. You might need to change the network settings for this connection".

Does anyone have any idea if something changed or defaults were altered?

Thanks,
Rune

P.S. running the VPN on the host will work technically but it will be very inconvenient for the way I work. It's on the guest I want to run the VPN.

[scottgus1]

If your guests are Bridged, are they able to see your physical network when the VPN's aren't running? Make sure there still is a network connection to use.

Virtualbox networking requires adding drivers to the host OS. Be sure that the Virtualbox bindings to the physical network card exist and are enabled. (No idea how to do this on a Mac host.)

It is possible to revert Virtualbox back to the previous working version to see if it is Virtualbox that has the issue. If you want to try this, uninstall, reboot, install the old version. To upgrade again, uninstall, reboot, install the new version, just to avoid confusion in the host OS.

[socratis]

I have no clue about VPN, but I have a couple of notes related to the host:

• I have no clue (do you see the irony with my last statement?) how the bindings are enabled or not on a Mac. I simply know that they always are on and there is no option that I know of to switch them off. Never had the slightest problem (it's a Mac, it just works ). For what it's worth, I know how to do it on Windows and I know nothing about the ones on Linux.
• The filter/adapter drivers are in "/Library/Application Support/VirtualBox/". VBoxNetAdp.kext for the HostOnlyNet, and VBoxNetFlt.kext for the BridgedNet. Never heard anyone complaining about neither.
• There is no need to reboot in between uninstalls, otherwise I could never try so many versions in so much little time. There is one simple rule to follow: whatever version you're uninstalling do it from that DMG version or a higher one. For example:
  • If you are downgrading from 5.1.10 to 5.0.20, mount the 5.1.10 DMG, run the Uninstall.tool, eject it, mount the 5.0.20 DMG, install it (it took me more to write it than it actually takes, believe me).
  • If you are upgrading from 5.0.20 to 5.1.10, mount the 5.1.10 DMG, run the Uninstall.tool (usually optional), install VirtualBox.
• Other than that the typical caveats apply: never use the "save the VM state" when changing versions.