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
    2021-05-18T22:06:15+00:00

    Allan, thanks, even now PPTP works again, I will do a test in my system of what you tell.

    Thanks again and best regards.

    Javier

    Was this answer helpful?

    0 comments
  2. Anonymous
    2021-05-18T21:21:44+00:00

    What I found to be our issue was Windows Defender.

    We were originally using another antivirus application and shifted over to Windows Defender.

    L2TP vpn stopped working.

    Prior to moving to Windows Defender, I followed the instructions from Windows Report:  https://windowsreport.com/cannot-connect-l2tp-vpn-windows-10/

    That worked and the VPN did as well.  Enter the transition to Windows Defender and the VPN stopped working.

    In Step 7, from Windows Report, they have you create an Inbound and Outbound port rules and set them to "Allow the connection if it is secure".

    I changed the setting on both Inbound and Outbound from "Allow the connection if it is secure" to "Allow the connection".  Boom!  VPN now connects.

    Not 100% sure if this is ideal or not, but it does allow the VPN to connect.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2021-01-11T22:40:17+00:00

    Let me clarify my situation. This thread was opened due to problems with VPN L2TP connection.

    My problem does have two faces:

    1.- I found that Windows 10 VPN Server DOES NOT support native L2TP/IPSec protocol and I would need a 3rd. party product, what I don't want.

    2.- So, I need to use PPTP protocol, and THIS ONE is the one that when I install the 2004 or 20H2 characteristics update doesn't work, the integrated server doesn't accept the connection, that restoring to 1909 DOES work.,

    Then, what I would need is a solution for VPN connection to Windows 10 integrated server using PPTP in 2004 or 20H2 versions.

    Regards

    Was this answer helpful?

    0 comments
  4. Anonymous
    2021-01-11T18:32:36+00:00

    As I said in a previous post, I tried it and it didn't work :( and I also tried the referenced url's and they are reachable without any problem.

    But the VPN integrated server in my 20H2 still does NOT accept connections

    Regards

    Was this answer helpful?

    0 comments
  5. Anonymous
    2021-01-11T17:48:11+00:00

    Try this. I have solve my problem.  I have tried many time on different version, that works.

    Run regedit

    HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\NlaSvc\Parameters\Internet

    Change the EnableActiveProbing to 0;

    • Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\NlaSvc\Parameters\Internet]

    "EnableActiveProbing"=dword:00000000

    （Sorry my English is poor.)

    ----------------------------------(google translate)--------

    1. After you log in with VPN, in an environment without internet, windows will automatically redirect to: www.msftconnecttest.com/redirect, and disconnect the VPN connection.
    2. If the VPN can access the Internet after logging in, the VPN will be normal after the windows redirect to www.msftconnecttest.com/redirect.
    3. This is why some people can log in to vpn and some people cannot log in.
    4. I have encountered this problem for more than a year. I have been using the ltsc version. Yesterday, after I tried to disable the redirection, the VPN became normal. I tried other versions of windows, which also solved the problem.

    you can try it.

    Hello,

    Works fine only disabling probbing, but works too unblock the urls www.msftconnecttest.com, v4ncsi.msedge.net and ncsi.4-c-0003.c-msedge.net in the internal firewall.

    Thx

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments