Reset Search
 

 

Article

KB43833 - Slow download speeds/unable to access resources over Wifi via Pulse Desktop client on Windows 10 Redstone 3 and up

« Go Back

Information

 
Last Modified Date1/20/2021 6:40 AM
Synopsis
This article describes an issue on Windows 10 where end user experiences slow download speeds/unable to access resources over Wi-Fi adapter via Pulse Desktop client on Windows 10
Problem or Goal
Possible symptoms:
  • PC is running Windows 10.
  • With Pulse client connected, end user may see resource access and slowness issues via VPN.
  • The issue is primarily seen in some cases on but not limited to Intel ® Wireless-AC 9560/9260 on particular hardware like DELL 5530 and HP Zbooks 15 (There is no exhaustive list).
  • With Pulse Desktop client installed, when connected over physical adapter (with or without Pulse VPN tunnel) user experiences slow network speeds.
  • User is unable to access any internal resource after launching Pulse tunnel when connected via Wifi. Only few pings will be successfully initially and then fails and Pulse client keeps trying to reconnect.
  • Even without Pulse Desktop client installed, slow download speeds is seen to be experienced as well : https://social.technet.microsoft.com/Forums/en-US/27dd19ab-78a2-42fc-accb-34bd949a30a7/windows-10-creators-update-causing-very-slow-wifi?forum=win10itpronetworkingr
  • When a speed test is performed the download speed is lower than the upload speed.
  • Ethernet or wired connection is not impacted.
  • If Windows system is using Hyper-V then download speed is also impacted on virtual machines configured with Hyper-V that are bridged to the host system via Wifi where the host system has Pulse Desktop client installed.
Cause
This issue is caused due to an interoperability with the Juniper Network Service which binds to physical adapters when Pulse Desktop Client is installed.

 


 
Solution
This issue is resolved in Pulse Desktop client 9.1R10 onward.

Note:
  • From PDC 9.1R10, “Juniper Network Service” will be disabled whenever a connection is established to Pulse Connect Secure.
  • And upon a connection Pulse Policy Secure (L3 Enforcement), the “Juniper Network Service” will be enabled.
  • This is purely a client-side fix (No Server Upgrade is needed).
The following alternate solutions have been implemented by our customers successfully, 

Solution # 1: Disable the Juniper Network Services from the physical and virtual adapter: 

(DO NOT apply Solution # 1, if one of the following is TRUE)

1. PDC is used to connect to an SRX device.
2. PDC is used to connect to PPS where SRX is acting as an L3 Enforcement Point (With IPSEC). 

Method :1 - Automated (Applicable to Pulse Desktop Client 9.1R5 or later & PCS 9.1R1 or later).

Install/Upgrade to Pulse Desktop Client 9.1R5 (Scheduled to be released by April, 2020) on end-points and following the steps below,
  • Login to the PCS Admin page (New UI Only).
  • Navigate to System -> Configuration -> Advanced Client Configuration.
  • Add the following content under “Enter advanced configuration in XML” and Save Changes,
<advanced-config>
 <version>9.1.5</version>
<desktop-client-config>
  <layer3-connection-config>  
   <adapter-config>
<disable-jnprns-driver>TRUE</disable-jnprns-driver>
   </adapter-config>
  </layer3-connection-config> 
 </desktop-client-config>
</advanced-config>
Note -
 
  • This method is applicable only to Windows 10 End Points & can be safely implemented even if only a subset of machines are affected (This implementation doesn't affect Windows 7/8 Machines in any way).
  • During the first Pulse Desktop Connection (9.1R5), the Windows End-Point will get the instructions from PCS to disable “Juniper Network Service” from all the adapters (Including Virtual Adapter) and the changes will remain as-is for any subsequent connections to PCS (Unless changed manually or setting the value to FALSE on the PCS Device).
  • Users may notice a few seconds delay compared to the normal behavior during their very first connection.
  • XML addition on PCS will not affect the Pulse clients below 9.1R5 in any way.
  • There is no other way of implementing this Method.

Method :2 - Manual
  1. Open Control Panel and select Network and Sharing Center the select Change adapter settings.
OR
From a DOS command prompt run the command: 
-Start > Run > ncpa.cpl
 
  1. Locate the physical adapter in the Network Connections
  2. Right-click on the adapter and select Properties.
  3. From the list, uncheck the checkbox for Juniper Network Service
User-added image
  1. Connect with Pulse Desktop Client. (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.)
  2. From the Network Connections, select Pulse Secure virtual adapter
User-added image'
  1. Right-click the adapter and select Properties
  2. From the list, uncheck the checkbox for Juniper Network Service & Click OK
User-added image

8. Alternatively, the same can be achieved upon running the following command from PowerShell (Running as an Admin)

 
Disable-NetAdapterBinding -Name * -DisplayName "Juniper Network Service"

Note : Replace * with specific Adapter display name if you do not wish to disable "Juniper Network Service" on all the adapters.

Solution # 2: Disable RSC from the physical adapter: 

(Apply Solution # 2, if one of the following is TRUE)

1. PDC is used to connect to an SRX device.
2. PDC is used to connect to PPS where SRX is acting as an L3 Enforcement Point (With IPSEC). 
  1. Open Powershell (Run as Administrator)
  2. Run the following command to determine which adapter RSC is enabled on:
Get-NetAdapterRsc

If RSC is enabled on the Wi-Fi adapter, for example, the following output will be seen:
User-added image
  1. Run the following command to disable RSC on the Wi-Fi 2 adapter:
Disable-NetAdapterRsc -Name "Wi-Fi 2"
Run the following command to verify that RSC is disabled:
Get-NetAdapterRSC
The output will change as shown below: 
 
User-added image

Note - The OperationalState of Blank or False indicates that RSC is Disabled.
  1. ​To disable RSC on all physical adapters, run the following command:  
Disable-NetAdapterRsc -name "*"                      
 
                Related Links
                Attachment 1 
                Created ByLokesh T K

                Feedback

                 

                Was this article helpful?


                   

                Feedback

                Please tell us how we can make this article more useful.

                Characters Remaining: 255