terminal server licenses exceeded (xp remote desktop to w2k svr over vpn)

[John A Grandy]

for months, i have been successfully connecting xp remote desktop to a w2k
advanced server via a vpn connection.

yesterday, i began getting the following logon error messages:

1. "the terminal server has exceeded the maximum number of allowed
connections"

2. "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"

my vpn connection still works fine (i can map network folders to the server)

the strange thing is, i am the only person who connects to this server via
remote desktop, or any other means. the logon account i use is a local
administrator on the server. however, it is not a domain account. i do not
logon to the domain.

i hesitate to reboot the server because it is not clear to me that remote
desktop would work following a reboot.

 

[nut cracker]

If your server was configured for management mode, you get 2 concurrent
sessions. If you were configured for application mode, you are limited by
the number of seats you told the licensing service you have.

Now, if you are in management (administration) mode, i would say that you
have 2 orphaned sessions on the box. Since these consititue your 2
connections, you are SOL when you try to connect.

You need to adjust the policy in the terminal services manager, or terminal
sevices client connection manager. I usally set it so that there is a 2 hour
limit, and broken sessions are reset after 5 mintues. Disconnected session
have no timeout. This way, I can start something... go away for a while, and
come back and reconnect to the same session.

Have fun...

NuTs

 

[John A Grandy]

<<<
You need to adjust the policy in the terminal services manager, or terminal
sevices client connection manager.
Could you provide more details? I've got to give specific instructions to a
sysadmin at the remote location.

 

[nut cracker]

no offense, but if he doesnt know then he is in the wrong job.

tell him to reset the currect connections through the terminal services
manager.

if you have to tell him to right click on them and select "reset", you may
also need to blow his nose for him too.

He should be familiar with the information presented here:

http://support.microsoft.com/default.aspx?scid=kb;en-us;186566

Cheers,

NuTs