remote desktop - manually reset user / adjust timeout for user

when i finish a remote desktop session connecting to my xp pro box, if i click on start>log out i find that the session actually doesn't get fully closed. i can only log out this way twice before i get the "the computer is not accepting connections, it may be busy or limit may be exceeded"-type error message. ie the system thinks there are already 2 people logged on so, please, go away. it times out after about 48 hours, but this can obviously be inconvenient.

if i, rather than log out, just "disconnect" i *can* reconnect again without problem, and so have been doing this. but i recently had the problem where i reset the router on the remote side (wasn't thinking) twice, which of course interrupted the session but didn't fully close it on the xp box, which then, again, made it impossible to log in through remote desktop for another 48 hours (i was physically separated from my box by several thousand miles).

is there a way to either 1. up the number of sessions allowed before this hangs (a little extra padding so to speak) or 2. set a lower time out on the sessions (like an hour) or 3. manually log out the current users that i can run in a batch file through scheduled tasks (i set up my system to automatically reboot via "shutdown" each night - but this didn't log out the active user)

oh - and an easy one here - where is the xp equivalent of terminal services manager from win2k server? you know, where you can see all the currently connected accounts and selectively boot them?


Who is Participating?
KenneniahConnect With a Mentor Commented:
Most of what you are looking for can be found in gpedit.
Go to Start|Run and type gpedit.msc

Then under Computer Configuration|Administrative Templates|Windows Components|Terminal Services|Sessions you will find settings to set time limits on disconnected, idle, or active sessions, plus set it to terminate rather then disconnect sessions that have reached those limits.
Also, terminal services in Windows XP only supports once connected user at a time, so there should be no other "users" to boto. However, Terminal Services Manager is installed with the Windows 2003 Administration Tools Pack, and is able to look at the sessions on the XP computer.
jlathigeeAuthor Commented:
many thanks - that does the trick!
Great! Glad it worked out.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.