Terminal Services and Maximum Connections Exceeded
-
Ok I am sick of rebooting our server every time it flipping well runs out of terminal service "slots." Basically we remote connect to our hosting box and we cannot always logout properly as the line may drop etc. We do try to avoid maxing out the number of active/disconnected connections but every now and then it does max out. So does anybody know how to "reset" this situation without actually rebooting the server? Rebooting a server hosting websites is never a good idea, especially for something so daft as this. The OS is W2k. ta
Paul Watson
Bluegrass
Cape Town, South Africa -
Ok I am sick of rebooting our server every time it flipping well runs out of terminal service "slots." Basically we remote connect to our hosting box and we cannot always logout properly as the line may drop etc. We do try to avoid maxing out the number of active/disconnected connections but every now and then it does max out. So does anybody know how to "reset" this situation without actually rebooting the server? Rebooting a server hosting websites is never a good idea, especially for something so daft as this. The OS is W2k. ta
Paul Watson
Bluegrass
Cape Town, South Africa- Log on to the Terminal Services-based server locally.
- Click Start, point to Programs, point to Administrative Tools, and then click Terminal Services Manager.
- Click the appropriate Terminal Services-based server. Note the Users Tab in the right pane.
- If there are two remote sessions, right-click one of the users with a Remote Desktop Protocol (RDP) session, and then click Logoff. (A reset also accomplishes this goal, but does not save profile changes.)
-
- Log on to the Terminal Services-based server locally.
- Click Start, point to Programs, point to Administrative Tools, and then click Terminal Services Manager.
- Click the appropriate Terminal Services-based server. Note the Users Tab in the right pane.
- If there are two remote sessions, right-click one of the users with a Remote Desktop Protocol (RDP) session, and then click Logoff. (A reset also accomplishes this goal, but does not save profile changes.)
Richard_D wrote: Log on to the Terminal Services-based server locally. Thanks for the effort but that is exactly the problem: Our server is located in a veritable castle co-location facility which requires DEFCON 4 clearance to get into :) So we remote connect to do anything. If we have to have something physically done to the server then we call up the co-location facility and they charge us an hours worth of work to do something.
Paul Watson
Bluegrass
Cape Town, South Africa -
- Log on to the Terminal Services-based server locally.
- Click Start, point to Programs, point to Administrative Tools, and then click Terminal Services Manager.
- Click the appropriate Terminal Services-based server. Note the Users Tab in the right pane.
- If there are two remote sessions, right-click one of the users with a Remote Desktop Protocol (RDP) session, and then click Logoff. (A reset also accomplishes this goal, but does not save profile changes.)
Richard_D wrote: Q250991[^] might help: My correction! You are a genius Mr. Rhichard_D. The KB article started out just like all the others but then at the bottom it went on to tell how you could do it. Lovely stuff, thank you, I owe you a beer :-D
Paul Watson
Bluegrass
Cape Town, South Africa -
Ok I am sick of rebooting our server every time it flipping well runs out of terminal service "slots." Basically we remote connect to our hosting box and we cannot always logout properly as the line may drop etc. We do try to avoid maxing out the number of active/disconnected connections but every now and then it does max out. So does anybody know how to "reset" this situation without actually rebooting the server? Rebooting a server hosting websites is never a good idea, especially for something so daft as this. The OS is W2k. ta
Paul Watson
Bluegrass
Cape Town, South Africa -
Remember to avoid this situation you have to tell your admins to log off when done with TS and not to disconnect . Disconnecting leaves these sessions connected ... Just some advice ... Chris
Chris F wrote: Disconnecting leaves these sessions connected ... Just some advice ... Thanks and very true advice. We do ensure that we logoff and not just disconnect, but due to the nature of our remote connection often we don't get a chance to do either as the line drops.
Paul Watson
Bluegrass
Cape Town, South Africa -
Chris F wrote: Disconnecting leaves these sessions connected ... Just some advice ... Thanks and very true advice. We do ensure that we logoff and not just disconnect, but due to the nature of our remote connection often we don't get a chance to do either as the line drops.
Paul Watson
Bluegrass
Cape Town, South AfricaHmmm, do you all log on as different users? If you log on as the same user, I don't think you have that problem. I know I don't ;) - Anders Money talks, but all mine ever says is "Goodbye!"
