What are the troubleshooting you perform for RDP issues?
Skip to main content This browser is no longer supported. Show
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. General Remote Desktop connection troubleshooting
In this articleTry our Virtual Agent - It can help you quickly identify and fix common RD Sessions connectivity issues Use these steps when a Remote Desktop client can't connect to a remote desktop but doesn't provide messages or other symptoms that would help identify the cause. Check the status of the RDP protocolCheck the status of the RDP protocol on a local computerTo check and change the status of the RDP protocol on a local computer, see How to enable Remote Desktop. Check the status of the RDP protocol on a remote computerImportant Follow this section's instructions carefully. Serious problems can occur if the registry is modified incorrectly. Before you start modifying the registry, back up the registry so you can restore it in case something goes wrong. To check and change the status of the RDP protocol on a remote computer, use a network registry connection:
Check whether a Group Policy Object (GPO) is blocking RDP on a local computerIf you can't turn on RDP in the user interface or the value of fDenyTSConnections reverts to 1 after you've changed it, a GPO may be overriding the computer-level settings. To check the group policy configuration on a local computer, open a Command Prompt window as an administrator, and enter the following command:
After this command finishes, open gpresult.html. In Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Connections, find the Allow users to connect remotely by using Remote Desktop Services policy.
Check whether a GPO is blocking RDP on a remote computerTo check the Group Policy configuration on a remote computer, the command is almost the same as for a local computer:
The file that this command produces (gpresult- Modifying a blocking GPOYou can modify these settings in the Group Policy Object Editor (GPE) and Group Policy Management Console (GPM). For more information about how to use Group Policy, see Advanced Group Policy Management. To modify the blocking policy, use one of the following methods:
Check the status of the RDP servicesOn both the local (client) computer and the remote (target) computer, the following services should be running:
You can use the Services MMC snap-in to manage the services locally or remotely. You can also use PowerShell to manage the services locally or remotely (if the remote computer is configured to accept remote PowerShell cmdlets). On either computer, if one or both services are not running, start them. Note If you start the Remote Desktop Services service, click Yes to automatically restart the Remote Desktop Services UserMode Port Redirector service. Check that the RDP listener is functioningImportant 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. Check the status of the RDP listenerFor this procedure, use a PowerShell instance that has administrative permissions. For a local computer, you can also use a command prompt that has administrative permissions. However, this procedure uses PowerShell because the same cmdlets work both locally and remotely.
Check the status of the RDP self-signed certificate
Check the permissions of the MachineKeys folder
Check the RDP listener portOn both the local (client) computer and the remote (target) computer, the RDP listener should be listening on port 3389. No other applications should be using this port. Important 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 check or change the RDP port, use the Registry Editor:
Check that another application isn't trying to use the same portFor this procedure, use a PowerShell instance that has administrative permissions. For a local computer, you can also use a command prompt that has administrative permissions. However, this procedure uses PowerShell because the same cmdlets work locally and remotely.
Check whether a firewall is blocking the RDP portUse the psping tool to test whether you can reach the affected computer by using port 3389.
FeedbackSubmit and view feedback for What are RDP issues?RDP connectivity can sometimes fail due to issues with the Credential Security Support Provider (CredSSP) protocol. The CredSSP provides a means of sending user credentials from a client computer to a host computer when an RDP session is in use. In 2018, Microsoft updated the CredSSP to fix a security vulnerability.
What is remote troubleshoot?Remote Troubleshooting means Sangoma support technicians or engineers using electronic methods to securely log into and attempt to identify and resolve issues.
|