PS2 mouse port stopped working on multiple Windows Server 2003 machines

This is weird.  I have 3 Windows 2003 servers which the PS2 mouse port stopped working on in the last 2 weeks.  I suspect a Windows Update but I don't know what to do now (other than buy some converters and start using USB port).  I've tested a USB mouse and it works.

I can't just replace the mice since this runs through a KVM switch which doesn't support USB.  But we have tested the servers without the KVM and have concluded that the PS2 port is no longer working.  
mpiaserAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

rindiCommented:
I would suspect the KVM switch to have caused this. A PS2 port shouldn't be hotplugged, as this can kill the port. KVM switches should prevent this from happening, but if this switch is bad or bad quality, they can cause ho plugging-like effects which can break the port.
0
mpiaserAuthor Commented:
That's the first I've ever heard that hotplugging a PS2 port can kill the port.   I've done it thousands of times without issue.  The KVM has been in use for a decade without problem so it seems odd that it just started messing up (although all things are possible).  I purchased a PS2 to USB adapter for each server and I will use the USB port instead of the PS2 port.
0
rindiCommented:
It doesn't always happen, but I have seen it happen now and then. The KVM switch is your common point which can cause this on multiple servers. I`d replace it.
0
mpiaserAuthor Commented:
We finally traced this problem to a bad cable.  Please close this question.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
mpiaserAuthor Commented:
We found the problem ourselves - it was a bad cable
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.