Bizarre Logoff Problem 1

[djcrane]

Hi All

I'm having problems with one particular w2k machine on our network:

When people log off the machine (and they do this correctly and I can replicate it using my account)if someone is to try logging into the machine 10 minutes later then it appears that the machine is locked by the previous user (despite logging off correctly)

This may be a simple problem but (hopefully!). Has anyone seen this before and what causes it?!

Thanks

DJ

 

[bcastner]

I assume you checked for Screensaver issues.

A wild guess: is PcAnywhere installed?

 

[chriseubank]

is autologon enabled? .....

If it is, when you log off it will automatically log back on again fairly quickly LOL

C

 

[djcrane]

Hi

Thanks for your replies.

Its none of these though!!

Any ideas anywhere please?!!

DJ

 

[bcastner]

If all you are seeing is the need to Ctrl-Alt-Del to enter the logon screen, this is normal. You might check the Power Options settings for the workstation to see if a Suspend or Hibernate feature is enabled.

 

[bcastner]

If all you are seeing is the need to Ctrl-Alt-Del to enter the logon screen, this is normal.

 

[djcrane]

Hi

Thanks for the reply.

It is not the CTRL+ALT+DEL window to enter the login screen.

It is as if the previous user has locked the workstation. Ie only the user or administrator can unlock the workstation. However the user HAS logged off!

When trying the administrator account it does not unlock the workstation either which is most bizarre.

Being suspicious minded I thought it could be some sort of key logging thing that may have been installed (so have changed the admin password!) but I can't find anything.

 

[bcastner]

Using regedit, examine this key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon

The key GINA.DLL should be pointing at MSGINA.DLL.

 

[bcastner]

By the way, do not change it if it is a different value. Try to find the application that modified the MSGINA chain.

 

[chriseubank]

Logoff script enabled possibly?

see this page:

http://www.jsiinc.com/SUBM/tip6100/rh6128.htm

 

[NortonES2]

Check the following:-

http://support.microsoft.com/default.aspx?scid=kb;en-us;242917

-------------------------------

If it doesn't leak oil it must be empty!!

 

[NortonES2]

Registry entries referencing a screen saver that has since been deleted from the workstation?

http://support.microsoft.com/default.aspx?scid=kb;en-us;242917

-------------------------------

If it doesn't leak oil it must be empty!!

 

[NortonES2]

Registry entries referencing a screen saver that has since been deleted from the workstation?

http://support.microsoft.com/default.aspx?scid=kb;en-us;242917

-------------------------------

If it doesn't leak oil it must be empty!!

 

[NortonES2]

Check the following:-

http://support.microsoft.com/default.aspx?scid=kb;en-us;242917

-------------------------------

If it doesn't leak oil it must be empty!!

 

[NortonES2]

Sorry about the multiple posts, had major posting problems

-------------------------------

If it doesn't leak oil it must be empty!!

 

[djcrane]

Hi All

Thanks for all the suggestions. In the end it was the corrupt password protected screen saver thing that can be found on MS article 242917.

Thanks to NortonES2 for the pointer!

DJ