Reset Search
 

 

Article

KB45277 - How To Configure Lock-Down Exception Rules for an Application.

« Go Back

Information

 
Last Modified Date6/28/2022 3:51 PM
Synopsis
This article provides information on configuring lockdown exceptions for always on VPN for the Netskope client to connect prior to a VPN connection.
Problem or Goal
It has been requested to enable lockdown and always-on VPN. When this is done, the Netskope client is no longer connecting properly prior to the session being established
Cause
Solution
Lockdown exceptions should be created for the Netskope applications (please check the path for your deployment; a sample path is C:\Program Files (x86)\Netskope\STAgent). This will require inbound and outbound rules.
In addition to the executables, it may be required to add the Netskope IP addresses for inbound and outbound rules as well.

User-added image

Lockdown exception rules should be configured in the following three ways under Resources for both “Inbound* and “Outbound* traffic separately.
These are created at Users>Pulse Secure Client>Connections>connectionName

User-added image

User-added image


Once the connection set is created, a configuration file can be saved for deployment at Users>Pulse Secure Client>Components



 
Related Links
https://kb.pulsesecure.net/articles/Pulse_Secure_Article/How-to-use-jamcommand-to-Import-connections-to-Pulse-Desktop-Client/?q=rma&l=en_US&fs=RelatedArticle
Attachment 1 
Created ByNawaid Haider

Feedback

 

Was this article helpful?


   

Feedback

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

Characters Remaining: 255