Software

Ask something
Question Locked

Locked XP Pro workstation - Login credentials grayed out

0 helpful
10 replies

by akrell

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

Locked XP Pro workstation - Login credentials grayed out (inactive text fields).

User locks or steps away from her machine (password prompt when return is set for screen saver). On occasion, when she hits ctrl-alt-del to log back into the session, the text fields for her credentials are disabled (greyed out). The user is noted as the active session. Neither user, nor Administrator can type into the credentials fields.

As a work-around, I had the user RDP to the locked machine using the console switch. The RDP session picked up the active user's session. I had her disconnect from RDP console, and retry at the local workstation. The credentials fields were now available and she could log in. This maintained her session, unsaved docs, and open applications.

Has anyone else experienced this issue and resolved (not just worked-around it)?

10 replies

by charliespencer

Could this result from someone else being remoted into the box during your first attempt to resume the session?

If it happens again, try setting the screen saver to "Blank". You don't say what the hardware is or what screen saver is in use, but it's possible the screen saver is hogging the resources.

I'm just speculating wildly here. Incidentally, welcome to TR. We've had a rash of newbies seeking hacking / cracking information lately. It's nice to see a new member with a legitimate technical question.

by akrell

There are no other users connecting to this workstation, remotely.

The windows logon screen saver is selected by Group Policy.

Thanks for the assistance.

by dawgit

but usually when 'sleep' or 'Hibernate' is used. Is there a long period of time between the screen saver mode to when the user tries to log back on? M$ had this problem but fixed it, now I'm seeing it come back. Did you do some changes to the sys lately? You might check the M$ site to see if they have a fix that you didn't realize you'd need before. (they are good at that)
edited to fix some spelling, of course.-d

by hal 9000

When the Live Update Option has been turned off and WGA is telling the system that it's not quite right so you get screwy errors cropping up from time to time. No it doesn't matter if everything is up to date it still happens.

When I spoke to M$ about this problem I was told to do a repair install and then log into their server to confirm that I had a valid copy of XP Pro. Basically after mucking around for the better part of 3 days I was told to turn on Live Updates and let it alone. You need to use a GP to disable the Live Updates from running if you are pushing out patches from a central server. If not just allow Live Update to download and then you can chose when you want to install any new patches that the computers pick up.

Col

by b.t.walter

I can vouch for this issue. I saw it for the 1st time thismorning. We require our users to log off their machines at E.O.B each day for nightly patches that are pushed from our server. User went to log in thismorning and wasn't able to enter in her credentials. Had user reboot and user was able to log in...
I wish M$ would give some resolution to this.

by 1bn0

Although this is the first successful workaround I have heard of.

The only other resolution I have seen is to reboot the workstation.

by b.t.walter

After searching event logs, and contacting our help desk techs, it turns out this happens when someone VNC's into the system and the VNC connection does not fully disconnect. Hope this helps.

by jthurstenson

I've just experienced this problem for the first time - I had installed VNC as a support tool just prior to the problem. A restart fixed it... is this an MS security feature or just a problem resulting from the VNC connection as b.t. has said? If a VNC problem, then is there a better VNC server flavor to use?

by b.t.walter

What version of VNC are did you install? I haven't seen the issue since upgrading to 4.0.

This discussion is closed to new replies.