Terminal Server Lockout
I have a web server colocated at an ISP
I connect to this box using terminal services. I just got locked out as the administrator connection got dropped (disconnected). Its a bug in win2k that it doesn't reconnect to the same session. Anyone know a way or any tools that will let me get back into it ?
Its not on a domain, its a standalone win2k server.
thanks this is urgent
I connect to this box using terminal services. I just got locked out as the administrator connection got dropped (disconnected). Its a bug in win2k that it doesn't reconnect to the same session. Anyone know a way or any tools that will let me get back into it ?
Its not on a domain, its a standalone win2k server.
thanks this is urgent
Hi!
What message do you get when you try to establish a terminal session?
NetoMeter
<removed by cs>
What message do you get when you try to establish a terminal session?
NetoMeter
<removed by cs>
ASKER
netometer: Thanks, theres Two msgboxes:
"The terminal server has exceeded the maximum number of allowed connections"
and
"The system can not log you on
The system has reached its licensed logon limit
Please try again later
Please try again or consult your system administrator"
James: thanks, I've got a win2003 here somewhere so I'll see if its on that and give it a go.
"The terminal server has exceeded the maximum number of allowed connections"
and
"The system can not log you on
The system has reached its licensed logon limit
Please try again later
Please try again or consult your system administrator"
James: thanks, I've got a win2003 here somewhere so I'll see if its on that and give it a go.
ASKER
I've now tried win2003 terminal services manager, it seems to only work on the lan, not on the internet.
The box is not firewalled.
The box is not firewalled.
ASKER CERTIFIED 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
Thanks chaps
shutdown came back with "the network path was not found". I used shutdown -f -r -m IP and also shutdown -i
There doesn't seem to be a password option so not much chance given that my local network is unrelated to the standalone server in terms of domain etc.
reset session also errors. Again there doesn't seem to be any way to get yer credentials in place first, so its going to fail on authentication
It gives "Error opening Terminal Server xxx.xxx.xxx.xxx"
shutdown came back with "the network path was not found". I used shutdown -f -r -m IP and also shutdown -i
There doesn't seem to be a password option so not much chance given that my local network is unrelated to the standalone server in terms of domain etc.
reset session also errors. Again there doesn't seem to be any way to get yer credentials in place first, so its going to fail on authentication
It gives "Error opening Terminal Server xxx.xxx.xxx.xxx"
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks James, It said "the network path was not found". Maybe the firewall at this end doesn't help.
I can get a reboot in one hour anyway, so thanks for your help.
I can get a reboot in one hour anyway, so thanks for your help.
ASKER
Thanks chaps. Its been rebooted.
Well it shows the box is well secured anyway I s'pose.
Its good to know about the shutdown, net use ipc$ and reset session commands for future ref
Well it shows the box is well secured anyway I s'pose.
Its good to know about the shutdown, net use ipc$ and reset session commands for future ref
plq
Welcome, glad to help
Cheers
JamesDS
Welcome, glad to help
Cheers
JamesDS
You could try using the Terminal Services Manager supplied with the ADMINPAK, but that will require ports other than 3389 open, so probably won't work.
If your server is not set to logoff disconnected sessions, then the only thing you can do is call them and request a reboot.
Cheers
JamesDS