- Products
- Learn
- Local User Groups
- Partners
- More
What’s New in Identity and Trust?
11 November @ 5pm CET / 11am EST
CPX is Back!
Join us in Las Vegas, Vienna, and/or Bangkok!
What’s New in Agentic Network Orchestration
AI Security Masters
LGTM: Bypassing an LLM Build Gate
When Prompt Injection Fails
CheckMates Go:
Fun Ding
Hi Everyone,
im currently encountering an issue with several drops of different sevices being rejected with the message Not allowed SSL version.
I checked the DB settings: ssl_min_ver is set to sslv3 while max is set to tls1.2 .
I also created a seperate rule for ssl inspect like described in sk34182., yet i still receive the error.
Currently it blocks me from initiating a rdp session within an existing Site 2 Site VPN Connection.
Remote_Desktop_Protocol (TCP/3389)
Reject
Not allowed SSL version
So far i was not able to find any other sk article regarding this issue,
Has anyone else encountered this problem?
Hi everyone,
it turned out that someone configured multiple Services with active protocol signature(TCP,UDP,) under R77.80.
But instead of matching them to the recommended port (e.g. 443 TCP) they were matched for any port. This led to the error that any tcp / UDP traffic which was encypted matched for those services (which were missing in the security and application policy rules). The issue became visible after the update fron 77.30 to 80.20 .
As a solution, i deleted both services.
Thx for all the help
Please check your RDP SSL Inspection is properly set. Look here: https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solut...
If that does not help, you can try HTTPSi bypass rule for RDP specifically
Hi Valeri,
i tried the explicit https bypass rule for RDP, unfortunately the behavior is still the same.
I also tried your link, but i get the message: Solution could not be found in the system.
Yet i found a TCP service which could be a remnant from R77.30
Protocol: SSL_V3
Match By Port: Any
Protocol Signature: checked
Could it be that the service is mismatched since it fulfills the criteria for this object?
Yes, you might need to set up a _new_ RDP service. One inherited from R77.30 is no good
The action is bypass, so it is not the policy. Which HFA are you running at? With R80.30 you need at least Jumbo 50
@PhoneBoy I am afraid you are mistaken, please check the SK I have referenced above
Hi,
i just checked the version of the cluster.
Sorry, it seems i was mistake. R80.30 is the Console.
Currently installed:
HOTFIX_R80_20_JUMBO_HF_MAIN Take: 87
Hi everyone,
it turned out that someone configured multiple Services with active protocol signature(TCP,UDP,) under R77.80.
But instead of matching them to the recommended port (e.g. 443 TCP) they were matched for any port. This led to the error that any tcp / UDP traffic which was encypted matched for those services (which were missing in the security and application policy rules). The issue became visible after the update fron 77.30 to 80.20 .
As a solution, i deleted both services.
Thx for all the help
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 34 | |
| 22 | |
| 13 | |
| 8 | |
| 7 | |
| 4 | |
| 4 | |
| 3 | |
| 3 | |
| 3 |
Tue 03 Nov 2026 @ 06:00 PM (CET)
Under the Hood: How to Secure Agentic AI on AWS with Check PointTue 10 Nov 2026 @ 06:00 PM (IST)
Under the Hood: Introducing Check Point Cloud Firewall as a ServiceTue 10 Nov 2026 @ 08:00 PM (IST)
Check Point Mobile Security | Extending Zero Trust with NetskopeTue 03 Nov 2026 @ 06:00 PM (CET)
Under the Hood: How to Secure Agentic AI on AWS with Check PointTue 10 Nov 2026 @ 06:00 PM (IST)
Under the Hood: Introducing Check Point Cloud Firewall as a ServiceTue 10 Nov 2026 @ 08:00 PM (IST)
Check Point Mobile Security | Extending Zero Trust with NetskopeAbout CheckMates
Learn Check Point
Advanced Learning
WE SECURE YOUR AI TRANSFORMATION