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 No comments

107 answers

Sort by: Most helpful
  1. Anonymous
    2020-06-26T12:56:55+00:00

    Thanks for the neat tip.

    I your connections are available to all users, you will want to use the following path:

    C:\ProgramData\Microsoft\Network\Connections\Pbk\rasphone.pbk

    Z.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2020-06-25T13:35:03+00:00

    Great option Dean.

    by the way it's shows in wireless area, vpn section that it's connected (at least in my cases) strange one...

    In addition to Dean option, for non multiple option could be done just by creating a new shortcut and placing this:

    rasphone -d "VPN connection name"

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2020-06-25T11:33:39+00:00

    Thanks for the update and fix.

    If only Microsoft could move this fast

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2020-06-25T10:11:58+00:00

    Not as yet, I escalated through our Microsoft Rep but mum's the word

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2020-06-25T09:43:49+00:00

    Yeah, same issue here. Anyone have more info about this yet?

    Luckily discovered this issue on our Test machines before pushing Win 10 2004 Upgrade to all users.

    Was this answer helpful?

    0 comments No comments