About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
Remote Desktop Connection gives up with:
Remote Desktop can't connect to the remote computer for one of these reasons:
- Remote access to the server is not enabled
- The remote computer is turned off
- The remote computer is not available on the network
or the shorter "This computer can't connect to the remote computer." Neither tells you which of the three it is.
Microsoft's troubleshooting page for these messages says there are several possible root causes, and the main ones are the RDP listener not working and incorrect network configuration (Microsoft Learn, Remote Desktop can't connect to the remote computer). The steps below follow its order, starting on the server and working outwards, so each check rules out one layer.
What you see
- One of the two messages above, before or after you enter credentials.
- Microsoft's page covers direct RDP connections, with no Remote Desktop Gateway involved.
Why it happens
From Microsoft's page, in the order it checks them:
- The server is not running, or not responding.
- The RDP listener is not working. Remote Desktop is turned off (
fDenyTSConnectionsset to 1, by the server's own setting or by Group Policy), the listener is disabled, a Remote Desktop service is stopped, or the machine is still in a Sysprep state. - The network path is blocked. A firewall rule, a changed RDP port, a name that resolves to the wrong address, or antivirus software.
- Something on the server takes the port or breaks the session. Another process listening on port 3389, a self-signed certificate that cannot be re-created, or Remote Desktop Services roles installed that the server does not need.
How to prove the cause
1. Is the server running? Check it is on and responding at its console: Microsoft's examples are iLO for a physical server and the Hyper-V console for a virtual machine. If you cannot get it running, or the console itself fails, that is the problem to fix first.
2. Is the listener up? At the server's console, run:
qwinsta
Microsoft's example output includes a line rdp-tcp 65536 Listen. If rdp-tcp is in the Listen state, the listener is running; go to step 3. If not, go to The listener is not running in the fix.
3. Server or network? At the console, run mstsc and connect to localhost.
- Fails at the console too: the problem is on the server. Go to step 5.
- Works at the console: the problem is probably in the network. Go to step 4.
Microsoft notes this test is not always possible, for example on Azure virtual machines; then use step 4 directly.
4. Can the client reach the port? From a computer on the same network as the server, in an elevated PowerShell:
Test-NetConnection -ComputerName <server name> -port 3389 -InformationLevel Detailed
TcpTestSucceeded : True means no connectivity problem; go to step 5. False means something is blocking the path; go to The network path is blocked in the fix. Also try connecting by IP address: Microsoft says if the IP works and the name does not, the issue is likely name resolution.
5. Is Remote Desktop Services the process on the port? On the server, in an elevated prompt:
tasklist /svc | findstr TermService
netstat -anob | findstr 3389
The process ID (PID) shown for TermService should match the PID listening on port 3389. Microsoft's example shows svchost.exe 820 TermService and port 3389 listening under PID 820.
The fix
The listener is not running
From Microsoft's page:
Remote Desktop turned on.
fDenyTSConnectionsmust be 0 underHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server, and also underHKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Servicesif a policy sets it. Microsoft says policies override the default and should be changed withgpedit.mscorgpmc.msc. Its general troubleshooting page adds that if the value goes back to 1 after you change it, a Group Policy Object is overriding it;gpresult /H c:\gpresult.htmlshows the winning GPO for Allow users to connect remotely by using Remote Desktop Services (Microsoft Learn, General Remote Desktop connection troubleshooting).Listener enabled.
fEnableWinStationis 1 underHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\Winstations\RDP-Tcp.Services running. Remote Desktop Services (TermService) and Remote Desktop Services UserMode Port Redirector (UmRdpService).
Not stuck in Sysprep. Under
HKEY_LOCAL_MACHINE\SYSTEM\Setup,SystemSetupInProgressandOOBEInProgressare both 0.Permissions. Microsoft's page includes a step to add Network Service to the local Administrators group and restart TermService:
Add-LocalGroupMember -Group Administrators -Member "Network Service"This gives a built-in service account administrator rights on the server. That is a significant change; record it, and remove the membership again if it does not fix the fault.
Replace the listener settings. As a last step, export
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcpfrom a working server on the same Windows version, back up the affected server's key, then replace it. Microsoft notes that RDP does not work while that key is deleted, so do this from the console.
The network path is blocked
Port.
PortNumberunder the RDP-Tcp key should be0x00000d3d(3389). If it is different, connect withservername:port. Microsoft does not recommend running RDP on another port.Name resolution. If the IP address works and the name does not, fix the DNS record or the client's DNS settings.
Windows Firewall. In
wf.msc, under Inbound Rules, Remote Desktop - User Mode (TCP-In) and Remote Desktop - User Mode (UDP-In) should be enabled for all profiles. Microsoft's PowerShell equivalent:Get-NetFirewallRule -DisplayGroup "Remote Desktop" | Set-NetFirewallRule -Enabled TrueMicrosoft also shows turning the firewall off for all profiles to rule it out (
Set-NetFirewallProfile -Profile Domain,Public,Private -Enabled False). If you use that test, turn it back on straight after.Other devices. Microsoft says other network elements restricting traffic should be checked. Its general page suggests testing from several computers with
pspingto see whether the server is blocked from all of them or only some.Antivirus. Microsoft notes antivirus can affect RDP connections; disable the service to test, or uninstall it and restart to rule it out completely.
The listener and network are fine, but it still fails
- Another process on port 3389. If the PIDs in step 5 do not match, find and stop that process, then restart TermService.
- Self-signed certificate. In the Certificates snap-in for the computer account, delete the certificate under Remote Desktop > Certificates, restart Remote Desktop Services and refresh. If it does not come back, follow the certificate checks (services, registry values and MachineKeys permissions) on Microsoft's "An internal error has occurred" page (Microsoft Learn).
- Unneeded RDS roles. In Server Manager, check whether Remote Desktop Services roles are installed that the server does not need (Microsoft's example is the Connection Broker role), remove them and restart. On a server that does run the Connection Broker role, Microsoft says the Remote Desktop Connection Broker service (TSSDis) must be running, and the local RDS Endpoint Servers group must contain NT AUTHORITY\NETWORK SERVICE.
How to confirm the fix
qwinstashowsrdp-tcpinListen.Test-NetConnection … -port 3389showsTcpTestSucceeded : Truefrom the client's network.- The PID listening on 3389 is TermService's.
- The connection works by name from a normal client computer.
What to watch afterwards
- Group Policy that turns Remote Desktop off, which Microsoft names as a reason the setting changes back.
- Temporary tests left in place. Firewall turned off, antivirus disabled, Network Service in Administrators: undo each one you used.
- New software that listens on 3389, which Microsoft lists as a cause.
Read next
Related articles you may want next.
- TroubleshootingFirewall Rules Stopped After a Move? Check the ProfileServices refused after a Windows server move? Read each connection's network category, trace why domain detection failed and fix that, not the rules.Read article
- HostingRemote Desktop Licensing Errors: Grace Period and CAL ModeWhy RDS users see 'no Remote Desktop License Servers available' or a mode warning, and how to check licence server, mode and CAL version read-only.Read article
- TroubleshootingRemote Desktop "An internal error has occurred": certificate, security layer and service checksA direct Remote Desktop connection fails with "An internal error has occurred" before or after you enter credentials. Rule out the network, test the security negotiation, then check the server's Remote Desktop certificate, key permissions and listener.Read article
Risks and limits
- Several of Microsoft's tests lower security while they run: turning off the firewall, disabling antivirus, adding Network Service to Administrators. Use them briefly, from the console, and reverse them.
- Replacing the RDP-Tcp key cuts off RDP until the new key is in place.
- Removing Remote Desktop Services roles from a server that does need them breaks that deployment. Check what the server is for first.
- This article covers direct connections. A Remote Desktop Gateway, CredSSP update mismatch or licensing fault shows different messages and has its own checks.
Sources
- Microsoft Learn, "Remote Desktop can't connect to the remote computer", last updated 12 February 2026: https://learn.microsoft.com/en-us/troubleshoot/windows-server/remote/remote-desktop-cannot-connect-remote-computer
- Microsoft Learn, "General Remote Desktop connection troubleshooting", last updated 12 February 2026: https://learn.microsoft.com/en-us/troubleshoot/windows-server/remote/rdp-error-general-troubleshooting
- Microsoft Learn, "'An internal error has occurred' when connecting to a remote machine", last updated 12 February 2026: https://learn.microsoft.com/en-us/troubleshoot/windows-server/remote/internal-error-has-occurred-connecting-remote-machine
Next step
Working from the listener outwards turns a vague message into one layer to fix. NetLeverage has looked after business servers since 2002. If Remote Desktop still can't reach your server, talk to us through managed support with the qwinsta output and the Test-NetConnection result.
This article was originally published on .