Re: Checkpoint Securemote

[Christopher Lee <complexity () bigfoot com>]

I'm surprised (or maybe I shouldn't) that Checkpoint could not answer this 
question...  :-)

Anyhow, the simpliest solution is to implement "Connect Mode" feature of the 
VPN client in conjunction with SDL.  This way, instead of being triggered by 
the netlogon service, the VPN software daemon will be triggered manually by the 
user.  I've gotten this to work, even within a verion 4.1 environment.

While you at it, try the "Office Mode" feature as well, but please make sure 
you are doing "office mode" on FP2 or later releases...

This is just the high level overview, but a quick peek into the manual should 
give you the easy how-to.

Regards,

Christopher Lee 
PGP Fingerprint: 15C1 65D0 E051 C64D 5246  89FC 5AE3 DE2C 8F1E 89A7 
Personal Web Page: http://complexity.webhop.net


Quoting Steve Evans <sevans () foundation sdsu edu>:

> We have a problem with the Checkpoint VPN client.  The VPN doesn't kick
> in until after the logon process, which makes it difficult in some
> situations to log on to a Windows 2000 domain over the VPN.  Does anyone
> have a fix for that?  We've worked with Checkpoint on it without any
> progress.  We're using the NG version now but we had the same problem on
> version 4.x
>
> Steve Evans
> SDSU Foundation
> (619) 594-0653
> _______________________________________________
> firewall-wizards mailing list
> firewall-wizards () honor icsalabs com
> http://honor.icsalabs.com/mailman/listinfo/firewall-wizards


_______________________________________________
firewall-wizards mailing list
firewall-wizards () honor icsalabs com
http://honor.icsalabs.com/mailman/listinfo/firewall-wizards