After upgrading to 1903, our (SSTP) VPN doesn’t work anymore.
Error message: Can’t connect to VPN. An existing connection was forcibly closed by the remote host
Tested on multiple machines with 1903, older versions still work.
Do any of you also have this issue?
Edit: There seems to be a lot of different solutions here, however none of them worked for us. What solved it for us was installing a new server 2019 with VPN. It is weird that this worked since they were setup with the same settings, it must be one of those M$ things.
I had a machine dropped off for being unable to connect to the VPN. Ran updates, got stuck on 1803, ran the manual update hoping to upgrade to 1809, jumped to 1903 and VPN started working again.
Windows 10 update needs to improve. This shit should have worked day one if they planned on doing these rolling releases.
Cyle here from South Africa…i too had this issue…fix i found…in your control panel\network and sharing centre…change adaptor settings, right click onyour VPN connection go to properties…on the security tab make sure “Automatically use my windows logon name and password(domain if any)” is ticked this should then work.
My VPN to Ubiquiti gear is also glitchy (L2TP) - but I noted that it was not the VPN end of things but rather the 1903 OS itself. If I clicked the network icon in the system tray and tried to connect to the VPN in the list it would never connect (not even prompt). If I opened the settings app and go to the VPN I was able to connect - so something weird there. I did not try it via the control panel / network connections but still…training users to go this route for their VPN is a PITA. Holding my business off from 1903 until this gets fixed.
Also had previous issues with 1809 where the VPN would just always show connecting but never connected - yet it was connected and data was fine. I swear - if MS is going to market a “PRO” version of their software, then it should work as advertised…
I use a PPTP VPN that shows the same problem in 1903. If I create the VPN through the Control Panel, it does not work. But if I do it through Settings and then modify it through the Control Panel, it works perfectly. I hope this helps someone
I had a similar error message where it was saying that it could not connect due to a firewall or other issue.
I work remotely and tried a few options that worked once or twice but did not work consistently.
Add a REG_DWORD value of 2 for AssumeUDPEncapsulationContextOnSendRule under HKLM\SYSTEM\CurrentControlSet\Services\PolicyAgent in the registry. This worked once or twice but not the next day.
Clear the credentials cache and then re-enter my domain credentials, worked once, may have been compounded from the other solutions though.
Remove my home network from the equation and connected to my cell phone’s wireless hotspot. This created a “public” connection under Windows Networking, so I then went and temporarily disabled the “public” Windows Defender firewall, this worked but I knew I’d get the banhammer for leaving this as is.
The “most-stable” solution I’ve found so far is to go into the VPN networking adapter and disable IPv6 connections, magically it started connecting again!
It may be worth noting that my coporate VPN uses M2FA and requires hitting “Approve” in response to a push notification on a cell phone using Microsoft Authenticator before the connection is established. Usually once I see that message a push-notification comes though, but it seemed almost like it was timing out or getting denied connection.
My problem is that it wasn’t even getting to that step before, it was getting to the “Verifying your sign-in” stage and then dying, saying that some firewall/NAT was preventing the connection.
I’m an amateur at this and my troubleshooting was mainly done to prevent myself from having to raise a ticket with IT and potentially drive into the office in another state. If this gets the gears turning in anyone’s head and they can narrow down the issue, I’d love it if you could help me craft this into a less trial-and-error solution that I can send off to my IT dept. Then I can pray the don’t murder me for upgrading my dev machine to 1903.
with 1903 MS in their wisdom no longer ask for a username and password - I have found that you have to modify the VPN connector under advanced settings (via settings) when the connector will then connect as it did before.
The only problem with this is that the username and password are saved and this is not something I would advise portable users to do.
Wow it’s August 13, 2019 and this is STILL broken in 1903. I’m connecting to a Meraki via L2TP/Ipsec w/ pre-shared key. If I run rasphone.exe it will connect that way.
Had this too with OpenVPN, had to uninstall the tap adapter, reinstall as admin. Recreated the profile, some reason (maybe wrong here) started working after disabling Windows Firewall and installing Sophos Endpoint - although I did do a lot of stuff trying to figure out why it wasn’t working.
I"m having issues on 1903 with VPN configured for L2TP with preshared key. Also configured to work with DUO(no encryption and PAP). It won’t get passed “Connecting…”
I have another VPN configured L2TP with preshared key but without the DUO changes and that one works.
