English Deutsch Français Italiano Español Português 繁體中文 Bahasa Indonesia Tiếng Việt ภาษาไทย
All categories

I have a box running Server 2003 along with Active Directory, File Server, and Print Server. I've turned on Terminal Server as well. As an Admin, I have no problem logging on from anywhere in the world. When I try to log on as a standard domain user, I get the following error:

"To log on to this remote computer, you must have Terminal Server User Access Permissions on this computer. By Default, memebers of the Remote Desktop Users group have these permissions. If you are not a member of the Remote Desktop 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."

All of my applicable users have already been added to the Remote Desktop Users group, and I don't have any policies in effect that would cancel this (I think. What policies are there that would cancel TS?).
Any help is appreciated. Thanks.

2007-02-26 09:43:22 · 3 answers · asked by greg_saladino 2 in Computers & Internet Computer Networking

3 answers

I had this identical problem on a 2003 server. Here are my relevant notes from the install job:

Tested terminal services internally and externally for connectivity, etc. using administrator account. No issues.
Tested using other user accounts. Security policies prohibited access. Multiple group policies, etc. involved in resolving security issues.
Users were added to Remote Operators and Remote Desktop Users in Active Directory. Local security policy on server was modified to allow users the right to log on locally, log on remotely and log on through terminal services session.
Upon modification of group policy and local security policy, all tests with standard user accounts were also successful.

Hope this helps!

PS. I would never put terminal services on a domain controller. Way too many security issues, unless you really, really trust your people.

2007-02-26 12:21:53 · answer #1 · answered by antirion 5 · 0 0

I have had a similar issue, however (after hours of pulling what little hair is left), my solution was quite simple:
In terminal services configuration I had to set the sessions properties. There set permissions and add in the appropriate groups.

2007-02-26 17:55:20 · answer #2 · answered by Gazza S 2 · 0 0

You should also check the box enabling users permission to log on remotely.

2007-02-26 18:37:22 · answer #3 · answered by Granitemill 1 · 0 0

fedest.com, questions and answers