5 replies
by mckaytech
Since they work during POST, I would rule out a hardware failure and would concentrate on the drivers. There are a couple of options for fixing that, none of them particularly pretty.
First, I would try to get into the box with a telnet session or a Terminal Services session since you know the network connection is good. You could then go to Control Panel-Keyboard, etc and get to the Driver Properties page and update the driver, then do the same for the mouse.
If that doesn't work, probably your next best bet is going to be a repair from the Recovery Console (if it will even work).
If that doesn't work, you could (but here's where it gets risky) do a remote registry hack to remove the existing drivers and hope they get auto-detected and installed on the next boot.
Or you could try booting up with a serial mouse rather than a PS/2 and see if that at least gives you the mouse back. That won't do you any good as far as logging in because I'm not aware of anyway to "mouse" the login information, but it might be a welcome relief to have something working again.
If none of those work, you're probably looking at an OS re-install unless the server manufacturer provides some type of management software that might do the trick (there is a lot you can do remotely with Compaq servers).
Best wishes with this challenging problem!
paul
by seadogs
I'm going to glob of the previous members answer specificaly the remote access part.
If the server does come up on the net goto:
http://www.dameware.com/dw2/download/
and get dameware NT utilities or just the remote control app. You have to have admin rights to the machine and you can remotely install their mini RC app. Ive used it a couple of times when I had a situation like yours. It accesses the keyboard and mouse at the system level so even if there is a driver failure somewhere after the POST it should still work.
Good Luck!
by seadogs
by seadogs
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending