Pulse Secure engineering is currently investigating this issue. This article will be updated with with the fix details once the issue is identified and resolved.
The following workarounds have been implemented by customers and have been reported to help.
Workaround 1: Disable the Juniper Network Services from the wireless and virtual adapter: (If the Pulse connection is being used to connect to an SRX device, then this should not be performed. See below for a workaround that can be applied to SRX connections.)
- Open Control Panel and select Network and Sharing Center the select Change adapter settings.
From a DOS command prompt run the command:
-Start > Run > ncpa.cpl
- Locate the wireless adapter in the Network Connections and right-click on the adapter and select "Properties".
- Disable the Juniper Network Service by deselecting it.
- Connect with Pulse. (This is necessary to change the virtual adapter settings. If the Pulse tunnel is not connected, the virtual adapter does not appear in the Network Connections.)
- From the Network Connections select the Pulse Secure virtual adapter
- Right-click and select Properties
- Disable the Juniper Network Service by removing the checkmark from the service
Workaround 2: Disable RSC from the wireless adapter: (If Pulse is being used to connect to an SRX device then the Juniper Network Service needs to remain enabled. In this case, follow the steps below to disable RSC from the wireless adapter.)
- Open Powershell
- Run the following command to determine which adapter RSC is enabled on:
If RSC is enabled on the Wi-Fi adapter, for example, the following output will be seen:
- Run the following command to disable RSC on the Wi-Fi 2 adapter:
Disable-NetAdapterRsc -Name "Wi-Fi 2
Then run the following command again to verify that RSC is disabled:
The output will change as shown below:
- To disable RSC on all physical adapters, run the following command:
Get-NetAdapter | Disable-NetAdapterBinding -DisplayName "Juniper Network Service