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-11-15T08:11:45+00:00

    After the November updates, the problem no longer exists.  I haven't moved to 20H2 yet.  It was some kb installed in the November updates.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-11-15T07:59:09+00:00

    Tried to update the server yesterday with 2004, it gave version 19041.630. 

    Same problem, integrated VPN server locks in the connection "connecting to...." I installed the last SSU and tried with kb4580364, but this one says "not applicable to this system".

    I am trying to use PPTP with userid and password.

    I also tried uninstalling and reinstalling the WAN Miniport drivers, Windows reinstalled them, also delete the "incoming connection" and redefined it. No way, same bad result.

    Client is Windows 2004, 19041.630

    Restoring back the server to 1909 VPN works perfectly again.

    Any further idea of help?

    Thanks

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-10-28T13:10:03+00:00

    We have about 1000 employees using VPN, some solved the problem, updating to 20H2, but others not.

    We using two authentication radius servers, NPS and FreeRadius, if I use the user that the server authentication is NPS, works fine, but If I use the user that server authentication is FreeRadius, doesnt work.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-10-26T17:08:36+00:00

    According to the Windows Insider blog, this should be fixed in the October 22nd patch for 20H2: https://blogs.windows.com/windows-insider/2020/10/22/announcing-windows-10-insider-preview-build-19042-608-20h2/

    It's likely this is only showing up for those in the Release Preview ring, but if past experience is anything to go by, this should wind up in the November Windows Update release for both 20H1 and 20H2. There's also a chance it shows up in the out of band patch release either this Tuesday or next Tuesday for 20H1 before the regularly scheduled release.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-10-26T16:52:30+00:00

    Very good. Thx a lot!!!

    Was this answer helpful?

    0 comments