This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I am an IT technician at an IT company. One of our clients has asked us to install a fresh version of Windows onto 6 of their PCs.
These PC's are old PC's that they do not use - meaning that they have had a fresh version of Windows installed onto them. This has been upgraded to 1903. I have attempted to setup a VPN connection in order to connect the PC's to the company's domain. When doing so, the VPN connection just hangs on 'Connecting to vpn'
I know 1903 is still very new into the world, but wondering if anyone knows how this issue can be resolved?
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.
We are using Windows Server 2016 Remote Access. I believe the service on the clients that stopped working after the update was RASMAN. This solution is a L2TP VPN. When I troubleshoot I keep getting the error from the direct access troubleshooter that it can't tunnel to the direct access server but no errors are thrown when I run netsh in httpstunnel show int.
Hmm I see we are using Cisco Appliance for L2TP VPN and it works fine after applying (KB4522355) update...I hope you will get it to work
The update to v1909 resolves the issue
Well, nevermind. It still isn't fixed. Still hangs on Connecting... from the task tray, but connects fine from the Settings VPN menu. Five different test boxes and two VMs still show no change from before the KB was installed.
Whatever they "fixed" in KB4522355, it wasn't in the task tray GUI. Come'on Microsoft...test your fixes before you deploy. I'd love to write **** software, never fix a critical bug, and still get paid!
odd. the KB resolved it for 3 of the machines I tried it on. Maybe try installing it again? What VPN type are you using ?
The update to v1909 resolves the issue
But it's broken again in the next insider build that followed, and the next on after that :P. Get your **** together MS!
It doesn't matter what type of VPN. It's the GUI that's broken from the tray, NOT the actual connecting of the VPN. Connect from the VPN panel in settings and it's perfect, but from the tray, it'll occasionally work, but will usually hang on "Connecting". Cancel it and connect the same VPN from the Settings panel and instantly connects.
And while 1909 works a bit better, it still will exhibit the same behavior occasionally, especially after a reboot.
