Question Locked

Server 2003 RDP Connection Issues

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have a server that won't allow new users to connect via RDP after I add them to the RDP users group. Terminal services is running and I have enough CALs. I've heard of this being an issue if a domain server was upgraded to a domain controller. I was told that there was something I could do with a GP to enable users to get access. If anyone has any ideas let me know please!

5 replies

by techrepublicsucks

Microsoft changed things in Windows Server 2003 from the way they worked in Windows 2000 Server. In 2003 RDP and TS are two different functions that can be enabled independently of one another and serve different purposes.
RDP is enabled by going into the server's System Properties and enabling Remote Desktop connections. RDP has a maximum of 2 simultaneous connections and is intended only for use by server administrators.
TS is installed through add/remove Windows components and requires the installation of TS CALs.
Because the difference of TS and RDP is not reflected in your question I am not sure of your goal. However, I can see 3 possible approaches based on your post:
1. Have users RDP into the server. This is a bad idea because a user could easily mess up your server. As I said, it is for administrative use only.
2. Have users TS into the server. I have not used this too much because of the hardware and software costs to run a TS server. After all, a TS server should be a stand-alone or member server dedicated to TS. The recommended configuration usually means a lot of CPU and RAM power. I do recall that TS users must be in the TS local users group either directly or in a group that has membership to the local users group. I know Microsoft has a step-by-step for setting up TS in Windows Server 2003. Just make sure not to mix it up with RDP when doing your research.
3. Have users RDP to their office workstation. This is done by setting up a VPN connection for the remote user and then making an RDP connection to their office workstation. Here is the GPO setting to enable RDP on the workstations so you don't have to manually set them up:
Computer Configuration > Administrative Templates > Windows Components/Terminal Services > Allow users to connect remotely using Terminal Services
You will also need to punch a hole in the workstation?s local firewall or disable it for RDP to work. This is also a computer policy setting. I usually disable the workstations? local firewall for the domain profile and enable it for the standard profile. That way notebook users? firewall will be enabled when they are out of office. (See Computer Configuration > Administrative Templates > Network/Network Connections/Windows Firewall/Domain Profile and Network/Network Connections/Windows Firewall/Standard Profile)
Link the GPO(s) to the OU that contains your computers. Reboot or run "gpupdate /force" to make it take effect on the computer.
FYI: I use method 3 on most of my client networks and use WinVNC for Windows 2000 computers since they don?t have RDP.
I hope this helps you find your way.

by beersee112

Thanks victim. I'll give this a try and let you know how it works.

by beersee112

I got TS to work with users by adding them individually to the "Allow logon through Terminal Services" and to the RDP group.

When I tried adding a group to the "allowed" section so i could just put users in the group, it broke everything. New users can't connect no matter if they are allowed via the group or specifically in the GP. Old users that I took out of the "allowed" section are still able to connect though.

If anyone can help I really need it. Thanks!

This discussion is closed to new replies.