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
    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
  2. Anonymous
    2020-10-22T17:31:07+00:00

    Just updating this post to say that I have solved this issue, but not by doing anything suggested here. My ISP does not give enrollees static ips. They are dynamic and are behind double NAT. It would appear that whatever Microsoft is doing to enable this VPN cannot work under these conditions. 

    I had to upgrade my line to a static ip which will cost me $10/month extra. 

    Shame that Microsoft can't handle this. Not everyone has a static ip.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-10-22T11:50:39+00:00

    I tried this a while ago. And again today. Doesn't work for, neither deactivated nor activated.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-10-22T08:20:01+00:00

    I solved it by deactivating the "Automatically use my Windows log-on name and password (and domain, if any)" option.

    It seems to work in contrary, re-activating it Windows asks me for the password when I try to connect to the VPN.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-09-15T19:52:45+00:00

    Just want to add in here that I've been trying to solve this issue for MONTHS and literally nothing is working. 

    None of the fixes or workarounds presented in this thread are working for me. I am able to connect to my l2tp vpn perfectly fine with any mobile device or my OSX clients but not a single one of my windows clients can connect (tested on a custom built pc as well as a SP4 - both fully up to date).

    Every work around presented has resulted in the same error and inability to connect to the remote network. I haven't been able to connect my main work-from-home pc to my work network since June. I've resorted to my super old macbook pro because it doesn't have this malfunction. 

    It's baffling to me that Microsoft can't solve this or address this in a timely manner.

    Was this answer helpful?

    0 comments