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-07-22T07:20:08+00:00

    Cary, thanks for that suggestion to delete and re-install the WAN MiniPorts as it seems to have worked for me. 👍

    Hopefully we don't have to do this every time.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-07-22T07:29:11+00:00

    Andrew, Carry, 

    What exactly did you do to make it work? Deleting all WAN MiniPorts, deleting the VPN connection, reboot, new setup didn't work for me, unfortunately.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-07-22T07:43:07+00:00

    Hi OliKr

    What you describe is pretty much what I did.  Deleted and re-installed the VPN's as an initial attempt but that did not fix the problem.  However deleting all the WAN MiniPorts and re-installing them does seem to have resolved the problem.  I have an HP EliteBook x360 1040 G5 running Windows 10 Enterprise version 10.0.19041 build 19041.

    The only other thing I might add is that we use two factor authentication and just prior to re-installing the MiniPorts I had a prompt to re-enter my 2FA credentials.

    regards

    Andrew

    Edit: Just had a minor hiccup where the VPN appeared to have timeout.  I tried to reconnect and got a message to say port was already open.  Hit reconnect again and all worked again.  So working but not 100% reliable yet.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-07-22T16:15:11+00:00

    What is being described here sounds to me like the issue being investigated in this TechNet posting:

    VPN connection prompts for credentials even if [Automatically use my Windows logon user name and password] enabled on 2004

    I do not have any additional information beyond what is contained on the TechNet thread. Microsoft is investigating the issue.

    Paul...

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-07-24T12:27:20+00:00

    Adding my comment on this as we are experiencing the same issue since the windows 10 2004 update. 

    The L2TP vpn client now constantly fails to connect to meraki client vpn. 

    The settings of the windows 10 gui and the control panel adapter page appear to be in conflict.  By which I mean that when you set the VPN to password authentication in the Windows 10 Settings gui it resets the network adapter security tab settings and then when you edit the control panel network adapter properties for the vpn connection under the security tab to allow the protocol for PAP it resets the windows 10 VPN gui to general authentication. 

    The two therefore remain in constant conflict and setting one, unsets the other...

    Was this answer helpful?

    0 comments