virtualbox.org

I have a MAC running High Sierra as a host. I am currently running VirtualBOX Version 5.2.14 r123301 (Qt5.6.3)

I am currently having some issue getting a Windows VPN connection to work within the guest. I have tried both bridged and NAT for my network. I consistently get the following error message in my Win10 VM guest: the modem (or other connected device) is already in use or not properly configured.

I was hoping there was a step by step setup I could follow.

Did you search the user manual for the term VPN? It specifically says that you can't use VPN-PPTP with NAT.

It should however work with bridged networking, provided bridged networking works for you otherwise, i.e. when not using VPN.

Moving to "Windows Guests" from "OSX Hosts" as this appears to be a guest issue.

Searching for "the modem (or other connected device) is already in use or not properly configured" returns (among many, many links) the following Microsoft article:

• "Error 633 - the modem (or other connecting device) is already in use" error message when you try to establish a VPN connection in Windows Server 2003

See if that helps. Just because an OS/program that runs in the context of VirtualBox has a problem, it doesn't make it a VirtualBox problem necessarily. You're having an issue that has most probably nothing to do with VirtualBox, so my suggestion would be to treat it as such, as a native problem with the OS or the application of the guest.

Socratis,

That solved the issue, but after subsequent reboot, the same condition returned, with no visual process running on 1723.
I explored further within the Windows stack as you suggested, and to your point, VirtualBox was not holding anything back at this point..

I ended up setting Remote Access Connection Mgr to manual within Services, then rebooting, and that let me connect.

I noticed the same behavior in different profiles, and the fix all worked for them all

Thanks again for you assistance with that article.

Glad you got it going. You also learned that a problem in a VM is not necessarily a VirtualBox problem...
Marking as [Resolved].