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: Oldest
  1. 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
  2. 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
  3. Anonymous
    2020-07-10T16:48:43+00:00

    Microsoft is currently investigating this behavior. Please hold on and wait for the future patch.

    It seems to be appearance problem. the dialog pops up asking user to type-in user credential, but not really mean any previous authentication has failed. the dialog is displayed even before any actual user authentication is attempted.  You can type-in any random username and password and hit enter. the typed in info will be discarded and still use your current Windows logon name and password to finish the authentication and VPN will be connected with the correct user credential. 

    so far, no workaround truly works, unless changing the authentication method away from using user name and password (for example use certificate instead) .

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2020-07-10T19:05:18+00:00

    Yes it's true. I will wait for Microsoft's fix.

    Microsoft is currently investigating this behavior. Please hold on and wait for the future patch.

    It seems to be appearance problem. the dialog pops up asking user to type-in user credential, but not really mean any previous authentication has failed. the dialog is displayed even before any actual user authentication is attempted.  You can type-in any random username and password and hit enter. the typed in info will be discarded and still use your current Windows logon name and password to finish the authentication and VPN will be connected with the correct user credential. 

    so far, no workaround truly works, unless changing the authentication method away from using user name and password (for example use certificate instead) . 

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2020-07-10T19:26:59+00:00

    Doesn't work for me. When I enter a random password (username is given and always my Microsoft account) I gte the error "Connection with <...> not possible. PPP connection protocol terminated" (translated from German, so probably a little different).

    Was this answer helpful?

    0 comments No comments