Windows Terminal Services

[BodShane]

This is one of the most common problems on Windows Terminal Services. The Terminal Services is licenced for a maximum of two connections by default, unless ofcourse someone decides to buy more licenses from Microsoft (I doubt that though!!).

So, when its two connection limit is reached, it does not allow any more connections and gives you an error (not exactly replicated here, please check for exact wording!!).

Maximum connection Limit reached

Now you got two options in this case:

1. You can ask the other person (hopefully the system owner) to log out and give you access.

2. You can log in via telnet and follow the following

a. List all the tasks presently running

tasklist

b. Note down the Process ID's of the processes associated with rdpclip

c. Kill all the tasks associated with "rdpclip" (repeat till all processes
are killed )

taskkill /pid <processID>

d. Finally, kill the rdpclip sessions (by now, these should be the only
ones assosciated with rdpclip.exe)

taskkill /pid <processID>

e. Now, try to log on via terminal session

P.S.

There also a third method....namely reoot the machine, and be the first person to log on via terminal servcies client