exhuser
asked on
unable to rdp to server
I have a Windows 2003 server and cannot use remote desktop to connect to it. Several days ago the server displayed a message that it was low on resources. Is there anything I can do remotely (aside from rebooting) to enable resources for remote desktop?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I have no rdp or direct terminal access to the server. Is there anything I can run remotely?
You can retrieve performance counters remotely - maybe. Usually the server collapses after some time, asked until then less and less of means remain to get any info.
You can try if Sysinternals' psExec still works to start a process remotely. And/or use tasklist and taskkill remotely in psExec or locally. Both ways might show processes you can kill.
You can try if Sysinternals' psExec still works to start a process remotely. And/or use tasklist and taskkill remotely in psExec or locally. Both ways might show processes you can kill.
Hello exhuser !
Do you get an error message when trying to access to the server by mstsc.exe ?
Do you get an error message when trying to access to the server by mstsc.exe ?
The other option is to login to a machine on the network with admin creds.
Start, run
type: shutdown -i
Enter the name of the server and choose to restart it. It may take some time, but it should reboot.
Start, run
type: shutdown -i
Enter the name of the server and choose to restart it. It may take some time, but it should reboot.
ASKER
No error with mstsc.exe. The connection terminates right after I enter the password.
There was one active RDP, which worked, but not I was "smart" enough to logoff rather than disconnect...
There was one active RDP, which worked, but not I was "smart" enough to logoff rather than disconnect...
ASKER
Tried remote shutdown (shutdown -i). The server accepted the command but never rebooted.
Any idea what to do next?
Any idea what to do next?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I've tried mstsc and then, when the prompt came, entered the login credentials. The session terminated shortly. Is there a special format?
Yes, if you use mstsc /console
It should create a console session on the machine. If that doesn't work, hard boot it.
Just to confirm, when you used shutdown -i
YOu entered the offending server's FQDN in the box, chose restart, put a reason in, unchecked the wait 30 seconds box, and the OK, correct?
It should create a console session on the machine. If that doesn't work, hard boot it.
Just to confirm, when you used shutdown -i
YOu entered the offending server's FQDN in the box, chose restart, put a reason in, unchecked the wait 30 seconds box, and the OK, correct?
mstsc /v:hostname /console
ASKER