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-08-05T13:41:04+00:00

    This issue not being on MS' radar would be quite a shock. We have a pandemic and VPN is more important than ever... 

    Oh i agree it is important as my boss wants a solution despite it being an MS issue. Its getting frustrating that we have to wait till august or September because it is such a hot item for us. I cant keep telling the boss  "We are waiting for MS but have this work around." 

    I would be happier if it was posted on the FP2004 issues page for tracking. 

    Thank's for the update, at least i can tell him Hopefully August - September time frame. 

    Dean

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-08-05T13:23:56+00:00

    Agreed

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-08-05T13:05:07+00:00

    This issue not being on MS' radar would be quite a shock. We have a pandemic and VPN is more important than ever...

    Was this answer helpful?

    0 comments
  4. 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
  5. 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