VPN not working on Windows 10 1903

The issue is down to Windows 10 1903, as I am using the Windows VPN RAS service a Windows Server  as the backend.  If I use any other version of Windows 10 I can connect to VPN fine.

I have found a potential workaround which mayindicate that this is NOT a Windows 10 issue. 

So here is what has worked for one of my client's employees. After exhausting all of my options trying every conceivable combination of VPN settings, Adapter Options and the VPN settings in the ASUS RT-3200 router, I came to the conclusion that it had might be something between her PC and the work router. 

I had everything on her PC set up exactly like mine (Antivirus, Windows version, VPN settings, adapter settings, firewalls, etc) - and mine connected almost instantly and hers did not. This just did not make sense, so I tried looking elsewhere for the cause of her VPN pain.

[snip]

What are you smoking? 'Cause whatever it is, we all want some.

Seriously, did you read anything before posting? This is NOT the issue. Paying a private VPN does NOT solve any problem. This is NOT a connectivity issue; it is a connect*ing* issue. It *is* a Microsoft issue. 

If going through a VPN to connect to a VPN works then it cannot be solely a connectivity issue. If it was, it would not connect through the VPN service.

Do you even know how VPNs work? Regardless of whether the Microsoft VPN client connects directly or through another VPN, it creates a virtual private network using the same connecting protocols. If this were a Microsoft protocol or connectivity issue it would not work through another VPN as the handshakes and connectivity do not change simply because you are tunneling through another VPN.

If you think otherwise, please explain how you think the Microsoft VPN client handshake or connection changes when going through another VPN as opposed to a direct connection and your reasoning for thinking that there is a change.

I have found a potential workaround which mayindicate that this is NOT a Windows 10 issue. 

So here is what has worked for one of my client's employees. After exhausting all of my options trying every conceivable combination of VPN settings, Adapter Options and the VPN settings in the ASUS RT-3200 router, I came to the conclusion that it had might be something between her PC and the work router. 

I had everything on her PC set up exactly like mine (Antivirus, Windows version, VPN settings, adapter settings, firewalls, etc) - and mine connected almost instantly and hers did not. This just did not make sense, so I tried looking elsewhere for the cause of her VPN pain.

[snip]

What are you smoking? 'Cause whatever it is, we all want some.

Seriously, did you read anything before posting? This is NOT the issue. Paying a private VPN does NOT solve any problem. This is NOT a connectivity issue; it is a connect*ing* issue. It *is* a Microsoft issue.

I have found a potential workaround which mayindicate that this is NOT a Windows 10 issue. 

So here is what has worked for one of my client's employees. After exhausting all of my options trying every conceivable combination of VPN settings, Adapter Options and the VPN settings in the ASUS RT-3200 router, I came to the conclusion that it had might be something between her PC and the work router. 

I had everything on her PC set up exactly like mine (Antivirus, Windows version, VPN settings, adapter settings, firewalls, etc) - and mine connected almost instantly and hers did not. This just did not make sense, so I tried looking elsewhere for the cause of her VPN pain.

First I deleted all of the VPN connections in VPN settings in Windows 10. I wanted a clean slate for this test. I also turned off her Windows 10 firewall completely, leaving only Eset Antivirus to protect her during this test.

Next I recreated a new, default VPN connection in VPN settings. I used the same settings that have worked for me all along.

Then, to try and isolate the issue, I installed Private Internet Access on her laptop (you could probably use any VPN provider, but I have been quite pleased with PIA and it's only $39.95 per year). I connected her to a local VPN through PIA (she's in Atlanta so I used a local VPN connection to keep ping times low) then I connected her to her work VPN as usual and everything worked. She connected almost instantly to her work VPN, going through the Private Internet Access VPN.

I restarted the firewall and tried without PIA and it failed. I retried using PIA and it worked.

I don't know what the core issue is here, but it does NOT seem to be a Microsoft issue. If the issue was with Windows 10, it would seem that the problem would persist no matter whether she connected to the work VPN directly or via the Private Internet Access VPN. If anyone knows a reason that my thinking on that might be incorrect, please let me know.

It may be her local modem/router. She is using an Xfinity modem/router. Maybe it has something to do with the updates to hardware and software between her and her work because of the NSA EternalBlue leak. I don't know. But I know that using a VPN service fixed her connectivity issue.

Please let me know if this works for you as well.