To resolve this issue, Pulse Secure recommends to upgrade to the following releases:
- Pulse Secure Desktop client 5.3R3 and above
- Pulse Connect Secure 8.3R3 and above
In the following release, lock down mode exception rules were added to allow specific traffic when lock down mode is enabled. In the Pulse connection set, lock down exceptions rules will need to be added for inbound and outbound connections for TCP 3115 and 65229.
Workaround:
If a software upgrade is not possible, the following steps can be taken to immediate resolve the issue:
- Pulse Connect Secure (PCS) administrator can disable lockdown mode from the Pulse Connection set and reboot the endpoint machine.
For Pulse Secure Desktop users, please contact your company help desk or Pulse Connect Secure (PCS) administrator to report this issue and provide the following KB article. The fix and workaround will require changes from the Pulse Connect Secure administrator.