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-23T18:27:30+00:00

    We are experiencing the same problem with Windows 10 2004 and 20H2:

    • Despite SSO enabled the user gets presented a password prompt saying "Action needed"
    • The user can enter ANY password to successfully connect
    • Initiating the connection from the command line with "rasdial" works with SSO
    • No changes on the server side and no errors logged on the server

    It seems to be a GUI problem as it only occurs when initiating the connection from the GUI. I have raised a pay per incident support ticket with Microsoft yesterday and am waiting for their response now. I've also linked this thread within my ticket.

    Michael

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2020-10-23T20:25:21+00:00

    Michael,

    Same behavior in observed in our environment. We are holding back updating to 2004 and beyond until this issue is resolved. 

    Thank you for opening a pay per incident support ticket with Microsoft.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-10-24T08:57:19+00:00

    Microsoft Support sent me the following questions to answer which I already have. Maybe some of you may answer them as well and post this here in the thread so Microsoft sees this:

    1. The complete problem description
    2. Is the problem reproducible?
    3. What are the steps in order to reproduce the issue?
    4. The exact text of the Error message and the Error Code which is triggered during the repro
    5. How does the problem begin to appear \ how does it show?
    6. When was the problem first observed?
    7. How long is the problem persisting? How often does it occur? When does it occur?
    8. What were the steps that you performed when the problem occurred?
    9. Did this configuration / setting ever worked? Is yes, when and for how long did it work?
    10. What Documentation did you follow / use to implement the current configuration? Can you please provide us theses?
    11. Was there any Hardware or Software change undertaken?
    12. What is the difference between the current status and the status when it previously worked?
    13. What steps have you or the “User”  performed to (try and) solve the problem?
    14. What OS are implicated in the configuration / problem that you have? What Version Number / build?
    15. Are the Machines up to date? What KB’s have been installed the latest?
    16. Are there any Event Logs / Error Logs being triggered when the problem occurs?
    17. Do you have a “Workaround” in place at the current point in time?
    18. What is the Business Impact and how fast do you need a solution?
    19. Do you have the possibility to provide us with a Network Plan / Network View / Visio?
    20. Is the Problem persistent or sporadic? Are all Clients affected?
    21. Is only the Client Side affected or also the Server side?
    22. Are there any Systems in your environment that are not affected by the problem?
    23. Did you mange to observe any similarities / differences in the GOOD and the BAD case scenarios?

    (Load based / User based / Machine based / Configuration based / Time based / Subnet based / Localtion based….?)

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-10-26T14:49:01+00:00

    Hi all,

    I just got an answer from Microsoft stating that they found the issue and it will be fixed in the next cumulative update at least for update 20H1 (no mention of 20H2 so far but I guess it will be fixed there as well):

    [...] We found internally filed Bug. This is the only impacted release (20H1). The fix release date is 10C.2020 (preview), and will be included in 11B.2020. Any 20H1 machine applied monthly rollup equal or newer than this shall no longer experience the issue. The fix release date is 10C.2020 (preview), and will be included in 11B.2020. Any 20H1 machine applied monthly rollup equal or newer than this shall no longer experience the issue. [...]

    I guess 10C.2020 means the preview of the next cumulative update. Does anyone know how to get the update in order to test it?

    Best Regards

    Michael

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-10-26T15:29:02+00:00

    Michael,

    thank you very much for taking care and making sure that MS is getting aware. Shame enough that they don't read their own forums like this one. Anyway ...

    I'm only confused about the versioning that MS is referring to. I'm on Version 2004 (Build 20221.1000). Is this a version that's still expected to have the issue? Or is it a version that MS says it does not have the issues (it still has!!!)?

    Was this answer helpful?

    0 comments