If I remember correctly, I got this one from Jeff Middleton a while back . . .
It's happened to all of us at one point or another. We need to TS into one of our servers to do a simple little configuration change for a client. However, when we try to connect we get that dreaded message that we can't connect because the maximum number of connections has been exceeded. You know there must be a stray TS session hanging out there - but how do you get by this without having someone log in locally?
Assuming you have VPN access into the LAN, you'll be fine. The first thing you need is a copy of tsadmin.exe on your PC. You can get this by copying it down from any Windows 2000 / 2003 server (it's in the \Windows\System32 directory), or you can extract it from Windows 2000 SP4 if you have that handy as well. Once you have tsadmin.exe on your PC, simply run it. VPN into the destination LAN, then run tsadmin.exe. Under the Actions heading, click 'Connect to Computer' and enter the netbios name of the remote server you're locked out of. Voila! You're controlling the TS sessions on the remote server, so you can kill off those old idle sessions so you can TS in. Very cool - very slick.
Of course, you could also go a different route and use something like TightVNC - but that requires it to be installed on the server beforehand. If it isn't installed, it's not going to help much when you find yourself in this position . . . :^)
Sat, Oct 2 2004 13:39