LEA Client is running
There are various things that could cause issues with collecting from Check Point:
Make sure the Check Point Log Viewer is receiving events.
Check Ports are available on both sides:
FW1 (256): Non-authenticated connections
FW_lea (18184): Non-authenticated / authenticated connections
FW_ica_Pull (18210): Sending the Cert file to the appliance
LEA Client Service, check that this has been setup correctly.
If the LEA Client configuration looks good you can enable debugging by going into the enVision Web UI to the Manage Lea Service screen. Select the advanced option triangle and check off the debug option. This will restart the lea service and begin generating 2 debugging file out under the logs folder. LeaConnectionName_opsec_output.log, LeaConnectionName_checkview.log. These 2 files combined will give you a better idea of what is happening during the connection. If using non-auth you would need to modify the port and auth port settings in the fwopsec.conf file for that to work
Related Articles
Explanation of product filtering in Lea client connections and its usage to filter checkpoint logs 64Number of Views Integrate Citrix NetScaler with RSA Authentication Manager 8.x 178Number of Views How to integrate SWIFT Alliance Access with RSA Authentication Manager using RADIUS protocol 104Number of Views Generating a Report on a Windows platform hosting Web Tier software 270Number of Views How to export Web Tier Virtual Host Key Pair to a PFX file for RSA Authentication Manager 8.x 1.01KNumber of Views
Trending Articles
RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA Release Notes for RSA Authentication Manager 8.8 Troubleshooting RSA MFA Agent for Microsoft Windows How to download and install the AFX Server Archive in RSA Identity Governance & Lifecycle The Template ({Connector Template Name}) has missing file content error when creating AFX Connectors in RSA Identity Gover…