And here I thought I would be done with Windows 2000 Advanced Server. Oh well.
Basically you’re allowed 2 RDP sessions and 1 console (local) session on win2k server. Server 2003/2008 allow you to use all 3 sessions remotely, which is a definite plus. Easy way to get to the console session of 2003/2008:

Start, Run
mstsc /admin
IP or Name of your server

Easy way on Windows 2000. Uh, THERE IS NO EASY WAY.
Our situation:
2 Windows 2000 Advanced Servers
Located 120 minutes away
Not on the domain (workgroup)
One of the servers had the maximum number of connections
The other server we could login no problem

As long as you have rights (privs) to the admin share (c$) of the computer, you can very easily connect:
1.) I logged into the win2k server that still worked
2.) Pulled up the command prompt
3.) Typed qwinsta /server:192.168.20.150
4.) Typed rwinsta /server:192.168.20.150 sessionid

Basically qwinsta will query for all the active/disconnected RDP sessions on the server. Rwinsta will remove the session id you pick. Check out the picture for more information.

Then just connect as usual.

******EDIT******
OK, so sometimes I’m a little slow on the uptake. I forgot how to manage remotely without being part of the domain. Authenticate as a user on that system and you can do it all remotely – ie if BOTH of those servers had max connections, what would I do?

net use /user:usernamehere \\ip_of_the_server\c$
This will prompt you to enter a password for the username you selected
Now you can run the same commands above.

ALSO, it looks like you can use:
query session /server:192.168.20.150
and
reset session 36 /server:192.168.20.150
as those are easier to remember on new systems.