This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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
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.
Just spent whole day deploying fresh l2tp-->Mikrotik-->Radius-->WinSRV2019 NPS and searching for solution to this problem.
Our findings indicate, that 2004 when using Windows log-on name and password does pass forward domain name. NPS is actually receiving user.name instead of domain\user.name, thus failing to authenticate user. Only option now to actually store credentials with connection in form domain\username
I've try to remove all vpn virtural apdater driver in device manager, reboot, then problem have been resolved!
Doesn't work for me. When I enter a random password (username is given and always my Microsoft account) I gte the error "Connection with <...> not possible. PPP connection protocol terminated" (translated from German, so probably a little different).
Yes it's true. I will wait for Microsoft's fix.
Microsoft is currently investigating this behavior. Please hold on and wait for the future patch.
It seems to be appearance problem. the dialog pops up asking user to type-in user credential, but not really mean any previous authentication has failed. the dialog is displayed even before any actual user authentication is attempted. You can type-in any random username and password and hit enter. the typed in info will be discarded and still use your current Windows logon name and password to finish the authentication and VPN will be connected with the correct user credential.
so far, no workaround truly works, unless changing the authentication method away from using user name and password (for example use certificate instead) .
Microsoft is currently investigating this behavior. Please hold on and wait for the future patch.
It seems to be appearance problem. the dialog pops up asking user to type-in user credential, but not really mean any previous authentication has failed. the dialog is displayed even before any actual user authentication is attempted. You can type-in any random username and password and hit enter. the typed in info will be discarded and still use your current Windows logon name and password to finish the authentication and VPN will be connected with the correct user credential.
so far, no workaround truly works, unless changing the authentication method away from using user name and password (for example use certificate instead) .
