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
    2021-05-18T22:06:15+00:00

    Allan, thanks, even now PPTP works again, I will do a test in my system of what you tell.

    Thanks again and best regards.

    Javier

    Was this answer helpful?

    0 comments
  2. Anonymous
    2021-05-18T21:21:44+00:00

    What I found to be our issue was Windows Defender.

    We were originally using another antivirus application and shifted over to Windows Defender.

    L2TP vpn stopped working.

    Prior to moving to Windows Defender, I followed the instructions from Windows Report:  https://windowsreport.com/cannot-connect-l2tp-vpn-windows-10/

    That worked and the VPN did as well.  Enter the transition to Windows Defender and the VPN stopped working.

    In Step 7, from Windows Report, they have you create an Inbound and Outbound port rules and set them to "Allow the connection if it is secure".

    I changed the setting on both Inbound and Outbound from "Allow the connection if it is secure" to "Allow the connection".  Boom!  VPN now connects.

    Not 100% sure if this is ideal or not, but it does allow the VPN to connect.

    Was this answer helpful?

    0 comments