It is - the last I read that it was to be resolved in another update end August early Sept but truly, who knows? Seems like their recent backdoor security issues are bigger fish to fry.
VPN not working on Windows 10 1903
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?
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.
118 answers
Sort by: Newest
-
Anonymous
2019-08-19T15:49:59+00:00 -
Anonymous
2019-08-18T00:33:52+00:00 This is still an issue. Any resolution or patches yet?
-
Anonymous
2019-08-18T00:33:13+00:00 This is still an issue. Anyone come up with a fix or is there going to be a patch to fix this?
-
Anonymous
2019-08-09T13:31:14+00:00 I had this same issue with the "hanging" connection, and tried some of the suggestions. In my case, the issue is not with the connection, but there is a break in launching the "credentials window" from the hidden icons VPN shortcut.
I discovered I could connect through the Network Setting for my VPN; however, if I tried to connect to my VPN through the lower right corner (hidden icons ^), I received the "Connecting to.... VPN" but the credential window wouldn't open and it just hanged.
-
Anonymous
2019-08-07T20:23:16+00:00 One way to workaround this VPN issue in Windows 10 - 1903 (and it is a workaround NOT A FIX) is to use the VPN Connect option in the Windows Network Settings window to get the login screen to pop up. And, NO setting the VPN to "Remember your Sign-in Info" is NOT a good solution. This just causes another issue, because when the user's AD password expires, the user is not informed that the password is expiring/expired and the VPN connection still does not present the login screen. VPN just throws a connection error and the End User is what do I do now..... What they do is, call IT... Like we need more work. By the way, the default setting of "Remember my Sign-in Info" for the VPN connection is BAD SECURITY!!!! We want the user to know their AD login ID and password and use it every time they access the network remotely!
We don't want End Users mucking around in the Network Settings, nor do we desire to teach them how to clear their VPN sign-in info when their AD password expires.
THIS IS A MICROSOFT BUG THAT NEEDS TO BE FIXED PURE AND SIMPLE!!!!!
Other VPN suggestions:
-Make NOT REMEMBERING the sign in info the default. If an admin wants to change it, then it's a conscious decision to trade convenience for security.
-Inform the End User when their password is expiring IN ADVANCE if possible across the VPN connection.
-If the password is expired, then automatically clear the sign-in info, TELL the End User, and then present a login screen.