cancel
Showing results for 
Search instead for 
Did you mean: 

Pulse secure stuck at securing connection and fails with 1205 virtual adapter not found

Occasional Contributor

Pulse secure stuck at securing connection and fails with 1205 virtual adapter not found

Hi all,

 We started to run into this issue recently where a lot of our users were seeing error 1205 virtual adapter not found. We opened a case with pulse secure but haven’t been able to narrow down this issue. We do see that the juniper drivers get deleted and repairing the pulse secure client will fix it but the issue comes back. I’m quite lost on this issue so I wanted to check if anyone has experienced it. BFE is turned on in our case. We are running windows 10 x64 LTSB 1607.

thanks

 

20 REPLIES 20
Moderator

Re: Pulse secure stuck at securing connection and fails with 1205 virtual adapter not found

Are you using Carbon Black, SEP, McAfee HIPS, Cisco AnyConnect, Jabber?
If yes, can you uninstall Carbon Black, AnyConnect, and/or Jabber (as well as Pulse), reboot, and test again?
Alternately, can you disable the driver filter from the Pulse adapter and test?
Occasional Contributor

Re: Pulse secure stuck at securing connection and fails with 1205 virtual adapter not found

Thanks for responding on this. We are using SEP. I have also seen this issue happening when I have only windows base image installed and pulse secure on it. Maybe I will try having windows defender disabled and observe. It seems like something is tearing down the virtual adapter as observed from the logs. If I repair the connection it connects but second attempt gives me same error again.
Occasional Contributor

Re: Pulse secure stuck at securing connection and fails with 1205 virtual adapter not found

I meant if I repair pulse secure from the installer then it will work once but then the second attempt will fail.
Occasional Visitor

Re: Pulse secure stuck at securing connection and fails with 1205 virtual adapter not found

Please let us know if you find the solution.

We are having the same issue (also have Windows 10 x64 Enterprise LTSB 1607 + SEP)

For us, it started on or about February 20th.

We have been uninstalling/reinstalling as a temporary fix.

 

Visitor

Re: Pulse secure stuck at securing connection and fails with 1205 virtual adapter not found

A bunch of our users also starting to have this issue out of nowhere, I'm suspecting a patch got installed.

Moderator

Re: Pulse secure stuck at securing connection and fails with 1205 virtual adapter not found

@Pretambey: thank you for the update. This does indicate that something on the system is blocking the driver from operating properly. Do you have DHCP media sense enabled or disabled?
When you refer to the Windows base image, is that the company base image or a clean install of Windows? If the former, are there any other VPNs installed? Are there any VoIP applications installed?
Occasional Contributor

Re: Pulse secure stuck at securing connection and fails with 1205 virtual adapter not found

@zanyterp I do not know what is DHCP media sense but we do not use it. This is clean install of windows 10. Do you think windows defender could be causing this issue? That's the only common link I see here.

Occasional Contributor

Re: Pulse secure stuck at securing connection and fails with 1205 virtual adapter not found

Our assumption regarding windows defender was wrong, it still failed. So clearly there is something which keeps deleting the jnprva.inf_amd64_80b297ba301623ad from C:\Windows\System32\DriverStore\FileRepository

We still don't know why. Any ideas?

Community Manager

Re: Pulse secure stuck at securing connection and fails with 1205 virtual adapter not found

Please confirm the following conditions are met:

 

  1. Endpoint should have KB4023057 installed
  2. From the device manager menu, the virtual adapter should be labeled as "Juniper_Networks_Virtual_Adapter_01" under "Other Devices". 
  3. Double click on the problem adapter and confirm from the "Events" tab the device is deleted multiple times.

If this is correct, then try the following steps:

 

  1. Uninstall Pulse
  2. Reinstall Pulse and confirm it works
  3. Apply the workaround from the Microsoft KB