Vista unable to connect to terminal server

A terminal services license server is required for continuous operation. A terminal server can operate without a license server for 90 days after initial start up. For more information, see Terminal Server Licensing help topic. This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully.

For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base: How to back up and restore the registry in Windows. Troubleshooting a failure to connect through Windows Remote Desktop to another computer in a local area network LAN Ensure that there is not a general network connectivity problem using commands such as ping and ipconfig.

Ensure that Remote Desktop is enabled on the destination machine. Skip to content. 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. On the Terminal Server, open Registry Editor. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request.

The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:. If you do not see your language, it is because a hotfix is not available for that language.

For more information about how to obtain a Windows 7 or Windows Server R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:.

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time DST bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Important Windows 7 hotfixes and Windows Server R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems.

Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature. Important Windows Vista hotfixes and Windows Server hotfixes are included in the same packages. To work around this issue, delete the original certificate on the RDS server instead of archiving it at first.