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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2020-06-09T20:59:30+00:00

    Same issue here, we are using IKEv2 (AlwaysON), It was working fine on Win10 1909, 1903 and 1809.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-06-14T15:45:59+00:00

    For me the following old solution from Microsoft worked: 

    https://support.microsoft.com/de-de/help/926179/how-to-configure-an-l2tp-ipsec-server-behind-a-nat-t-device-in-windows

    Setting the Value to "2" and rebooting, the VPN connection could be established an authentication worked

    Let me Know if it worked.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-06-15T08:55:25+00:00

    Just for test try disjoin from domain and rejoin and see if problem persist?

    Check event viewer and see if there is any log files like network or DNS failure?

    Report this issue through Feedback Hub app.

    Just to let you know this happened to a machine that was freshly joined to the domain so no DNS issues as it joined fine to the domain. So disjoining it and rejoining is a pointless exercise.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2020-06-15T09:15:59+00:00

    For me the following old solution from Microsoft worked: 

    https://support.microsoft.com/de-de/help/926179/how-to-configure-an-l2tp-ipsec-server-behind-a-nat-t-device-in-windows

    Setting the Value to "2" and rebooting, the VPN connection could be established an authentication worked

    Let me Know if it worked.

    Hello,

    unfortunately, the "AssumeUDPEncapsulationContextOnSendRule" reg entry is already set to "2".

    I can try (later) to delete reg entry, reboot, recreate reg entry, reboot and retry.

    Edit : I've tested to delete reg entry, reboot, recreate reg entry and reboot but the problem persist.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-06-15T09:18:18+00:00

    Just for test try disjoin from domain and rejoin and see if problem persist?

    Check event viewer and see if there is any log files like network or DNS failure?

    Report this issue through Feedback Hub app.

    Just to let you know this happened to a machine that was freshly joined to the domain so no DNS issues as it joined fine to the domain. So disjoining it and rejoining is a pointless exercise.

    I can try this tomorrow when I'm at the office. :)

    Was this answer helpful?

    0 comments