-
Notifications
You must be signed in to change notification settings - Fork 404
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Connect before windows logon does not work #625
Comments
In a nutshell here are the requirements for PLAP to work:
Consult the following for some more info:
If you still have issues after following those instructions, come back here with specific questions. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
First, forgive me for translation errors. I'm Brazilian and I'm using Google Translate.
Today I have a huge headache with external users who need to login the first time via domain. They need to log in as a local user, connect to OpenVPN, then click Switch User and log in with their Active Directory credentials. Once recorded in cache, then they can log in normally later.
In a perfect world, OpenVPN starts and connects even before the user enters their credentials, so the equipment "would already be on the company's network", connecting to the domain server's network.
Try all the ways I found on the internet, even with the help of ChatGPT. And nothing worked effectively. The most I could do was for OpenVPN to start automatically, but only after I had logged in as a user, which makes no sense.
But now I saw that OpenVPN has a native function when installing:
Enable OpenVPN Pre-Logon Access Provider
I left it enabled during installation, and it still doesn't work! OpenVPN does not start as a service already connecting before logging in with the user.
I do not know what else to do
The text was updated successfully, but these errors were encountered: