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
    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
  2. Anonymous
    2020-12-23T04:55:50+00:00

    SSTP VPN here. No issues since the November update. Tried with both 2004 and 20H2.

    L2TP VPN here, literally just applied the KB here https://support.microsoft.com/en-us/help/4592438/windows-10-update-kb4592438, and I can confirm this is now resolved for me - after a year of waiting! :)

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. 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
  4. Anonymous
    2020-10-19T03:29:56+00:00

    Hi AyrA.ch, your registry change that you suggest in your Data Protection API post seems to have fixed my VPN issues.  For anyone else interested in trying this then here's the link and the registry edit that seems to have resolved the problem on my PC.

    https://answers.microsoft.com/en-us/windows/forum/windows_10-security/data-protection-api-dpapi-seemingly-broken/3f37f1dc-2e74-4ee1-8de8-84a1923082a6 

    Potential solution:

    1. Open the registry editor
    2. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\Protect\Providers\df9d8cd0-1501-11d1-8c7a-00c04fc297eb
    3. Create a DWORD value named "ProtectionPolicy" and set it to 1
    4. Reboot

    UPDATE:

    I spoke to soon.  Although this appears to have improved my VPN experience it has not fully resolved the problem.  Here's hoping the MS update mentioned in other posts fixes all our woes.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. 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.

    Was this answer helpful?

    0 comments