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
How to configure a working SSL Certificate for Checkpoint VPN 72Number of Views Explanation of product filtering in Lea client connections and its usage to filter checkpoint logs 67Number of Views GoToMeeting - RSA Ready Implementation Guide 42Number of Views Specops Software uReset - SecurID Authentication API with CAS Configuration - RSA Ready SecurID Access Implementation Guide 22Number of Views RSA SecurID Authentication Engine 2.8.2 for Java Release Notes 4Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Reporting on RSA Authentication Manager 8.x users with On-Demand Token, a fixed passcode or a hardware/software token assi… How to Download OTP Token Seed Files from myRSA Anomalix idGenius - SAML Relying Party Configuration - RSA Ready Implementation Guide RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide