- Products
- Learn
- Local User Groups
- Partners
- More
What’s New in Device Diagnostics?
Dec 2nd @ 5pm CET / 11am EST
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
Hello again.
Continuation of a previous post but the old post is marked as resolved (because it was) to allow contributor to receive credit. 😊
In a nutshell - we need to limit access to a network host to a small group of 5 individuals. The solution has to work with NAT (Identity Awareness is out as it doesn't work with NAT). This solution will be used for WFH users - the current OM IP pool is Nat'd to the internal interface of the Check Point.
My solution:
I'd like to configure the ipassignment.conf file to assign a range of IPs to my already existing AD group - then limit access to the resource based on the static IPs. (This will be used for WFH users).
What I've done:
Here is how my ipassignment.conf file will look referencing SK: sk33422
#Gateway Type IP Address User Name
==================================================
IP of gateway range 10.0.0.0-10.0.0.5 Test Group (AD group)
Questions:
Thank you, and as always - any help is always much appreciated!
Best Regards,
Joe
Even if you could get past the UI validation in SmartConsole, I suspect that space will be problematic in ipassignment.conf as well.
Change the name to something without a space.
Otherwise, this should work.
Even if you could get past the UI validation in SmartConsole, I suspect that space will be problematic in ipassignment.conf as well.
Change the name to something without a space.
Otherwise, this should work.
Ok cool. Thank you!
Please refer to https://support.checkpoint.com/results/sk/sk33422 for what exactly to use based on how the user authenticates.
Hello PhoneBoy,
see the screenshot of the line added at the end of the file.
user log to the vpn through LDAP with the AD account , his name is on capital letter from active directory but when he wants to connecte on the VPN client, he use small letter like i wrote on the file and it works but still taking the ip from the pool instead of the ipassignment file
Also after checking with vpn ipafile_check $FWDIR/conf/ipassignment.con detail , i get the output on the second screenshot
It's user/password authentication, right?
What if you put it in as it is in AD (i.e. with a Capital)?
If this doesn't work, suggest involving TAC.
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 30 | |
| 8 | |
| 7 | |
| 5 | |
| 5 | |
| 4 | |
| 4 | |
| 4 | |
| 3 | |
| 3 |
Tue 24 Nov 2026 @ 01:30 PM (GMT)
La nueva realidad de los ataques DDoS: autonomía, escala y el futuro de la defensaThu 26 Nov 2026 @ 10:00 AM (CET)
The Cloud Architects Series: Cloud Security State in 2026 – Lessons Learned and a Look AheadWed 02 Dec 2026 @ 03:30 PM (GMT)
The New DDoS Reality: Autonomy, Scale, and the Future of DefenseThu 03 Dec 2026 @ 11:00 AM (EST)
Under the Hood: Check Point Cloud Firewall for Nutanix - How to Secure your AI WorkloadsTue 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 DefenseThu 03 Dec 2026 @ 11:00 AM (EST)
Under the Hood: Check Point Cloud Firewall for Nutanix - How to Secure your AI WorkloadsAbout CheckMates
Learn Check Point
Advanced Learning
WE SECURE YOUR AI TRANSFORMATION