Discussion Locked

can't get past login screen at login

0 helpful
14 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

user tries logging in after machine left on over night, name and password entered, user waits 1-3 minutes, never even gets past login screen, then gets kicked back out to ctrl+alt+del splash screen. tries again, same results, has to reboot machine before can login. have tried
rebooting before going home for the evening, and even disabling diskeeper, still no luck. Tried disabling hibernation and running sp1 again and hotfixes, worked great for 4 days then leaving it on over 3-day weekend caused same problem.

14 replies

by pchw

We have to leave the machines up one night a week for remote updates, etc., to avoid interference with production. This only happens when the machine is left on overnight, and rebooting before leaving for the evening doesn't help.

by jas03

If you are trying to log into a network it might be an issue with drivers & hibernation (or stand by).
Try disabling hibernation and/or stand by on the system. Also chick on the NIC properties for a powersaving mode and disable it.
Hope that helps

by pchw

I will try this again. It didn't seem to take my comments. I already tried those options, and it made no difference. Thanks.

by blackdiamond

Hey,

Can anyone else login into the machine when this occurs? Tyring to determine if it is machine specific or possibly user related. How many system does this happen on?

by pchw

This varies. I have found frequently that if a different user logs on after the first user fails, then it tends to log on successfully. I have also ruled out profile issues, as it has failed on several accounts upon initial login, even mine, and I'm an admin. This is happening on two machines. Also, we have just incurred as of yesterday another issue on two other machines, which I think is related, where they try to log back on after the screen locks (the day after the one evening a week itstays on overnight), and it hangs in much the same fashion. Eventually it cancels out and I can log the user off and log in with my account. What is also unusual with the whole thing is that with these machines that don't want to log the user on after being on all night, occasionally it lets them log on just fine, so not even that is consistent. I ran the service pack/hot fixes, because there is an issue where XP won't "let go" of the account logged in after they log out. This did seem to fix the first machine for 4 days (until it was left on over a 3 day weekend). Also, if this was the case, you would think rebooting after log off would resolve that as well (which was one of the first things I tried).

by blackdiamond

Hey,

I guess at this point with something like this I determine my ?Dink Factor? whether is it something I want to continue Dinking with or just reload the system or just have them reboot when this happens. It sounds like they usually power the system down on the other days of the week, so rebooting seems like the lesser of two evils at this point.

Sorry I could not help with a better solution.

Thanx

by pchw

At first that is what I finally resolved to, just have them reboot first thing in the morning before logging on, and they were fine with this. The only problem is that this seems to be spreading to the second variation of the problem I mentioned. I'm not sure if it is the same thing, but it appears to be related at any rate. THese are brand new machines, and it is all occurring in the same unit. The thing is we have deployed several hundred machines with virtually identical builds, so I am concerned that this will start spreading like a virus. THAT is what keeps me from just letting it go. I think you can see where I am at on this issue as a result. Thanks for trying. : )

by mant

when you power on your system keep tapping PF8
this will take you to safe mode. select safe mode and wait till your desk top screen appears.
go to START >SETTINGS >CONTROL PANEL >ADMIN.TOOLS
>SERVICES.
Hi-Lite BACKGROUND INTELLIGENCE
inthe same window go to start up type click on the drop down arrow and select DISABLED then APPLY > OK and SHUT DOWN system via START button.power on the system again this should stop the freeze.

by pchw

This sounds like a good idea with one exception. I checked that service and it is set to manual, so it isn't starting. Is it possible that it might start up on its own at a later time (e.g. when the system is idle)? I am under the impression thatit won't start when set to manual unless something forces it to start. Please let me know if I am wrong in this thinking. If I am wrong, and it does have the potential to start on its own at a later junction, then I will give this a try. Thanks!

by mant

PCHW. when background intelligence is set to "DISABLED" the system will not boot up of its own accord when in standby, it will respond as normal only coming to life when prompted. if this does not work which it should you can set it back to manual again or even try setting it to automatic ,but automatic was the root problem with XP not letting users get by log on and systems hanging/freezing.

by pchw

Well, I applied this change and monitored it for a couple weeks (she forgot to leave her machine on last week), and unfortunately, it didn't work. Sorry for the bad news. Thanks for your help. On a lighter note, though, I have found that re-running the service pack and disabling the NIC power off feature is helping with machines not letting user log back in after machine has been locked during breaks/lunch. So far so good on that, anyway, just no solution for initial problem.

by ronhoughton

I know it's been awhile since this was posted but incase you do read this again, the reason it was happening was because machine was allowed to turn off the NIC when idle. When this happens on a domain machine it causes the machine to lose it's trust cert. from the server. Restarting the machine or the netlogon service is required to get a new trust cert.

by pchw

Thanks for your response. Actually, that was one of the first things I disabled, so that unfortunately does not solve the problem. Needless to say, the machine has been rebooted at least a hundred times since I disabled the nic. Thanks anyway. : )

This discussion is closed to new replies.