webknot
asked on
W2K Mouse on startup using KVM
I've 3 W2K machines hooked to a Belkin electronic KVM. One is an Exchange server. I had only W2K server (not Exchange) running for a couple months without any problems. Since installing the Exchange components, I am now having difficulties with the mouse being recognized on boot. I.e., after all the machines have booted, one of them does not have a cursor (it does have a keyboard and display).
The timing may be coincidental as it is not the Exchange machine but one of the others that consistently is missing the mouse. I've had a lot of trouble with this since I started using KVMs a year or two ago and I'm reluctant to experiment as the problem machine is a critical component in a productin network.
It's pretty certainly not the cables becuase if I restart the machine with the KVM active on that port, the mouse is there. I suppose the KVM could be faulty - I'll try it on a different port. Any other suggestions?
The timing may be coincidental as it is not the Exchange machine but one of the others that consistently is missing the mouse. I've had a lot of trouble with this since I started using KVMs a year or two ago and I'm reluctant to experiment as the problem machine is a critical component in a productin network.
It's pretty certainly not the cables becuase if I restart the machine with the KVM active on that port, the mouse is there. I suppose the KVM could be faulty - I'll try it on a different port. Any other suggestions?
ASKER
OmniView SE 4-Port.
Have you looked into their troubleshooting steps, paticularly the mouse drivers supported? http://web.belkin.com/support/faq_qa.asp?pid=190&cid=1
Belkins are nasty. I've dealt with many customers and found the same issues re-occur. The KVM needs time to 'sync' before the keyboard and mouse are ready. Try counting to two after switching and before touching the keyboard/mouse.
I've seen and had this problem with Belkins several times. I've found that newer scroll mice, particularly Compaq (HP)cause the issue. Each time I corrected it by getting an older scroll mouse. Here is a link you may already have seen. http://web.belkin.com/support/faq_qa.asp?pid=190&cid=#887
Hope this helps,
ZENworker
Hope this helps,
ZENworker
Belkin has also confirmed there is problem with their KVM boxes and certain Compaq servers - an error they haven't been able to correct to the best of my knowledge. I know it happens on Proliant ML330, ML350 and ML530.
Strangely, workstations attached to the same KVM box have no problems and neither do older servers.
Strangely, workstations attached to the same KVM box have no problems and neither do older servers.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Great answer. I've changed ports on the KVM, and that looks to be helping but this looks like a really good solution. Thanks.
What model Belkin is it?