- Products
- Learn
- Local User Groups
- Partners
- More
What’s New in Identity and Trust?
AI Security Masters
Security in the Pace of AI:
From Threat to Force Multiplier
CPX is Back!
Join us in Las Vegas, Vienna, and/or Bangkok!
Check Point Named a Leader
The Forrester Wave:
Enterprise Firewall Solutions, Q4 2026
What’s New in Agentic Network Orchestration
CheckMates Go:
Fun Ding
I'm currently working on getting the AD authentication working on our MDS and I have been able to setup the AD LDAP account unit in our Global domain.
However the connection is not working the way it should, when I try to change anything in the account unit, I can Publish the changes but in the end I know it does not take any effect. There was a mentioning that the Install Database was automatic when you close the SmartConsole to the Global domain, however this also does not seem to work.
Example of a change was to change the access to the AD servers from plain LDAP (389) to LDAPS (636). Using tcpdump to see what was sent to the AD server revealed in before and after traces that 389 was used all the time. Not even an attempt to use 636 instead.
Anybody any Ideas?
hello Zib
is this limitation still valid? i'm tying to do same thing, but i got:
An error was detected while trying to authenticate against the AD server.
It may be a problem of bad configuration or connectivity.
Please refer to the troubleshooting guide for more help
same LDAP AU configured locally, instead, it works
I'm afraid I have left my last employer and have no ability to confirm 100% but I doubt that you can connect from Global Domain. You should wait till Q3 when big news are coming regarding IA. @Royi_Priov are there any public materials available already now about those? I don't want to steal the thunder 🙂
thanks or your reply!
my question of course is, what is useful global LDAP AU for? it seems they cannot work properly..
anyway, from logs, i can see that FW queries by LDAP the AD inside the Global LDAP AU, but no answer....
Discussion here is about using Global Domain within CP Multi Domain Management environment. Seems like you are mixing it up with AD AU?
If you are using MDM to manage large single organisation, than ability to use Global Domain would remove the need to connect every single management domain (aka CMA) to AD separately.
ok sorry for the wrong thread
anyway the goal here is to use Global LDAP AU from FW to perform the ldap queries to AD, and this is what is not working here
TAC Case just opened
ty
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 28 | |
| 8 | |
| 5 | |
| 5 | |
| 4 | |
| 4 | |
| 4 | |
| 4 | |
| 3 | |
| 3 |
Tue 17 Nov 2026 @ 08:30 AM (EST)
Bogota Breakfast & Hack: IA bajo control y ataques en vivo con Workspace SecurityTue 17 Nov 2026 @ 05:00 PM (CET)
AI Security Masters: Security in the Pace of AI: From Threat to Force MultiplierTue 17 Nov 2026 @ 11:00 AM (EST)
Under the Hood: Check Point SASE | Troubleshooting Like a ProTue 24 Nov 2026 @ 01:30 PM (GMT)
La nueva realidad de los ataques DDoS: autonomía, escala y el futuro de la defensaTue 17 Nov 2026 @ 05:00 PM (CET)
AI Security Masters: Security in the Pace of AI: From Threat to Force MultiplierTue 17 Nov 2026 @ 11:00 AM (EST)
Under the Hood: Check Point SASE | Troubleshooting Like a ProTue 24 Nov 2026 @ 01:30 PM (GMT)
La nueva realidad de los ataques DDoS: autonomía, escala y el futuro de la defensaWed 02 Dec 2026 @ 03:30 PM (GMT)
The New DDoS Reality: Autonomy, Scale, and the Future of DefenseTue 17 Nov 2026 @ 08:30 AM (EST)
Bogota Breakfast & Hack: IA bajo control y ataques en vivo con Workspace SecurityAbout CheckMates
Learn Check Point
Advanced Learning
WE SECURE YOUR AI TRANSFORMATION