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. Anonymous
    2020-07-13T01:10:46+00:00

    I've try to remove all vpn virtural apdater driver in device manager, reboot, then problem have been resolved!

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2020-07-14T18:20:57+00:00

    Just spent whole day deploying fresh l2tp-->Mikrotik-->Radius-->WinSRV2019 NPS and searching for solution to this problem.

    Our findings indicate, that 2004 when using Windows log-on name and password does pass forward domain name. NPS is actually receiving user.name instead of domain\user.name, thus failing to authenticate user. Only option now to actually store credentials with connection in form domain\username

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2020-07-14T19:59:08+00:00

    Going to add myself to the list of companies experiencing this.  Hopefully a fix is released during today's patch cycle as we have a number of employees affected by this (just started deploying 2004 last week).

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-07-15T21:43:34+00:00

    I'm going to piggyback on this. Our organization is also experiencing this issue and it's been quite a nuisance especially since we're all working remotely due to Covid-19.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-07-17T14:19:52+00:00

    It gets better for us... If the VPN connection has any kind of hiccup (as lots of employees internet connection isn't the most stable), when they try and reconnect their credentials no longer work.  Being the good users that they are, they try and reboot to fix the issue.  Their cached credentials no longer work so they are now being forced to come into the office to log in and restore the credentials. 

    I may have to roll back to 1909 which wont be fun for the 50 VPN users...

    Was this answer helpful?

    0 comments