Not as yet, I escalated through our Microsoft Rep but mum's the word
Upgrade to Windows 10 2004 (VPN L2TP fail autoconnect)
![](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)
Anonymous
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: Newest
-
Anonymous
2020-06-25T10:11:58+00:00 -
Anonymous
2020-06-25T09:43:49+00:00 Yeah, same issue here. Anyone have more info about this yet?
Luckily discovered this issue on our Test machines before pushing Win 10 2004 Upgrade to all users.
-
Anonymous
2020-06-23T12:08:57+00:00 Same problem.
It's not even sending any credential. It's just pops with message that "The user name or password is incorrect" But it's not the correct message from VPN - Radius response like (The remote connection was denied becouse the user name and password combination you provided......)
Trying some deeper invest on this one BUG. Will share results.
-
Anonymous
2020-06-17T10:54:34+00:00 That is a workaround and not a fix. If the user's credentials change i.e. password expires then he has to update the stored credentials as well. Which is a minor inconvenience to having to enter the password each time. A workaround you use for temporary fixes, it worked correctly under 1909 and earlier so one should expect to work now.
The issue is either Microsoft is not sending the credential password or not decrypting it correctly.
Seeing that everyone that has installed 2004 is having the issue, it is most certainly a bug that needs to be fixed.
Thanks for the info anyhow.
-
Anonymous
2020-06-17T09:54:47+00:00 Sorry missed the one line at the end of the 1909 trace
[0]0E70.0F70::2020-06-15 14:58:00.239 [Microsoft-Windows-RRAS]IASResponse = ACCESS_ACCEPT