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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2020-06-15T09:56:08+00:00

    Hi Did as you requested, Removed the setting rebooted tested ( without the setting it does not connect to the RAS server) readded and rebooted again.  Tested again still the same issue,  invalid password but works when I type in the password. KB update for 2004 still same issue. 

    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.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-06-15T09:51:17+00:00

    Mine are two 3 different dell Laptops all worked fine 1903 but are now broken since 2004.  It's not a DNS issue else why does the connection work when you type in the password.  I have tested with Direct Access at least they did not break that.

    What hardware are you using?

    i have:

    1.) a custom built PC with no issues

    2.) a Surface Laptop 2 with the resolved issue applying reg-key

    3.) a Surface Pro 7 with a partial resolved issue; connection is established, authentication does not work.

    might be correlated to: https://docs.microsoft.com/en-us/windows/release-information/status-windows-10-2004 ?

    Issue persists with KB4557957 installed.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-06-15T09:47:37+00:00

    What hardware are you using?

    i have:

    1.) a custom built PC with no issues

    2.) a Surface Laptop 2 with the resolved issue applying reg-key

    3.) a Surface Pro 7 with a partial resolved issue; connection is established, authentication does not work.

    might be correlated to: https://docs.microsoft.com/en-us/windows/release-information/status-windows-10-2004 ?

    Issue persists with KB4557957 installed.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-06-15T09:41:49+00:00

    In my case it was not DNS: I sniffed with Wireshark an could see all pakets were correct, only the ESP protocol was missing.

    So I assume it's no DNS issue, even less a domain join issue.

    Should my assuption be wrong, please let me know.

    Was this answer helpful?

    0 comments
  5. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more