This is causing a whole host of issues on Win 10 Enterprise.
Our VPN kills the session periodically. Once this happens any attempt to reconnect matches the symptoms of multiple threads on here. I need a solution to save restarting. There must be a way?
It wouldn't be so bad if after the disconnect a restart takes between 5 and 10 minutes to shut down.
I have tried enabling the adaptor, and the "repair pulse secure" which led to a installer freeze that I left for 30 minutes, then cancelled and left 30 minutes. Then needed to kill that and restart twice to get back on to the VPN.
Surely there must be a solution after all this time?
One thing I can rule out, is there are a few mentions of 2 Juniper devices needing to be present, I am now back on the VPN and confirm only the Juniper Networks Virtual Adaptor is required.
Solved! Go to Solution.
The 1205 error can be for many reasons. Below are some articles that may be of some use.
Thanks, I'd already been through these.
KB40347 mentions:- Please verify the following virtual adapters are installed and operational.
But when on the VPN the manager is not shown so I think this is a red herring, or bad info. Also the solution of reinstalling every day is not a viable option.
I'll check the others next time it happens. The funny thing is I've just started in an office where everyone just accepts they restart a couple of times a day to fix PulseSecure, and I'm seen as wasting time by getting to the bottom of this. Is this being addressed by the Dev team here do you think or is it just accepted with PulseSecure that regular reboots are needed? Like 90's Microsoft operating systems :-)
When I got my 5 minute warning I disconnected gracefully. Left it 5 minutes and tried to connect again.
"Waiting to connect..." graphic has now been spinning for 3 hours.
Have found I can just about get by with Citrix desktop so just going to use that.
Just use CITRIX. Forget PulseSecure if you want to hibernate your laptop. Have to restart for every VPN session.