Pulse Secure Client 5.3.7 is already end of life.  https://support.pulsesecure.net/product-service-policies/eol/software/pulse-client-software-dates-milestones/   Please uninstall and install one of the latest version. The current version of Pulse client available is 9.1R11 ... View more

Pulse Secure Client 5.3.7 is already end of life.  https://support.pulsesecure.net/product-service-policies/eol/software/pulse-client-software-dates-milestones/ Please uninstall and install one of the latest version. The current version of Pulse client available is 9.1R11 ... View more

It could be due a third party conflict  KB40887 - How to isolate or fix third party conflict issue with Pulse Secure Desktop client ... View more

Please uncheck Juniper network service from both the WiFi and Pulse Secure Adapters. KB43833 - Slow download speeds/unable to access resources over Wifi via Pulse Desktop client on Windows 10 Redstone 3 and up   If the issue persists, it could be due to a 3rd party application. We would need to review the logs. We suggest you to open a support case with us.      ... View more

This looks a known issue which is still under investigation with our Dev team. I suggest you to open a support ticket with us to get ETA. ... View more

Please check if you're firewall is dropping this traffic.   ... View more

Please check if this helps, here's what we have to do in the registry. Set the NoActiveProbe DWORD value to 0. Remove the following from HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NlaSvc\Parameters\Internet: * ActiveDnsProbeContent * ActiveDnsProbeContentV6 * ActiveDnsProbeHost * ActiveDnsProbeHostV6 By deleting the above DWORDs, we essentially eliminated the NLA's DNS query check and only rely on its TCP connection checks to validate network connectivity.     ... View more

I think you are trying to create a PSAM / Layer 4 connection PSAM is a windows feature where it will use WFP/TDI drivers, especially for windows, it will not work in the Linux platform. For Linux, we recommend using PDC with a JSAM / L3 tunnel to access internal resources. ... View more

You must have configured Prelogon (credential provider) or certificate authentication (domain joined laptop) so you're not prompted for credentials when login into the endpoint for AD and not for Azure.     ... View more

There is no option to SNMP Poll/Traps for license allocation or expiring licenses on PCS appliance. I recommend you to file an Enhancement Request through your Pulse assigned SE. ... View more

Unfortunately, there is no options to trigger "Forget saved settings" from command prompt. You can reach out to your Pulse assigned SE to file an Enhancement Request to include this options in the future releases.     ... View more

We would need to investigate this issue. So I recommend you to open a support ticket with us. ... View more

5.3.5 (1491) is already EOL. Please upgrade the Pulse client to one of the latest version. The current version is 9.1R11  All Pulse client versions are forward and backward compatible.   https://support.pulsesecure.net/product-service-policies/eol/software/pulse-client-software-dates-milestones/ ... View more

Please test the behavior after upgrading the pulse client to 9.1R11 and ESAP to 3.7.4. If the issue persists, please open a support case with Pulse. ... View more

Please test the behavior after upgrading the pulse client to 9.1R11 and ESAP to 3.7.4. If the issue persists, please open a support case with Pulse. ... View more

The concurrent SSL connections graphs shows the client side connections such as VPN Tunneling (Network Connect or Pulse Secure Desktop client), WSAM, JSAM.   Even if you select ESP mode, it would be counted as SSL as connection is SSL and only the data channel uses ESP. KB16841 - Differences between Concurrent Users and Concurrent SSL Connections graphs ... View more

Please try with one of the latest version. You will have uninstall Network Connect (Pulse Client v5.2.7) and install the latest version. If the issue persists, please collect Pulse Client debug logs and open a support case with Pulse Secure.   Client side debug logs: 1.Open the Pulse client. 2.File > Logs > Annotate > Disconnection 3.File > Logs > Log Level > Detail. 4.Connect to the VPN  5.As soon as you get disconnected, save the logs 6.File > Logs > Save As ... View more

Please try the upgrade from the PCS appliance KB44670 - Pulse Secure Client upgrade from PCS/PPS irrespective of the end user's OS/platform ... View more

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

This is working as designed.  FQDN split tunneling will need to modify the DNS setting on both physical and virtual adapters. Therefore, DNS entries from both the virtual and physical interfaces get registered.   Possible workarounds: Use IP-based split tunneling Manual de-register the DNS entries on the endpoints Please follow the instructions given below to de-register the DNS entries. Open Control Panel. Click on Network and Internet. Click on Network and Sharing Center. Click the Change adapter settings option in the left pane. Right-click the network interface of the adapter that you don't want the DNS to be register and select the Properties option. Select and check the Internet Protocol Version 4 (TCP/IPv4) option. Click the Properties button. Click the Advanced button. Click the DNS tab. Uncheck “Register this connection’s addresses in DNS” for the interfaces Repeat the same steps for the other adapters that you don't want the DNS to be register I understand this is going to be a challenge as there might be lot of users. Please check with your network team if this case be pushed via Group policy or Script. There is already an Enhancement Request. Please reach out to your account manager. ... View more