Unable to RDP to a W2k3 Server after joining the domain.
We rename a Windows 2003 server and join it to the domain from workgroup. When I login as a domain user, I am getting a message - Please see the screen shot.
I have already make sure the user belongs to the local Remote Desktop Users group which has permission to remote in. Both TS Licensing and Terminal Services are running.
Try adding the user to the Remote Desktop Users group in Active Directory.
MohanrajM
User is having admin rights or not?...check with the other server with the user account so that you will know there is a issue with access not with server.
Mahesh
Just check if you have set any GPO which having following user rights enabled for this server:
"Allow logon through terminal services"
If that's the case, you must have configured some domain groups there which can access server remotely
Just add user to that group and check
As mentioned, the server was renamed before joining the domain. Do you think that is the cause of what is happening?
Mahesh
On windows 2003 server, navigate to terminal services configuration->rdp-tcp->properties->permissions tab
and add "Domain Users" to the permissions tab and please check
The error message is "To log on to this remote computer, you mush have terminal server user access permission on this cojputer. By default, members of the remote desktop group have these permissions. If you are not a member of the remote desktop user group......"
I have already followed your suggestions in bullet 2, 3, 4 but same result. I still cannot login.
RDP-TCP properties security permission already shown local Remote Desktop Users group is included. The local Remote Desktop group does include the domain users group.
Sorry, I do not want to send a sceenshot over the internet.
What about step 1 , did you created a new user in seperate OU with no inheritance properties and that OU should not have any GP applied on it . Add that user to RD group or you can add it especially on the RDS machine. Check if it works or not.
Oh my bad , Did you mentioned that the role was already installed on the machine and later you joined the domain. If that so , its not the right approach. Add machine as member server and then add the role on it.
nav2567
ASKER
Sorry, I have tried that but they just don't work. I will have to revisit the issue later.