- Products
- Learn
- Local User Groups
- Partners
- More
AI Security Masters E7:
How CPR Broke ChatGPT's Isolation and What It Means for You
Blueprint Architecture for Securing
The AI Factory & AI Data Center
Call For Papers
Your Expertise. Our Stage
Good, Better, Best:
Prioritizing Defenses Against Credential Abuse
Ink Dragon: A Major Nation-State Campaign
Watch HereCheckMates Go:
CheckMates Fest
Hi Checkmates,
As this is a new feature in E88.60.0087 (EPS-57370 in sk182468), I would like to check if anyone has experienced this.
SK182468: https://support.checkpoint.com/results/sk/sk182468
In current environment, we are utilising endpoint superNode & superNode Client so that the "semi-isolated" superNode Client that has no internet access is able to use superNode, as a proxy to connect Endpoint Cloud Server.
Everything is working good (deployment, update, logs) except the following errors at the assets:
- Threat Emulation Status showing error "Connection Error"
- Threat Emulation Reputation Status showing error "Service is not available"
- Attached the screenshot as reference
As I am able to replicate this at my lab environment, so I do not think it is caused by connections drop.
We have involved CP R&D into this but so far there is no breakthrough on the issue.
If anyone has tried this feature, I really appreciate if you can advise on this.
Thank you.
As a solution for this post, my issue is resolved by using E88.61.1058 package from R&D.
I believe version higher than it also contain the patches.
Can you send me the SR in a PM?
hi ,
Could test connectivity using C:\Program Files (x86)\CheckPoint\Endpoint Security\Endpoint Common\bin\CheckConnectivity.exe
hi PJ_wong
I could use the push operation to repair this customer
Hi lluner,
Unfortunately, "repair client" is not fixing it.
Attached the screenshots for client UI and test connectivity.
Aside from that, TAC has asked to turn on the proxy settings, which I think sometimes "silenced" the error for a while before it came back. This is not consistent and I am still trying to figure out the behaviour.
Thank you.
The TAC case you PMed me seemed to suggest something with TLS versions used might be an issue.
Hello PJ_WONG,
I have the same issue, do you have an update from checkpoint to resolve it please ?
Thank you
Sebastien
Hi Sebastien,
So far the issue is not resolved and we might have to wait for version E88.70 to fix it.
Best Regards,
PJ
Hi PJ_WONG,
Thanks for your feedback, I opened a case but as you advised I think I will have to wait for the next version.
Have a nice day,
Best Regards,
Sebastien
As a solution for this post, my issue is resolved by using E88.61.1058 package from R&D.
I believe version higher than it also contain the patches.
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 4 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
Tue 28 Apr 2026 @ 06:00 PM (IDT)
Under the Hood: Securing your GenAI-enabled Web Applications with Check Point WAFThu 30 Apr 2026 @ 03:00 PM (PDT)
Hillsboro, OR: Securing The AI Transformation and Exposure ManagementTue 28 Apr 2026 @ 06:00 PM (IDT)
Under the Hood: Securing your GenAI-enabled Web Applications with Check Point WAFTue 12 May 2026 @ 10:00 AM (CEST)
The Cloud Architects Series: Check Point Cloud Firewall delivered as a serviceThu 30 Apr 2026 @ 03:00 PM (PDT)
Hillsboro, OR: Securing The AI Transformation and Exposure ManagementAbout CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY