I can access to this computer remotly thorugh a VPN, so I would like to know if there is any way to restore this image remotely, while I am connecting through my VPN. In ohter words, I would like to know if I can restore a Windows image backup from Windows, without the need to restart the computer in rapair mode with the recovery disk.
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.
Original product version: 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:
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:
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.
Additionally, the following event ID messages may be logged in Event Viewer on the Remote Desktop server.
Resolution for Symptom 1
To resolve this problem, use the following methods, as appropriate.
Verify Remote Desktop is enabled
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
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:
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:
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
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
Note
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:
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:
Screens 4 5 1 – Access Your Computer Remotely Backup Software
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:
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:
![]()
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:
Verify that the RDP port has changed
To verify that the RDP port assignment has been changed, use the netstat tool:
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.
Resolution for Symptom 3
To resolve the issue, configure authentication and encryption.
To configure authentication and encryption for a connection, follow these steps:
Note
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:
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.
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.
Use our home office solution-Click here to learn more
Connect to a computer remotely, be it from the other end of the office or halfway around the world. AnyDesk ensures secure and reliable remote desktop connections for IT professionals and on-the-go individuals alike.
400+ million sessions per monthMulti-platform support
AnyDesk works across all your devices and operating systems: Windows, macOS, iOS, Android, Linux, FreeBSD and even your Raspberry Pi!
Online collaboration
Collaborate and communicate with ease, whether you’re holding online meetings and presentations or working on the same document from the other side of the world.
Built-in file transfer
Simply copy and paste or use the new transfer tab to transfer files between computers.
Screens 4 5 1 – Access Your Computer Remotely Backup Hard DriveLightweight
No administrative privileges or installation needed. Simply download the 3MB file and you’re off. Require unattended access to your computer when you’re on the road? No problem, you’ll just need to install and set a password.
Make it yours
Customize the AnyDesk user interface to give customers a remote desktop experience consistent with your brand.
Record sessions
Both the IT professional and the user whose computer they access can get a recording of each session. This adds an extra level of security and is handy for training purposes too.
Own network
No cloud, no problem. If you need full control of your data, setting up your own Enterprise Network is easy. Unencrypted data will never leave your DMZ.
Unparalleled performance
Low latency, fast data transmissions, frame rates of 60 fps – we know how critical these are when working on a remote desktop. That’s why our innovative DeskRT codec ensures low lag, even at high screen resolutions or bandwidths of just 100 kB/s.
Secure by design
Your security has been built into AnyDesk from day one. We use banking-standard TLS 1.2 technology to ensure your computer is protected from unauthorized access and RSA 2048 asymmetric encryption to verify every connection. Plus, our servers use Erlang telecommunication technology for maximum reliability.
Screens 4 5 1 – Access Your Computer Remotely Backup PasswordBuilt for pros, loved by all
AnyDesk has been designed and developed with IT professionals in mind, offering an unbeatable service for those who need fast, efficient and reliable remote access. AnyDesk is also a practical – and totally free – solution for private users.
Grows with you
As teams grow, their needs evolve – and so should the software they use. AnyDesk lets you start small and scale quickly, with sensible pricing for teams of all sizes.
Jan Peters
CEO, Spidercam
spidercam® Producer uses AnyDesk Remote Desktop Tool for Worldwide Equipment Support.
Francisco Rodríguez
CIO, Airport Münster/Osnabrück
It wasn't until we tried AnyDesk that we were able to solve the data security problem.
Mario Dionies
IT-Security Officer, AIP
After searching for a bit, we found AnyDesk with its in-house-solution, offering exactly what we were looking for.
AnyDesk is free for evaluation and private use. Try today!Download Now
No signup required.
By downloading and using AnyDesk, you accept our license agreement and our privacy statement.
Please consider taking our survey to help us make AnyDesk even better!
If the download does not start automatically, please click the Download link below.
Get Started with AnyDesk in 3 steps:
Double-click the downloaded AnyDesk file and AnyDesk will start immediately.
Enter the ID or Alias of the remote device into the field under 'Remote Desk'.
Click the green 'Connect'-Button and enjoy our fast and simple remote software solution.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |