Secuirty - workstation locks itself

I have a XP machine SP2 in a Domain. When no user is logged in the box, XP
will (after about 15 minutes) locks the workstation by itself. Strange even
more, it uses the local admin account. That is, when you hit the C-A-D keys
to unlock the thing the username is blank and the computer listed is the
local account. No one uses the local admin account. There is no group policy
to do this. There are no screen savers in the gpo or the local gpo (which
wouldn't count anyways because its in a domain).

Also when I try to unlock it using the local and domain admin accounts it
won't let me. But I can use a blank username and the correct admin password
and the system gets unlocked after a few moments then re-boots.

This only happens when no user is logged into the box. If a user is logged in
everything runs as normal as far as the screen savers and locking work
stations goes.

Occassionaly there are winlogon.exe errors that will pop up in the app error
window (the one telling you the app has to close and do you want to send the
error to MS) the error is in the winlogon.exe. System runs fine if you ignore
the message and hit don't send and close the window. There are no errors in
the event logs at all.

I reinstalled SP2 but still have the problem. No viruses. Scanned daily using
up to date NAV files.
Any help here would be greatly appreciated.
Many Thanks in advance.
.

Relevant Pages

  • Re: same domain names co-exist in WAN
    ... > This next script renames the account as well as resets the password. ... > 'Rename Local Admin Account ...
    (microsoft.public.windows.server.active_directory)
  • Re: Best Practice for Domain & Local Admins
    ... I do have a separate local admin account on my workstations than the domain admin account. ... I personally have found there is more risk from workstations running with local admin rights and folks being able to download malware. ... Since many of the password-hacking systems out there require that the id be stored in a hash file locally, if the domain admin account is not used on the client machine, it's not able to be hashed. ...
    (microsoft.public.windows.server.sbs)
  • Best Practice for Domain & Local Admins
    ... Considering that there are password-breaking utilities out there, would it be a best practice to have two separate admin accounts for our SBS deployments? ... One would be the system admin account which would be used solely on the physically secured server, and the other would be a local admin account that is just a regular domain user, but is set as an administrator on all local machines. ... Since many of the password-hacking systems out there require that the id be stored in a hash file locally, if the domain admin account is not used on the client machine, it's not able to be hashed. ...
    (microsoft.public.windows.server.sbs)
  • Re: Grant Object Access
    ... application that doesn't use a local admin account but can still use my COM ... > Denied message from COM when trying to add a task to the Scheduled Tasks. ... > worked again without having to give admin rights to IUSR_. ... I'd like to not use an admin account for the COM+ ...
    (microsoft.public.windows.server.security)
  • XP local users getting locked out.
    ... I have a computer that is not a part of a domain but is in a workgroup. ... Every so often all users except the local admin account will get locked out ... and I have to login with the local admin account to unlock. ...
    (microsoft.public.windowsxp.configuration_manage)
Loading