Guest User!

You are not Sophos Staff.

This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Safeguard 5.4 0 Logon Delays

We are experiencing logon delays of up to 30 seconds (including when a machine is locked / unlocked). This is not occurring on all of our machines, but on some which is causing our users inconvenience. Our environment is as follows:

OS - WinXP SP2
SafeGuard Enterprise client 5.40.0.152
SafeGuard Port Protector client 5.40
SafeGuard Client Configuration 5.40

We have tried changing the logon gina back to msgina.dll but this doesn’’’’t seem to work (keeps defaulting back to sggina.dll). Note: The PC’’’’s affected do NOT have any other software such as Checkpoint software which would interfere with the login process.

The machines do boot fine, there is unfortunately the delay is very noticeable delay at the login screen.

We thought that by changing the gina it may resolve this issue.

Note that we do not have Disk Encryption, only Data Exchange and Configuration Protection.

Cheers

Matt

:1427


This thread was automatically locked due to age.
Parents
  • You're welcome Planet_Uranus,

    I wish I could provide you with a silver bullet but logon delays are tricky to diagnose over a forum such as this. Since you are only experiencing the delay on a small number of devices, it is clear that the delay is related to those systems. Quickly off the top of my head here are some things to look at:

    1. Are the policies the same for the computers experience the delay compared to the one that are not? Don't dismiss a small difference.

    2. Are they based on the same image or are their differences related to additonal services starting?

    3. DNS baked into the image. (see below)

    4. The list goes on.

    I worked with a customer a couple years ago that experienced logon delays over 6 minutes on some computers and not others. After going through the stop watch tests, then digging through the Windows Event logs, we found an error which was always around system startup. I forgot the error code (this was a long while ago) but it was related to a DNS failure pointing to a decommissioned Domain Controller! The old DC was baked into the image, taken offline, but the clients weren't updated. The net result was that the clients had to wait for DNS to timeout before trying another DC. They updated the registry with a the correct DC and the logon delay was resolved.

    If none of these items help you out, please contact Sophos Technical Support so they can boil the issue down to the root cause.

    :1495
Reply
  • You're welcome Planet_Uranus,

    I wish I could provide you with a silver bullet but logon delays are tricky to diagnose over a forum such as this. Since you are only experiencing the delay on a small number of devices, it is clear that the delay is related to those systems. Quickly off the top of my head here are some things to look at:

    1. Are the policies the same for the computers experience the delay compared to the one that are not? Don't dismiss a small difference.

    2. Are they based on the same image or are their differences related to additonal services starting?

    3. DNS baked into the image. (see below)

    4. The list goes on.

    I worked with a customer a couple years ago that experienced logon delays over 6 minutes on some computers and not others. After going through the stop watch tests, then digging through the Windows Event logs, we found an error which was always around system startup. I forgot the error code (this was a long while ago) but it was related to a DNS failure pointing to a decommissioned Domain Controller! The old DC was baked into the image, taken offline, but the clients weren't updated. The net result was that the clients had to wait for DNS to timeout before trying another DC. They updated the registry with a the correct DC and the logon delay was resolved.

    If none of these items help you out, please contact Sophos Technical Support so they can boil the issue down to the root cause.

    :1495
Children
No Data