Upgrade to Windows 10 2004 (VPN L2TP fail autoconnect)

Anonymous
2020-06-02T14:15:49+00:00

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.

0 comments

107 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2020-10-23T20:25:21+00:00

    Michael,

    Same behavior in observed in our environment. We are holding back updating to 2004 and beyond until this issue is resolved. 

    Thank you for opening a pay per incident support ticket with Microsoft.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-10-23T18:27:30+00:00

    We are experiencing the same problem with Windows 10 2004 and 20H2:

    • Despite SSO enabled the user gets presented a password prompt saying "Action needed"
    • The user can enter ANY password to successfully connect
    • Initiating the connection from the command line with "rasdial" works with SSO
    • No changes on the server side and no errors logged on the server

    It seems to be a GUI problem as it only occurs when initiating the connection from the GUI. I have raised a pay per incident support ticket with Microsoft yesterday and am waiting for their response now. I've also linked this thread within my ticket.

    Michael

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2020-10-22T18:34:16+00:00

    Windows 10 Enterprise version 20H2, Build 19042.572 and the problem STILL persists. Like everyone else reported this worked fine on version 1909 and earlier. I've had to block all feature updates in WSUS until this is resolved. We're currently holding at version 1909.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  4. Anonymous
    2020-10-22T17:31:07+00:00

    Just updating this post to say that I have solved this issue, but not by doing anything suggested here. My ISP does not give enrollees static ips. They are dynamic and are behind double NAT. It would appear that whatever Microsoft is doing to enable this VPN cannot work under these conditions. 

    I had to upgrade my line to a static ip which will cost me $10/month extra. 

    Shame that Microsoft can't handle this. Not everyone has a static ip.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-10-22T11:50:39+00:00

    I tried this a while ago. And again today. Doesn't work for, neither deactivated nor activated.

    Was this answer helpful?

    0 comments