if anyone can help me, the problem i'm having is i cant get one user to remote control another user through terminal services manager. this person has been able to remote control everyone for yrs with no problem until recently (last couple weeks) she keeps getting access denied error. error is: session (id#) remote control failed. (error 5 - access denied).

nothing has changed with her acct, even after i try to add her to the admin acct she still gets access denied. whether she logs on TS from home or i log on her session from the office, still same error. to me, it seems like a problem with either her profile or a configuration setting on TS itself.

if anyone has any ideas of what could be causing this and how to fix it, would be greatly appreciated....thanks!

oh, windows 2k server with terminal server 2k.

i can actually respond to my own issue somewhat....i played around a lot with permissions of the rdp clip in terminal services configuration and somehow i was able to give this person the correct permissions to remote control. why she suddenly was getting denied, i really do not know, nothing changed with the permissions ever that i touched and it only started happening a few weeks ago. if someone has any ideas of how this couldve happened, please throw them my way....thanks!

I've come across this problem during the past couple of weeks. We have seven live TS boxes. Six of the seven servers have this problem - one remains ok. We also have a test server, which is fine. At least I have something to work on for comparison.
From what I have seen, it could be related to the local administrators group of the server. If you add a group or user requiring the ability to remote control to the local administrators group (and that group/person has the rights set up on the RDP Permissions within Terminal Services Configuration on that box) then they can start controlling people again. This is our short term fix.
As one server is working ok, I can eliminate any policies being applied - policies are still being applied to that server ok.
We did update the anti-virus to a newer version but have eliminated that aswell by removing it.
I have double checked sercurity within the likes of services, local security policies etc.
Have also double checked the hot fixes that have been applied and so on.
Just to let you know, we always use a clone for our Terminal Servers - ensuring they are all the same.

It will be a matter of time before I close in on the problem and will post on here with a possible solution/reason for you.