- Products
- Learn
- Local User Groups
- Partners
- More
Access Control and Threat Prevention Best Practices
5 November @ 5pm CET / 11am ET
Ask Check Point Threat Intelligence Anything!
October 28th, 9am ET / 3pm CET
Check Point Named Leader
2025 Gartner® Magic Quadrant™ for Hybrid Mesh Firewall
HTTPS Inspection
Help us to understand your needs better
CheckMates Go:
Spark Management Portal and More!
Hi Rock,
We performed the sk132712 and this didnt resolve our issue. After policy installation the gateway stopped listening on port 18231, but after making VPN connection the icon for Compliance on Endpoint VPN Client changed to grey(Greyed out) and status to Off. So this solution will not work of our environment. Hence we ended up opening TAC. TAC provided us the below solution.
Follow the steps - (Make this changes on Gateway)
*#*0 dtps dtpsd respawn 0
*#*0 dtls dtlsd respawn 0
Then perform cprestart on the GW. Do a cpstop; cpstart in a maintenance window.
3. After this, the policy server should be shown down.
4. After that, we need to apply the hotfix(Contact TAC). The hotfix will assist to make the configuration changes permanent.
5. Check the status of port 18231 -
# netstat -tulnp |grep 18231
# netstat –atun |grep 18231
Note: Checkpoint has created PRHF-32277 for this issue and they don't have any plans to integrate this issue in next JHF anytime soon. So for every upgrade, we need to reach TAC for hot-patch.
About CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY