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-10-17T15:45:17+00:00

    I have the same issue and (in my case) was able to trace it back to the data protection API. A whole lot of other things are also broken, and no error is logged anywhere: https://answers.microsoft.com/en-us/windows/forum/windows\_10-security/data-protection-api-dpapi-seemingly-broken/3f37f1dc-2e74-4ee1-8de8-84a1923082a6

    If anyone is willing to test, try this tool on a broken machine: https://github.com/AyrA/DPAPITest

    It will not fix your problem, it merely checks if the data protection API is responsible for it, or if you have a different issue.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2020-08-05T13:12:57+00:00

    Microsoft is hoping to solve this problem in the August or September update.  I presume if you are not using windows credentials it is saved in the rasdial "phone book". I use a bat file to dial my secure connection (Windows credentials work fine then) one could always autrorun the batch file at logon for those who need auto-connect. The command is rasdial "Name of vpn connection". To autorun at logon create a string key in HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Run make the name anything you want to call it. value data would be the full path to the location of the bat file including bat file name and ext.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2020-07-14T18:20:57+00:00

    Just spent whole day deploying fresh l2tp-->Mikrotik-->Radius-->WinSRV2019 NPS and searching for solution to this problem.

    Our findings indicate, that 2004 when using Windows log-on name and password does pass forward domain name. NPS is actually receiving user.name instead of domain\user.name, thus failing to authenticate user. Only option now to actually store credentials with connection in form domain\username

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2020-07-13T01:10:46+00:00

    I've try to remove all vpn virtural apdater driver in device manager, reboot, then problem have been resolved!

    Was this answer helpful?

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