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.
It is waiting on credentials and because the "Type of sign-in info" is likely set to "General Authentication". Go into the VPN connection's advanced options and click "Edit" underneath the connection. From there, change "Type of sign-in info" to "User name and password". Now it will prompt from the tray when you click to connect it.
Um, No. Wrong. It's waiting for credentials because of a bug in the tray code with SAVED credentials.
It is waiting on credentials and because the "Type of sign-in info" is likely set to "General Authentication". Go into the VPN connection's advanced options and click "Edit" underneath the connection. From there, change "Type of sign-in info" to "User name and password". Now it will prompt from the tray when you click to connect it.
Well that would be great, IF you wanted it to query for the login each time. When you have dozens of VPNs that you connect to, each network with different passwords, it's a pain to do that. It needs to just remember the password, and connect reliably with proper GUI messages.
It's actually still broke, even after the 1909 release and some time. Most times, it'll actually be connected, but with the tasktray network list still showing "Connecting...". So the GUI issue is still present as of January 2020. Connecting from the Connections panel in Settings works instantly and shows the correct messages.
I am running 1909 and as with most I have reviewed, my VPN connections from systray just stopped working one day. Microsoft magic! I finally took some time to look into it on my machine (got tired of going to settings). I am hoping I can get some confirmation to a fix.
Go to the VPN adapter in your Control Panel=>Network and Sharing=>Change Adapter Settings. You should see the VPN connection as an adapter. Right click and select properties, on the options tab click "Remember my Credentials".
Open the connections from your systray and connect to the VPN. You should be prompted for Creds. Enter them and it connects as normal.
Let me know if this helps you, it bugged the bejeezus out of me.
I have the same issue too. Just try to install a VPN in your browser like extension.
What does this have to do with the issue at hand? And why is there a link to some useless review of a crappy consumer VPN? The issue is a VPN connection problem via the TRAY GUI, not a VPN connection issue in general, and is due to a bug in the tray GUI that Microsoft does not acknowledge nor seem to care about and hasn't been fixed despite being around for quite a while.
And yes, even in 1909, with all of the supposed "fixes", it still exists. Funny thing is when connecting from the tray, the GUI hangs on "Connecting..." and the Connect button never changes to "Disconnect", but an IP does get issued and the VPN is connected (sometimes).
Going to the VPN connection panel will still show the same status. However, Cancelling the connection there and hitting Connect will succeed.
Either way, it's ridiculous that this has been around for this long and Microsoft would rather waste time figuring out what new icons they can create for emojis and other consumer ****.
