Apparently yes, it is on the client side. I don't know is why it happens!
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-04T19:46:41+00:00 -
Anonymous
2020-06-04T18:13:11+00:00 It's a client side problem rather than a server side problem. I have two computers that recently updated to Windows 10 2004 from 1909 and they're both experiencing this problem when previously they did not.
I'm lucky enough to have the access to the logs on the RADIUS server that performs the authentication for the L2TP VPN and it doesn't even process the authentication until after the password is entered. The same is also true for an old PPTP connection I was able to test with that's being hosted off of a Windows 2012 R2 RRAS server.
-
Anonymous
2020-06-04T08:22:05+00:00 The strange thing is that in the dialog window it says that the user or password is wrong. If it was a security requirement, I would not display this message. I think!
-
Anonymous
2020-06-04T06:47:10+00:00 Just to inform that there are more users having this issue.
We have the same problem with all our computers, around 100, after the Windows 10 2004 update.
-
Anonymous
2020-06-04T05:57:20+00:00 I can't find any DNS errors and this is happening on more computers. I didn't disjoint and join the domain because it's not just being applied to one machine.