But I'm not even using my Windows credentials. How can I force VPN (PPTP) to use the credentials that I have stored in the dialog while setting up the connection? Or where in the credentials manager can I find the credentials that VPN shall use?
Upgrade to Windows 10 2004 (VPN L2TP fail autoconnect)
Good evening.
After upgrading to Windows 10 2004, the L2TP / IPSEC VPN using MS-CHAPv2 with the option "Automatically use my Windows log-on name and password (and domain, if any) no longer connects automatically. Note that the computer in question is in an AD domain and in the previous version it was working without problems (the connection was established with the Windows credentials.
It turns out that now, in this version, it says that the user or password is wrong and shows the dialog window for entering the password. I put the same one I use for windows login and the connection is established. I wanted this to be done automatically and, if not possible, I would like to understand technically why this is happening.
Thank you.
Ricardo
Windows for home | Windows 10 | Internet and connectivity
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
107 answers
Sort by: Most helpful
-
Anonymous
2020-07-20T18:51:50+00:00 -
Anonymous
2020-07-20T18:35:56+00:00 The best suggestion is to create a batchfile that uses rasdial.exe. Lt2p VPN will connect using windows credentials
-
Anonymous
2020-07-20T17:28:53+00:00 Yep, no way for a roll-back. And I'm really wondering that Microsoft isn't giving us a fix during these days where VPN is so viable.
Anyway, I tried what Cary described. Deleted all WAN Miniports, then deleted the VPN connection and restarted the PC. But unfortunately no change. I'm still asked for the password with my Microsoft account given. But this is not what I use for my PPTP login. I need to use a plain username and password to authenticate against a VPN service running on a NAS (which worked fine for years).
Any other idea or working solution?
-
Anonymous
2020-07-20T17:02:08+00:00 I will give this a go. Its a problem during these times having to get people to come into the office and re-authenticate with the domain controller just to get them back online. Rolling back to 1909 isn't viable for us. Thanks!
-
Anonymous
2020-07-17T14:19:52+00:00 It gets better for us... If the VPN connection has any kind of hiccup (as lots of employees internet connection isn't the most stable), when they try and reconnect their credentials no longer work. Being the good users that they are, they try and reboot to fix the issue. Their cached credentials no longer work so they are now being forced to come into the office to log in and restore the credentials.
I may have to roll back to 1909 which wont be fun for the 50 VPN users...