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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2020-08-05T12:48:34+00:00

    I agree that the WAN Miniports does nothing and even deleting windows credentials and letting the VPN re-establish them when i went into windows setting does nothing. it lets you put in the user id and password but becuase the end user is using MFA to log in, it is throwing an error. For Microsoft to be aware of this issue for two months now "investigating" , i can say the 'fix' is not in the July Cumm update and nor is it being reported as an issue in the FP 2004 issues page. this leads me to believe it isn't on MS radar and then can care less. 

    The other issue our users are starting to see is if they log on with MFA, it will log them off before getting to the sign on screen and then they login again with MFA (CAC Card) it will get to desktop then log them off. Third time is the charm but i have heard reports of a 4th attempt. Not for this thread but is the only other issue i see with MFA and Credentials.  (we set policy to log off if MFA removed so i am investigating this one and it may be for another thread. )

    Thank you,

    Dean

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-08-05T12:30:49+00:00

    Is there any way to store the credentials in the credential manager (without them being overridden by the dialogue mentioned before)? If yes, where?

    Or is there any other positive experience in the meantime? (deleting WAN miniports didn't help me)

    Was this answer helpful?

    0 comments
  3. 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
  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-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