Desktop

First, Check your documentation and switch the servers being displayed to see if the problem is an nonresponsive keyboard or a server. Switch them manually if that option is available. Does the mousre work? If not, then :
Second, get a couple of known good keyboards, monitors and mice to bypass the KVM switch. Shut down servers then attach and reboot. Can these servers be acessed remotesly to do so? Hmm! are they being remotly accessed now?
Third. Now log into each server. If they all work, the issue is either the kvm switch/keyboard issue If one of them doesn't. Thats the problem.

Last year I installed a lightweight (in more sense than one) KVM switch and saw how it continuously generated mouse port interrupts into the event log of the two Windows NT servers, the W2K server was not affected. After the KVM switch was replaced, the problem disappeared.

Have you checked if the mouse and keyboard connectors are OK, any bent pins?

Some KVMs give the option to lock the inputs, and also give a sign that it is locked, such as flashing lock lights. Check your KSM switch manual/website, you will normally find that presisng "scroll lock twice and a action key" will acess KVM switch commands. Might be worth a look.

If I am not mistaken, the flashing of the leds mean the kvm is expecting you to tell it which machine you wish to connect to. Until you select a system, the keyboard will not work. Press a letter that corresponds to the server. Or if you press the Esc key, that will cancel the request. The request is usually started by pressing the Ctrl key twice.

Thanks to all who responded for this advice. It turns out when I replaced the keyboard cable (after unplugging it) from the KVM device, the LEDs stopped blinking. So far so good.

Thanks also for the Scroll Lock keyboard shortcut which I will try to remember if this situation occurs again.

This question was closed by the author