Terminal server unable to connect to license server

I've installed this type of system for several customers. TS role is installed. All access credentials Password vs ,etc The strange part is ordinary domain users can not access the TS with their own credentials It's a DC; by default only admins can remote to it.

You need to change the group memberships. Are you giving users local admin rights and remote desktop rights on the machine in question? Domain Users do NOT have local admin rights. When you gave access, which group on the TS are they in? If memory serves me, they should be in "Remote Desktop Users".

Admins automatically have access but other's do not. For example, I walk up to the DC1 console with my Admin account logged in, sense only admin accounts will get me into DC1. If I access it from another machine it will not work. It says my credentials are wrong. How is that possible? My Domain is up, and all of the joined systems are found in domain list. Therefore, Authentication was working.

I hope I would be able to help you. I was having this issue administering my Window Server also. I wanted my domain users to be able to establish a remote desktop connection to my Window Server without having to be assigned the role of an administrator.

So I searched everywhere online, messed with a lot of stuff and then got the fix after a lot of trials. Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more. Domain users unable to logon to remote desktop server Ask Question. Asked 6 years, 2 months ago. Active 3 years, 3 months ago.

Viewed 46k times. Improve this question. Users can access a Terminal Server from within a corporate network or from the Internet. Terminal Services supports two concurrent remote connections to the computer. To allow more than two administrative connections or multiple user connections you must install the Terminal Services role and have appropriate TS CALs. By default, the connection is configured to allow an unlimited number of sessions to connect to the server.

Remote Desktop Disconnected. This computer can't connect to the remote computer. Try connecting again. If the problem continues, contact the owner of the remote computer or your network administrator. The Remote Desktop Users group on a Terminal Server is used to give users and groups permission to remotely connect to a Terminal Server.

You can use the following procedure to add users and groups to the Remote Desktop Users group by using the Remote tab in the System Properties dialog box on the Terminal Server. Membership in the local Administrators group, or equivalent, on the Terminal Server that you plan to configure, is the minimum required to complete this procedure. If you don't select Allow users to connect remotely to this computer on the Remote tab, no users will be able to connect remotely to this computer, even if they are members of the Remote Desktop Users group.

The default port assigned to RDP is To resolve this issue, determine which application is using the same port as RDP. If the port assignment for that application cannot be changed, change the port assigned to RDP by editing the registry. After editing the registry, you must restart the Terminal Services service. After you restart the Terminal Services service, you should confirm that the RDP port has been correctly changed. The listener component runs on the Terminal Server and is responsible for listening for and accepting new Remote Desktop Protocol RDP client connections, thereby allowing users to establish new remote sessions on the Terminal Server.

There is a listener for each Terminal Services connection that exists on the Terminal Server. Connections can be created and configured by using the Terminal Services Configuration tool. You can run the netstat tool to determine if port or the assigned RDP port is being used by another application on the Terminal Server. To determine which application is using port or the assigned RDP port , use the tasklist command line tool along with the PID information from the netstat tool.

You should determine if this application can use a different port. If you cannot change the application's port, you will have to change the port assigned to RDP.

To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority. Incorrectly editing the registry might severely damage your system. Before making changes to the registry, you should back up any valued data. The RDS deployment uses the correct license server, licensing mode, and policy settings. The details of the configuration depend on the type of deployment that you have:.

In the policy list, right-click Use the specified Remote Desktop license servers , and then select Properties. Select Enabled , and then enter the name of the license server under License servers to use. If you have more than one license server, use commas to separate their names. In the policy list, right-click Set the Remote Desktop licensing mode , and then select Properties.

Follow this section's instructions carefully. Serious problems can occur if the registry is modified incorrectly. Before you starty modifying the registry, back up the registry so you can restore it in case something goes wrong. To resolve this problem, back up and then remove the X Certificate registry keys, restart the computer, and then reactivate the RD Licensing server.