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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2020-10-30T21:36:06+00:00

    This problem appears to be fixed as part of Windows 10 KB4580364 Preview.  The changelog for that KB includes this:

    ·         Addresses an issue with virtual private network (VPN) connections that use Secured Password (EAP-MSCHAP v2) for authentication and have enabled the “Automatically use my Windows logon user name and password” property. When you connect to this type of VPN, an authentication dialog box incorrectly prompts for your credentials.

    https://support.microsoft.com/en-us/help/4580364/windows-10-update-kb4580364

    Was this answer helpful?

    3 people found 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-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
  4. Anonymous
    2020-11-15T08:53:14+00:00

    Thanks for your answer.

    After Updating to 2004, I tried to look for additional updates, but the only one that came was for NET.

    Looking at the client, it seems that there is an additional one: KB4586781, I will do an additional try today and try to download the independent update for that one and look if it can be installed and if it solves the problem.

    Regards

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-11-15T15:37:36+00:00

    No way :(  , I updated my windows 10 to 2004, then latest SSU, then tried KB4586781 that seems to be November cumulative update, this last one said it was already installed, uninstalled WAN Miniport drivers, deleted incoming connection, restarted system, redefined the incoming connection using PPTP...

    Same result

    VPN from the client locks at "connecting to...." message

    Again, stepping back to 1909 and keeping the client at 2004, VPN works again.

    Any other idea of help? Should I try 20H2 if there is any way to do it?

    Thanks

    regards

    Was this answer helpful?

    0 comments