Pulse Secure 1205 error after 1st good connection

[pkjohn1]

Running Pulse Secure version 9.1.8 (3143) on Windows 10 (1809).  

After booting up, I can get 1 good connection from Pulse Secure.   If I disconnect and attempt to reconnect to the same or different VPN site, it fails during the Securing Connection step with 1205 error.

The only way to restore is to reboot.  However, the virtual adapter is stuck and won't allow the reboot to happen, it errors out and the error is reported to Microsoft before it reboots the laptop.

I've looked in device manager and before I start Pulse Secure client, there is no virual adapter.  Once I start it up, it creates the virtual adapter and I can connect (the first time).

Anyone have a suggestion on where to look for this?  

[flipPipe]

Hi,

With that behavior and if you have some Cisco software i bet in KB40351

If not, in KB40347, there are more possible solutions for that kind of problems.

In Device Manager, you must use the option to show hidden devices.

Best Regards,

[pkjohn1]

KB40351 wasn't applicable, do not use IP communicator.   KB40347 while more promising, is one I'd already seen.   The Windows version 1809 doesn't have a separate reliability tool, looks like it's rolled up into perfmon (version 10.0.17763.1).   

Prior to Pulse Secure version 9.1.4, there didn't seem to be any issues.   Only after that version and even 9.1.8, both exhibit the same issue.

One other interesting issue is that when you connect and disconnect from a VPN location, it shows disconnected. 

But if you try to connect to a different VPN location, it says you still have an active connection to the previous site.

If you try to reconnect to the first site, it give you the 1205 error on securing connection.

From what I was reading, it says that when you disconnect from VPN, the virtual adapter should dim (in device manager).  I guess to indicate it has been disabled.  However, it doesn't change at all.   It's almost like it never disconnects.

[pkjohn1 · Accepted solution]

Found the issue.   The Microsoft Wi-Fi Direct Virtual Adapter was binding to the Juniper Networks Virtual Adapter.   When you disconnected from a VPN location, the adapter was never getting disabled.   So if you tried to re-connect, the connection info still showed an active connection and it couldn't 'enable' the adapter.    If you tried a different location, the adapter was already enabled (connection info for the first location) so it says you are already connected to another location.

Disabling the MS adapter allows the Juniper adapter to get disabled and re-enabled properly.