-->
Sep 22, 2020 Remote Desktop Licensing server is on Windows Server 2019 Sometimes (I would even say quite rarely) users got disconnected from the RDS server all at the same time. In just a few seconds they are able to reconnect. It is not because of the Internet outage because multiple users connect to the separate servers from different physical locations. Keep Terminal Services & Remote Desktop From Disconnecting. I have run into many cases where my customers had a hard time with a remote desktop connection to their server disconnecting. I did all the tweaks needed to make sure terminal services and remote desktop (They are the same) didn't have a timeout limit.
This article helps you understand the most common settings that are used to establish a Remote Desktop session in an enterprise environment, and provides troubleshooting information for Remote desktop disconnected errors.
Applies to: Windows Server 2012 R2
Original KB number: 2477176
Note
This article is intended for use by support agents and IT professionals.
Remote Desktop Server
A Remote Desktop Session Host server is the server that hosts Windows-based programs or the full Windows desktop for Remote Desktop Services clients. Users can connect to an RD Session Host server to run programs, to save files, and to use network resources on that server. Users can access an RD Session Host server from within a corporate network or from the Internet.
Remote Desktop Session Host (RD Session Host) was formerly known as the Remote Desktop server role service, and Remote Desktop Session Host (RD Session Host) server was formerly known as Remote Desktop server.
Remote connections for administration
Remote Desktop supports two concurrent remote connections to the computer. You do not have to have Remote Desktop Services client access licenses (RDS CALs) for these connections.
To allow more than two administrative connections or multiple user connections, you must install the RD Session Host Role and have appropriate RDS CALs.
Symptom 1: Limited Remote Desktop session or Remote Desktop Services session connections
When you try to make a Remote Desktop Connection (RDC) to a remote computer or to a Remote Desktop server (Terminal Server) that is running Windows Server 2008 R2, you receive one of the following error messages:
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.
Also, you are limited in the number of users who can connect simultaneously to a Remote Desktop session or Remote Desktop Services session. A limited number of RDP connections can be caused by misconfigured Group Policy or RDP-TCP properties in Remote Desktop Services Configuration. By default, the connection is configured to allow an unlimited number of sessions to connect to the server.
Symptom 2: Port assignment conflict
You experience a port assignment conflict. This problem might indicate that another application on the Remote Desktop server is using the same TCP port as the Remote Desktop Protocol (RDP). The default port assigned to RDP is 3389.
Symptom 3: Incorrectly configured authentication and encryption settings
After a Remote Desktop server client loses the connection to a Remote Desktop server, you experience one of the following symptoms:
- You cannot make a connection by using RDP.
- The session on the Remote Desktop server does not transition to a disconnected state. Instead, it remains active even though the client is physically disconnected from the Remote Desktop server.
If the client logs back in to the same Remote Desktop server, a new session may be established, and the original session may remain active.
Also, you receive one of the following error messages: Skyrim best house mod.
Error message 1
Because of a security error, the client could not connect to the Terminal server. After making sure that you are logged on to the network, try connecting to the server again.
Error message 2
Remote desktop disconnected. Because of a security error, the client could not connect to the remote computer. Verify that you are logged onto the network and then try connecting again.
Symptom 4: License certificate corruption
Remote Desktop Services clients are repeatedly denied access to the Remote Desktop server. If you are using a Remote Desktop Services client to log on to the Remote Desktop server, you may receive one of the following error messages.
Error message 1
Because of a security error, the client could not connect to the Terminal server. After making sure that you are logged on to the network, try connecting to the server again.
Error message 2
Remote desktop disconnected. Because of a security error, the client could not connect to the remote computer. Verify that you are logged onto the network and then try connecting again.
Error message 3
Because of a security error, the client could not connect to the Terminal server. After making sure that you are logged on to the network, try connecting to the server again.
Remote desktop disconnected. Because of a security error, the client could not connect to the remote computer. Verify that you are logged onto the network and then try connecting again.
Additionally, the following event ID messages may be logged in Event Viewer on the Remote Desktop server.
Event message 1
Event message 2
Event message 3
Event message 4
Event message 5
Resolution for Symptom 1
To resolve this problem, use the following methods, as appropriate.
Verify Remote Desktop is enabled
Open the System item in Control Panel. To start the System tool, click Start, click Control Panel, click System, and then click OK.
Under Control Panel Home, click Remote settings.
Click the Remote tab.
Under Remote Desktop, select either of the available options, depending on your security requirements:
Allow connections from computers from computers running any version of Remote Desktop (less secure)
Allow connections from computers only from computers running Remote Desktop with Network Level Authentication (more secure)
If you select Don't allow connections 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.
Verify Remote Desktop Services Limit number of connections policy
Start the Group Policy snap-in, and then open the Local Security Policy or the appropriate Group Policy.
Locate the following command:
Local Computer Policy > Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections Limit number of connections
Click Enabled.
In the RD Maximum Connections allowed box, type the maximum number of connections that you want to allow, and then click OK.
Verify Remote Desktop Services RDP-TCP properties
Follow these steps, depending on your operating system version.
Setting via Remote Desktop Services Configuration
Configure the number of simultaneous remote connections allowed for a connection:
On the RD Session Host server, open Remote Desktop Session Host Configuration. To open Remote Desktop Session Host Configuration, click Start, point to Administrative Tools, point to Remote Desktop Services.
Under Connections, right-click the name of the connection, and then click Properties. Fallout 4 eliza map.
On the Network Adapter tab, click Maximum connections, enter the number of simultaneous remote connections that you want to allow for the connection, and then click OK.
If the Maximum connections option is selected and dimmed, the Limit number of connections Group Policy setting has been enabled and has been applied to the RD Session Host server.
Verify Remote Desktop Services Logon rights
Configure the Remote Desktop Users Group.
The Remote Desktop Users group on an RD Session Host server grants users and groups permission to remotely connect to an RD Session Host server. You can add users and groups to the Remote Desktop Users group by using the following tools:
- Local Users and Groups snap-in
- The Remote tab in the System Properties dialog box on an RD Session Host server
- Active Directory Users and Computers snap-in, if the RD Session Host server is installed on a domain controller
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 an RD Session Host server.
Membership in the local Administrators group, or equivalent, on the RD Session Host server that you plan to configure, is the minimum required to complete this procedure.
Add users and groups to the Remote Desktop Users group by using the Remote tab
Start the System tool. To do this, click Start, click Control Panel, click the System icon, and then click OK.
Under Control Panel Home, click Remote settings.
On the Remote tab in the System Properties dialog box, click Select Users. Add the users or groups that have to connect to the RD Session Host server by using Remote Desktop.
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.
Add users and groups to the Remote Desktop Users group by using Local Users and Groups snap-in
- Click Start, click Administrative Tools, and then click Computer Management.
- In the console tree, click the Local Users and Groups node.
- In the details pane, double-click the Groups folder.
- Double-click Remote Desktop Users, and then click Add.
- In the Select Users dialog box, click Locations to specify the search location.
- Click Object Types to specify the types of objects that you want to search for.
- In the Enter the object names to select (examples) box, type the name you want to add.
- Click Check Names.
- When the name is located, click OK.
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).
- You can't use Remote Desktop Connection to connect to a computer using Windows 7 Starter, Windows 7 Home Basic, or Windows 7 Home Premium.
- Members of the local Administrators group can connect even if they are not listed.
Resolution for Symptom 2
Important
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, seeHow to back up and restore the registry in Windows.
To resolve this problem, 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 changing the registry. After you change the registry, you must restart the Remote Desktop Services service. After you restart the Remote Desktop Services service, you should verify that the RDP port has been changed correctly.
Remote Desktop server listener availability
The listener component runs on the Remote Desktop 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 Remote Desktop server. There is a listener for each Remote Desktop Services connection that exists on the Remote Desktop server. Connections can be created and configured by using the Remote Desktop Services Configuration tool.
To perform these tasks, refer to the following sections.
Determine which application is using the same port as RDP
You can run the netstat tool to determine whether port 3389 (or the assigned RDP port) is being used by another application on the Remote Desktop server:
- On the Remote Desktop server, click Start, click Run, type cmd, and then click OK.
- At the command prompt, type
netstat -a -oand then press Enter. - Look for an entry for TCP port 3389 (or the assigned RDP port) with a status of Listening. This indicates another application is using this port. The PID (Process Identifier) of the process or service using that port appears under the PID column.
To determine which application is using port 3389 (or the assigned RDP port), use the tasklist command-line tool along with the PID information from the netstat tool:
- On the Remote Desktop server, click Start, click Run, type cmd, and then click OK.
- Type
tasklist /svcand then press Enter. - 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. If you cannot change the application's port, you must change the port that is assigned to RDP.
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. To open Registry Editor, click Start, click Run, type regedit, and then click OK.
If the User Account Control dialog box appears, verify that the action it displays is what you want, and then click Continue.
Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlRemote Desktop serverWinStations
RDP-TCP is the default connection name. To change the port for a specific connection on the Remote Desktop server, select the connection under the WinStations key:
- In the details pane, double-click the PortNumber registry entry.
- Type the port number that you want to assign to RDP.
- Click OK to save the change, and then close Registry Editor.
Restart the Remote Desktop Services service
For the RDP port assignment change to take effect, stop and start the Remote Desktop Services service. To do this, you must be a member of the local Administrators group, or you must have been granted the appropriate permissions.
To stop and start the Remote Desktop Services service, follow these steps:
On the Remote Desktop server, open the Services snap-in. To do this, click Start, point to Administrative Tools, and then click Services.
If the User Account Control dialog box appears, verify that the action it displays is what you want, and then click Continue.
In the Services pane, right-click Remote Desktop Services, and then click Restart.
If you are prompted to restart other services, click Yes.
Verify that the Status column for the Remote Desktop Services service displays a Started status.
Verify that the RDP port has changed
To verify that the RDP port assignment has been changed, use the netstat tool:
On the Remote Desktop server, click Start, click Run, type cmd, and then click OK.
At the command prompt, type
netstat -athen press Enter.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.
Important
Remote Desktop Connection and the Terminal server Web Client use port 3389, by default, to connect to a Remote Desktop server. If you change the RDP port on the Remote Desktop server, you will have to modify the port used by Remote Desktop Connection and the Remote Desktop server Web Client. For more information, see Change the listening port for Remote Desktop on your computer.
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.
Note
RDP-TCP is the default connection name and 3389 is the default RDP port. Use the connection name and port number specific to your Remote Desktop server configuration.
Windows Remote Desktop Disconnects After A Few Seconds
Method 1
Use an RDP client, such as Remote Desktop Connection, to establish a remote connection to the Remote Desktop server. How to add new mouth shapes in papagayo for mac.
Method 2
Use the qwinsta tool to view the listener status on the Remote Desktop server:
- On the Remote Desktop server, click Start, click Run, type cmd, and then click OK.
- At the command prompt, type qwinsta, and then press Enter.
- The RDP-TCP session state should be Listen.
Method 3
Use the netstat tool to view the listener status on the Remote Desktop server:
- On the Remote Desktop server, click Start, click Run, type cmd, and then click OK.
- At the command prompt, type
netstat -athen press Enter. - The entry for TCP port 3389 should be Listening.
Method 4
Use the telnet tool to connect to the RDP port 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> 3389, 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 3389: Connect failed
The qwinsta, netstat, and telnet tools are also included in Windows XP and Windows Server 2003. You can also download and use other troubleshooting tools, such as Portqry.
Resolution for Symptom 3
To resolve the issue, configure authentication and encryption.
To configure authentication and encryption for a connection, follow these steps:
On the RD Session Host server, open Remote Desktop Session Host Configuration. To open Remote Desktop Session Host Configuration, click Start, point to Administrative Tools, point to Remote Desktop Services, and then click Remote Desktop Session Host Configuration.
Under Connections, right-click the name of the connection, and then click Properties.
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. You can select Low, Client Compatible, High, or FIPS Compliant. See Step 4 above for Windows Server 2003 for Security layer and Encryption level options.
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.
- To open Remote Desktop Services Configuration, click Start, click Control Panel, double-click Administrative Tools, and then double-click Remote Desktop Services Configuration.
- 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 FIPS compliant setting (the System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing setting in Group Policy or the FIPS Compliant setting in Remote Desktop server Configuration) encrypts and decrypts data sent from the client to the server and from the server to the client, with the Federal Information Processing Standard (FIPS) 140-1 encryption algorithms, using Microsoft cryptographic modules. For more information, see Terminal Services in Windows Server 2003 Technical Reference.
- The High setting encrypts data sent from the client to the server and from the server to the client by using strong 128-bit encryption.
- The Client Compatible setting encrypts data sent between the client and the server at the maximum key strength supported by the client.
- The Low setting encrypts data sent from the client to the server using 56-bit encryption.
Additional troubleshooting step: Enable CAPI2 event logs
To help troubleshoot this problem, enable CAPI2 event logs on both the client and server computers. This command is shown in the following screenshot.
Workaround for the issue (You cannot completely disconnect a Remote Desktop server connection) described in Symptom 3
To work around this problem, follow these steps:
- Click Start, click Run, type gpedit.msc, and then click OK.
- Expand Computer Configuration, expand Administrative Templates, expand Windows Components, expand Remote Desktop Services, expand Remote Desktop Session Host, and then click Connections.
- In the right pane, double-click Configure keep-alive connection interval.
- Click Enabled, and then click OK.
- Close Group Policy Object Editor, click OK, and then quit Active Directory Users and Computers.
Resolution for Symptom 4
Important
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, see 322756 How to back up and restore the registry in Windows.
To resolve this problem, back up and then remove the X509 Certificate registry keys, restart the computer, and then reactivate the Remote Desktop Services Licensing server. To do this, follow these steps.
Note
Perform the following procedure on each of the Remote Desktop servers.
Make sure that the Remote Desktop server registry has been successfully backed up.
Start Registry Editor.
Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlTerminal ServerRCMOn the Registry menu, click Export Registry File.
Type exported- Certificate in the File name box, and then click *Save.
Note
If you have to restore this registry subkey in the future, double-click the Exported-parameters.reg file that you saved in this step.
Right-click each of the following values, click Delete, and then click Yes to verify the deletion:
- Certificate
- X509 Certificate
- X509 Certificate ID
- X509 Certificate2
Exit Registry Editor, and then restart the server.
References
For more information about Remote Desktop Gateway, see the following articles:
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.
| Information in this topic applies to desktop and web applications. |
When using Remote Desktop to connect to a remote computer, closing Remote Desktop locks out the computer and displays the login screen. In the locked mode, the computer does not have GUI, so any currently running or scheduled GUI tests will fail.
To avoid problems with GUI tests, use the tscon utility to disconnect from Remote Desktop. tscon returns the control to the original local session on the remote computer, bypassing the logon screen. All programs on the remote computer continue running normally, including GUI tests.
Disconnect Manually
To disconnect from Remote Desktop, run the following command on the remote computer (in the Remote Desktop Connection window) as an Administrator, for example, via the command line:
%windir%System32tscon.exe RDP-Tcp#NNN /dest:console
where RDP-Tcp#NNN is the ID of your current Remote Desktop session, for example, RDP-Tcp#5. You can see it in the Windows Task Manager on the Users tab, in the Session column.
| Note: | The Session column is hidden by default. To show it, right-click somewhere within the row that displays CPU, Memory, and so on, then choose Session in the opened context menu. |
You will see the Your Remote Desktop Services session has ended message, and the Remote Desktop client will close. But all programs and tests on the remote computer will continue running normally.
Disconnect via a Batch File
Microsoft Remote Desktop App
You can automate the disconnection procedure using a batch file. On the remote computer, do the following:
Microsoft Rewards
Create a batch file with this code:
for /f 'skip=1 tokens=3' %%s in ('query user %USERNAME%') do (
%windir%System32tscon.exe %%s /dest:console
)Create a desktop shortcut to this file. To do this, right-click the batch file and select Send to > Desktop (create shortcut).
In the shortcut properties, click Advanced and select Run as administrator.
Double-click this shortcut on the remote computer (in the Remote Desktop Connection window) or call this batch file at the beginning of your tests (provided that the tests are run as an Administrator).
Important Notes
tscon leaves the remote computer unlocked, which can reduce the system security. You can lock the computer after the test run is over using the following command:
Do not lock the remote computer while your automated tests are still running. If the tests need to interact with the GUI, they will fail since the operating system will stop drawing the GUI. For more information about this, see Running Tests on Locked Computers. If the rdpclip.exe process is running on the remote computer and the clipboard is not empty when you disconnect from the remote session, the rdpclip.exe process can fail.
To avoid this issue, you can terminate the rdpclip.exe process before disconnecting from the session.
See Also
Running Tests via Remote Desktop
About Running Tests via Remote Desktop
Running Tests in Minimized Remote Desktop Windows
Running Tests on Locked Computers