Link to home
Start Free TrialLog in
Avatar of AE_JB
AE_JBFlag for United States of America

asked on

unable to send CTRL+ALT+DEL and log on

An older SBS 2003 box is locked and CTRL+ALT+DEL does not register.

The computer is usually accessed via Logmein.  There may have been an active session that were disconnected while "Lock keyboard and mouse" was enabled.
The mouse works fine.
I tried the following:
swapped keyboard with another known good keyboard, to a different port.
Tried connecting via RDP, it says the computer is unavailable.
Restarted the logmein service

Is there a way to log off the current user, or otherwise restore access, without forcing a restart?
SOLUTION
Avatar of David Kroll
David Kroll
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
It would be best to use the shutdown command and force a clean restart. "shutdown \\MACHINENAME -r -t 0" will remotely shutdown that machine.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of AE_JB

ASKER

Unfortunately, I don't have the authority to restart the server.  I used the command prompt from another workstation to query the active sessions on the server, and there is only one console session active, which is the account on the server that is currently locked.  I attempted to reset the session and received error 31
could not reset session id 0, error code 31
error [31]: a device attached to the system is not functioning

I will try again after unplugging peripherals, though most posts I have seen related to this error are result of internal drive failure.
Avatar of AE_JB

ASKER

I ended up forcing shutdown from the machine, as the system was unresponsive otherwise.