![]() The logs also don't seem to pickup the source of the IPs, maybe there's another log that tells me what's going on? Maybe in Expert mode? I even changed the VPN DHCP source from the Checkpoint box to my Windows DHCP server to see if it made a difference, it doesn't. I've already looked at the regular scope in the Expert settings and found exactly what I already have on the Gaia webpage. I've tried looking through the SKs? And KB articles on Checkpoint website and nothing gives me an indication where another hidden dhcp scope might be. They can still connect internally but only via IP. ![]() Somehow, some of my endpoints when they connect to the VPN get a 192.168.20.0/30 subnet with none of my DNS settings, I don't have nor see any DHCP scopes for 192.168.20.0 in any of the Gaia or GUI interfaces. I've gone through many hoops to get it all setup and figured it mostly out, realizing many of the Nuances and pain points of Checkpoint in comparison.Īnyways, I've been stumped with this problem where some VPN clients are not getting the default IP Pool range of 172.16.10.x/24, its all setup with correct DNS and DNS Domain settings as per the configs using SmartDashboard / Gaia Web Console. I have lots of experience with Fortinet but very little with Checkpoint. I'm at the end of my straw here with a new Checkpoint device I've been carded to setup for a client, switching from a Fortinet (Not my decision).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |