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. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  2. Anonymous
    2020-11-18T15:28:48+00:00

    New trial, new NO solution.

    I have installed 20H2, uninstalled WAN miniport drivers, deleted entry connection, restart, drivers automatically installed, defined new entry connection... same BAD result, trying connection to VPN from the client stais locked in "connecting to....."

    Looked for new updates... only the Net framework one. Tried to install the November cumulative update, "already installed in this system".

    Framework and antivirus stopped, same, no connection.

    So, again VPN integrated server doesn't accept PPTP connections. Restored 1909 version, it works again.

    Any other idea of help?

    Regards

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-11-19T08:01:04+00:00

    I tried to use L2TP protocol, but it doesn't work either, even in 1909 it doesn't connect from my Windows 10 2004 (client) to my Windows 10 1909 (server). It stays locked at "connecting with...". As soon as I change to PPTP, it works perfectly, but it doesn't when the server is upgraded to 2004 or 20H2.

    Please, any idea or plan of help? Should I stay forever in 1909 in the VPN integrated server?

    regards

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-12-10T21:59:25+00:00

    I had this problem. Tracked down that if I go to Device Manager and remove all the WAN Miniport protocol versions, Scan for Hardware Changes and let Windows re-install all the Mini port drivers, It seems to be working now. Hope this helps. Had to recreate the VPN connection. Using L2TP to Meraki.

    Can confirm!

    Removing all WAN Miniports and creating the VPN again seems to work ( L2TP PSK )

    Thnx Cary B

    Various sources also report issues with xbox live.  Specifically, try disabling the xbox live networking service. Also google this issue.  MS has not properly addressed it.  Uninstalling all the WAN Miniport's and adding back did not work for me.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-12-10T22:24:43+00:00

    Thanks, I looked for XBOX services and the two of them (network included) are stopped and in manual status, at least in 1909, next time I will upgrade to either 2004 or 20H2 my VPN integrated server desktop I will check them for the case they have a different status.

    regards

    Was this answer helpful?

    0 comments