Link to home
Start Free TrialLog in
Avatar of kwatt562
kwatt562Flag for United Kingdom of Great Britain and Northern Ireland

asked on

Password Problem after Hibernation

Strange one, on one of our laptops (on a domain), logon attempts after hibernation are not succesfull (password not accepted). The user always has to reboot the machine. We are running XP Pro SP3 on all our machines. Has anyone seen this problem before?
Avatar of moon_blue69
moon_blue69

Hi

Can you check the event logs please to see if you find anything there?
Just to make sure that user is typing the password correctly you could ask the user to type the password in the username field that way we could also know if by mistake user has enabled the Numpad (Numeric Key pad) which are activated/de-activated using Fn (Function Key or Shift key).

Sudeep
Avatar of kwatt562

ASKER

Hi
I checked and there is nothing in the event logs

I had a similiar thought about the num lock particulary since we use complex passwords, but everything seems fine.
Hi

you could try the following things.

1. turn off fast user switching from control panel user accounts.
2. You can try restoring your system to an earlier date when it was working
Thanks for your comments

1. Not an option as we are on a domain, user switching is off already
2. Doesnt help in this case as its a new PC with a fresh image (and he image is fine on the other PC's)
You may want to check the server event log as well.

Also there are some know issues with laptops and windows hibernate and sleep functions.
You should check that all windows updates are installed and that the lates drivers for you network device (whether LAN or WiFi) is installed, as there are some cases where computers lose network access after sleep/hibernation requiring a restart. Hope this helps.
I will check the logs
I add a similiar thought about the network LAN losing connection, but wouldnt the cached credentials work in this case?
The only thing that comes to mind here is that possibly your number of cached interactive logons is set to 0, meaning that each time you log on your PC has to actually contact the DC for authentication rather than caching the credentials for comparison. And, since the laptop is coming out of hibernation the NIC might not be fully ready to talk to the network, especially if it is connected via wireless.  

If that's not it and I am totally in the wrong direction, you might try turning hibernation off then back on.

Kenny
Is it worth using the user hive cleanup tool.....I have never used it before
That was my thought as well, but as coalnine suggestion indicates, cached credential settings can vary depending on settings, what seems to be happening is that after hibernation there NIC either isn't communicating connected with the network (either not ready or no connection) or it is attempting to continue work from the point when it was hibernated, depending of the domain settings it's failure to repsond during that time would have resorted in it's connection being terminated, and hence it would have to be reauthenticated, which it isn't attempting to do.

I can be way off here, but just my take on it thus far.
Thanks
If the the interactive logons is set to 0, and it it looks like the NIC connecting with the network is the issue, is there a config change to resolve this?. The laptop is pretty new Hp 8440p, with the latest drivers from the HP website, so an updated driver is probably out.
This may be of some assistance: http://support.microsoft.com/kb/907477/

Haven't touched XP in a while so trying to troubleshoot by memory. Would it safe
*would it be safe to assume you're connecting via wifi?
To make it simple, suggest you to test with a local account, if the same problem doesn't happen, you may test with another Domain User account, if the problem only occurs on that user account, you may delete that User Profile on the notebook and create a new one.

ASKER CERTIFIED SOLUTION
Avatar of johnb6767
johnb6767
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Hi John6767,  with regards your last comment, I had the same thought this morning so I disabled the sleep function on the LAN. Im waiting for the user to verify if it has resolved the problem.

cheers
Yeah disabling the sleep function on the NIC solved the problem, many thanks to all