Determine which application is using the same port as RDP You can run the netstat tool to determine whether port or the assigned RDP port is being used by another application on the Remote Desktop server. To use netstat:. This indicates another application is using this port. 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:.
Look for an entry for the PID number that is associated with the port from the netstat output. The services or processes that are associated with that PID appear on the right.
Change the port assigned to RDP You should determine whether this application can use a different port. Important We recommend that you do not change the port that is assigned to RDP. If you have to change the port assigned to RDP, you must change the registry. To do this, you must be a member of the local Administrators group, or you must have been granted the appropriate permissions. To change the port that is assigned to RDP, follow these steps:.
On the Remote Desktop server, open Registry Editor. If the User Account Control dialog box appears, verify that the action it displays is what you want, and then click Continue. To change the port for a specific connection on the Remote Desktop server, select the connection under the WinStations key:. To stop and start the Remote Desktop Services service, follow these steps:.
On the Remote Desktop server, open the Services snap-in. To do thisin, click Start , point to Administrative Tools , and then click Services. Look for an entry for the port number that you assigned to RDP. The port should appear in the list and have a status of Listening. For more information, see the following Microsoft Knowledge Base Articles:. Verify that the listener on the Remote Desktop server is working To verify that the listener on the Remote Desktop server is working correctly, use any of the following methods.
Use the connection name and port number specific to your Remote Desktop server configuration. Method 2 To use the qwinsta tool to view the listener status on the Remote Desktop server:. Method 3 To use the netstat tool to view the listener status on the Remote Desktop server:.
From another computer, click Start , click Run , type cmd, and then click OK. At the command prompt, type telnet servername , where servername is the name of the Remote Desktop server, and then press Enter.
If telnet is successful, you receive the telnet screen and a cursor. If telnet is not successful, you receive the following error message:. Connecting To servername Could not open connection to the host, on port Connect failed. You can also download and use other troubleshooting tools, such as Portqry.
In the Properties dialog box for the connection, on the General tab, in Security layer , select a security method. In Encryption level , click the level that you want. To perform this procedure, you must be a member of the Administrators group on the local computer, or you must have been delegated the appropriate authority.
If the computer is joined to a domain, members of the Domain Admins group might be able to perform this procedure. As a security best practice, consider using Run as to perform this procedure. Any encryption level settings that you configure in Group Policy override the configuration that you set by using the Remote Desktop Services Configuration tool. Also, if you enable the System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing Group Policy setting, this setting overrides the Set client connection encryption level Group Policy setting.
When you change the encryption level, the new encryption level takes effect the next time a user logs on. If you require multiple levels of encryption on one server, install multiple network adapters and configure each adapter separately.
To verify that certificate has a corresponding private key, in Remote Desktop Services Configuration, right-click the connection for which you want to view the certificate, click the General tab, click Edit , click the certificate that you want to view, and then click View Certificate. At the bottom of the General tab, the statement, "You have a private key that corresponds to this certificate" should appear.
You can also view this information by using the Certificates snap-in. The High setting encrypts data sent from the client to the server and from the server to the client by using strong bit encryption. The Client Compatible setting encrypts data sent between the client and the server at the maximum key strength supported by the client.
To help troubleshoot this problem, enable CAPI2 event logs on both the client and server computers. This command is shown in the following screen shot. Click Start , click Run , type gpedit. Sign in to vote. I have one client machine - thin T Windows 7 embedded. It uses RemoteApps. Worked fine. Suddenly fail to launch RemoteApp with the error: The remote computer disconnected the session because of an error in the licensing protocol.
There are dozens posts with a fix of this error Thursday, October 22, PM. Checked the problematic machine thin client. When accessed first time Remote App the error message was differernt from the initial: "The remote computer disconnected the session because of an error in the licensing protocol" to "The remote session was disconnected because license store creation failed with access denied" 1.
Restarted Thin. It Auto logged on with Standard user profile. Then I opened RemoteApp without any problem. So looks like just registry corruption. Tuesday, November 10, PM. Friday, October 23, PM. Monday, February 6, PM. In the Properties dialog box for the connection, on the General tab, in Security layer , select a security method.
In Encryption level , click the level that you want. To help troubleshoot this problem, enable CAPI2 event logs on both the client and server computers. This command is shown in the following screenshot. To resolve this problem, back up and then remove the X Certificate registry keys, restart the computer, and then reactivate the Remote Desktop Services Licensing server.
To do this, follow these steps. If you have to restore this registry subkey in the future, double-click the Exported-parameters. Right-click each of the following values, click Delete , and then click Yes to verify the deletion:.
If this article does not help you resolve the problem, or if you experience symptoms that differ from those that are described in this article, visit the Microsoft Support for more information. To search your issue, in the Search support for help box, type the text of the error message that you received, or type a description of the problem. Skip to main content. This browser is no longer supported.
Download Microsoft Edge More info. Contents Exit focus mode. Please rate your experience Yes No. Any additional feedback? Note This article is intended for use by support agents and IT professionals. Note If you select the Don't allow connections to this computer option 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.
Note You can't connect to a computer that's asleep or hibernating, so make sure the settings for sleep and hibernation on the remote computer are set to Never. Hibernation isn't available on all computers. For information about making those changes, see Change, create, or delete a power plan scheme. Members of the local Administrators group can connect even if they are not listed. Important This section, method, or task contains steps that tell you how to modify the registry.
Important We recommend that you do not change the port that is assigned to RDP. Note To perform this procedure, you must be a member of the Administrators group on the local computer, or you must have been delegated the appropriate authority.
If the computer is joined to a domain, members of the Domain Admins group might be able to perform this procedure. As a security best practice, consider using Run as to perform this procedure. Any encryption level settings that you configure in Group Policy override the configuration that you set by using the Remote Desktop Services Configuration tool.
Also, if you enable the System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing Group Policy setting, this setting overrides the Set client connection encryption level Group Policy setting.
When you change the encryption level, the new encryption level takes effect the next time a user logs on. If you require multiple levels of encryption on one server, install multiple network adapters and configure each adapter separately. To verify that certificate has a corresponding private key, in Remote Desktop Services Configuration, right-click the connection for which you want to view the certificate, click the General tab, click Edit , click the certificate that you want to view, and then click View Certificate.
At the bottom of the General tab, the statement, You have a private key that corresponds to this certificate , should appear. You can also view this information by using the Certificates snap-in.
The High setting encrypts data sent from the client to the server and from the server to the client by using strong bit encryption. The Client Compatible setting encrypts data sent between the client and the server at the maximum key strength supported by the client.
0コメント