• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 839
  • Last Modified:

Unable to RDP to a Server 2003 R2 box due to permissions error

Recieve the following error when attempting to open a RDP session to my Server 2003 machine.
"To log on to this remote computer, you must have Terminal Server User Access permissions on this computer. By default, members of the Remote Desktop Users group have these permissions. If you are not a member of the Remote Desktop Users Group or another group that has these permissions, or if the Remote Desktop User group does not have these permissions, you must be granted these permissions manually."
I've checked membership on the remote Desktop Users group, and the user i am testing with is definitely in there.
Remote Desktop User group is allowed "Log on with Terminal Services" permission on the box in question.
Connection permissions are correct in Terminal Server Configuration.
I'm not sure where else to look.
This is a server 2003 R2 box also running an Exchange role.
0
EvanStein
Asked:
EvanStein
  • 5
  • 4
1 Solution
 
Radhakrishnan RITCommented:
Hi,

Could you check the following;

1) Administrative Tools>>Terminal Services Configuration>>RDP-TCp Properties>>Permission>>Make sure that the Remote Desktop Users group added in it.
0
 
EvanSteinAuthor Commented:
Confirmed, the RDU group is added to the Connection's security ACL.
0
 
Radhakrishnan RITCommented:
In addition to my previous update;

Domain Policy>>Computer Configuration>>Windows Settings>>Local Policy>>User Rights Assignments>>"Allow log on through Terminal Services">>Is there any restrictions?
0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
EvanSteinAuthor Commented:
No restrictions. The only member of that ACL is the RDU group.
0
 
Radhakrishnan RITCommented:
Is the TS running in trial period, i think there is 90 / 120 days grace period. I believe that this will be not the case?

Also, check the windows firewall, make sure that it's stopped and disabled.
0
 
EvanSteinAuthor Commented:
TS is in trial period, as we have just activated that role.

Windows firewall does not appear to be interfering. We are able to start an RDP session and log in. The error message is displayed after credentials are processed, but the TS session ends.
0
 
ABCStoreCommented:
Make sure you're not trying to log on to console, i.e. not using /admin switch for mstsc.exe
0
 
EvanSteinAuthor Commented:
Not trying to log in to console. I'm pretty familiar with MSTSC and command line switches. This is just a vanilla MSTSC session.
0
 
Radhakrishnan RITCommented:
Try rebooting the server and check the issue.
0
 
EvanSteinAuthor Commented:
this ended up being a licensing issue.
0

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now