Using Suspend Operation while authenticating with SecuRemote

[BarryStiefel]

Using Suspend Operation while authenticating with SecuRemote

I have this rule in my Checkpoint NG FP3 Any => 2.3.4.5 => 8080 accept log Users@Any =>1.2.3.4=>ALL Accept log



When a remote user dials the internet and try to access 2.3.4.5 he get the Secure Remote Prompt. If I press the Suspend button At the client Secure remote I am not able to connect to 2.3.4.5 any more. If I stop the secure remote I am able to connect to 2.3.4.5 Any ideas?

From What I see When Secure Remote is on Suspend. There is No Connection to my FW at All. and I don’t see Packets Drop on my fw log.



Answer It's probably an issue of the SecuRemote drivers getting wedged on suspend. You can either not hit the "suspend" button when being prompted for SecuRemote authentication (seems pretty easy to me) or try a newer SecuRemote to see if it helps (yes, you can use newer SecuRemote with older firewalls).



Comments

I've had users do this on occasion.



Try opening the client from the task bar (into 'configure' mode) and updating the suspended site, I've found this usually kick-starts the authentication again.

HTH

Brett My experience is that it's possible to use a site update to heal various anomolies regarding authentication with SecuRemote.



-RobertGraham -- RobertGraham - 02 Feb 2004

FAQForm FAQs.Class: SecureClientFAQs, TroubleshootingFAQs FAQs.OS: FAQs.Version: