cannot type password to log into DC

[zephyran]

One of our Win2K domain controllers is having an apparent keyboard problem. I was using it, locked it when I walked away, and when I came back to it, I couldn't type in the password to unlock the server. Most keystrokes cause the server to beep from the internal speaker, though some keys (like Backspace and the Spacebar) do appear to register some kind of characters.

The server connects to the keyboard through a KVM switch. I've tried connecting the keyboard and monitor directly to the server, with no luck. The keyboard itself doesn't appear to be bad, however, because the other servers on the KVM work fine.

The server is still accessible remotely, and otherwise appears to be working fine. There aren't any clues in the Event Logs as to what may be happening. Is there any way I can fix or troubleshoot this without having to reboot the server?

 

[DirtDawg]

just a quick question, if you unlock the server remotely. then open a txt file on the server and type does everything appear ok? just sounds like the keyboard port may be haveing problems might have to switch to a usb keyboard on the server.

 

[zephyran]

I couldn't unlock it remotely (neither Terminal Services nor a remote control program like PCAnywhere were installed), but I could access its resources remotely.

Finally, after being locked out of it for a couple days, I was able to get it responding again (after typing the unknown characters from the Backspace key in the Username field). The last time I had something like this happen was when I had the Russian language set up on my computer and locked it while that language was still set as the primary.

I don't have any other language than English, and no strange fonts or keyboard types, installed on that server. What could have caused this, and what can be done to prevent it from happening again?

 

[beerhunter2]

Have you checked the Num Lock key?

Help! I've fallen and I can't reach my beer.

 

[zephyran]

That, Scroll Lock, and Caps Lock were the first ones I checked, but none of them should have caused (or did cause) this problem.

 

[ashpp]

The likely culprit is the KVM. Even though you changed the keyboard and placed it directly into the server you need to do a reboot for the PS/2 port to initalize.