Hi, Testing with different SecureClient versions leads me to the sad conclusion that the Auto Local Logon feature in the 2k/XP version of the R55 (541000082) client is broken. It seems to work as long as SDL is not enabled. When SDL is enabled it works, until Logoff in windows, and logon again using SDL, then you are prompted for the SC password again. As long as you never logoff but reboot, everything is fine.... Or when authentication fails for some reason (i.e. no connection to the FW), then also Auto Local Logon breaks.... Once The local logon is broken, re-enabling it requires to disable SDL, disable Auto Local Logon, then re-configuring it and enabling it. And after the reboot re-enabling SDL... When broken the user credentials remain in the registry so all the user data is still there, they just don't get used.....
Has anybody else observed this behavior? Is there a fix or is this a genuine bug! Dion-ben Hendriks ----------------------------------------------------------------------- Dion-ben Hendriks, Netwerkspecialist, Staf Info - ICT in balans UMC St Radboud / UMC Nijmegen 215 Staf INFO Postbus 9101, 6500 HB Nijmegen, The Netherlands Tel:(+31)/(0) 24 36 19330 ================================================= To set vacation, Out-Of-Office, or away messages, send an email to [EMAIL PROTECTED] in the BODY of the email add: set fw-1-mailinglist nomail ================================================= To unsubscribe from this mailing list, please see the instructions at http://www.checkpoint.com/services/mailing.html ================================================= If you have any questions on how to change your subscription options, email [EMAIL PROTECTED] =================================================
