> ## Documentation Index
> Fetch the complete documentation index at: https://help.freakhosting.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Fix "Remote Desktop Can't Connect to the Remote Computer"

> Remote Desktop can't connect to the remote computer? Check the server is running, the IP and port, the RDP firewall rule, the listener and the TermService service.

When Remote Desktop shows "Remote Desktop can't connect to the remote computer", the server is usually off or still restarting, you are using the wrong IP or port, or the **Remote Desktop** firewall rule or service is disabled. Sign in through the [VNC console](https://help.freakhosting.com/portals/vps-panel/how-to-enable-and-use-vnc-console-access.md), run `qwinsta` to check that `rdp-tcp` shows `Listen`, and enable the firewall rule with `Get-NetFirewallRule -DisplayGroup "Remote Desktop" | Set-NetFirewallRule -Enabled True`.

The full error reads:

```text theme={null}
Remote Desktop can't connect to the remote computer for one of these reasons:
1) Remote access to the server is not enabled
2) The remote computer is turned off
3) The remote computer is not available on the network
Make sure the remote computer is turned on and connected to the network, and that remote access is enabled.
```

| Difficulty | Time | Works on | Needs |
| - | - | - | - |
| Beginner to intermediate | 5 to 20 minutes | Windows Server 2019 / 2022 / 2025 | Console access, Administrator password |

## Before you start

* You need a way in that doesn't use RDP. On a VPS, open the [VNC console](https://help.freakhosting.com/portals/vps-panel/how-to-enable-and-use-vnc-console-access.md). On a dedicated server, [open a ticket](https://freakhosting.com/clientarea/submitticket.php) if you have no console access.
* Run the PowerShell commands below in **PowerShell as Administrator** on the server.

## Cause 1: the server is off, restarting or installing updates

**Check:** look at the server in the [VNC console](https://help.freakhosting.com/portals/vps-panel/how-to-enable-and-use-vnc-console-access.md). If you see "Working on updates" or a boot screen, Windows isn't ready for RDP yet. A new Windows VPS also needs several minutes after installation.

**Fix:** wait for the sign-in screen. If the server is off, [start it](https://help.freakhosting.com/portals/vps-panel/how-to-start-stop-restart-and-power-off-your-vps.md). If it never reaches the sign-in screen, see [Windows Server not booting](https://help.freakhosting.com/portals/other/how-to-fix-windows-server-not-booting.md).

## Cause 2: wrong IP address or port

**Check:** compare the address in **Remote Desktop Connection** with the IP on your [server page](https://help.freakhosting.com/portals/vps-panel/a-tour-of-your-server-page.md). If you [changed the RDP port](https://help.freakhosting.com/portals/other/how-to-change-the-rdp-port-on-windows-server.md), check the port the server listens on:

```powershell theme={null}
Get-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp' -Name PortNumber
```

**Fix:** connect with the port after a colon, for example `203.0.113.10:3390`. The default is `3389`.

## Cause 3: the Windows Firewall blocks Remote Desktop

**Check:** from your own Windows PC, test the port:

```powershell theme={null}
Test-NetConnection -ComputerName 203.0.113.10 -Port 3389 -InformationLevel Detailed
```

`TcpTestSucceeded : True` means the port is reachable. `False` means something blocks it.

**Fix:** on the server, enable the built-in rules:

```powershell theme={null}
Get-NetFirewallRule -DisplayGroup "Remote Desktop" | Set-NetFirewallRule -Enabled True
```

In the GUI, open `wf.msc` and enable **Remote Desktop - User Mode (TCP-In)** and **Remote Desktop - User Mode (UDP-In)** under **Inbound Rules**. If you use a custom port, allow it too: see [open a port in Windows Firewall](https://help.freakhosting.com/portals/other/how-to-open-a-port-in-windows-firewall.md). Also check any rules you added in the [FREAKHOSTING firewall panel](https://help.freakhosting.com/portals/firewall/firewall-panel-overview.md).

> [!WARNING]
>
> Don't switch the Windows Firewall off to "test". It exposes every service on the server to the internet. Enable the specific rule instead.

## Cause 4: Remote Desktop is disabled

**Check:** open **Server Manager > Local Server** and look at the value next to **Remote Desktop**.

**Fix:** click it and select **Allow remote connections to this computer**, or run `SConfig`, choose **7** and then **E**. In the registry the setting is `fDenyTSConnections` under `HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server`: `0` means enabled, `1` means disabled. If Group Policy sets it, run `gpresult /H C:\gpresult.html` and check **Allow users to connect remotely by using Remote Desktop Services** under **Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections**.

## Cause 5: the RDP service or listener isn't running

**Check:**

```powershell theme={null}
Get-Service TermService, UmRdpService
qwinsta
```

A working server shows both services as `Running` and a line like:

```text theme={null}
 rdp-tcp                                 65536  Listen
```

**Fix:** start the services, then test again:

```powershell theme={null}
Start-Service TermService, UmRdpService
```

Next, check that nothing else uses the port. The PID from both commands must match:

```powershell theme={null}
tasklist /svc | findstr TermService
netstat -anob | findstr 3389
```

If another program holds port `3389`, stop or reconfigure it and restart `TermService`. To test RDP on the server itself, run `mstsc /v:localhost` in the console session: if that works too, the problem is on the network path, not in Windows.

## Cause 6: a broken RDP certificate

**Check:** RDP still fails although the listener shows `Listen` and the port is reachable.

**Fix:** Microsoft's guidance is to open the **Certificates** snap-in (`mmc`, **Computer account**), delete the self-signed certificate under **Remote Desktop > Certificates**, and restart **Remote Desktop Services**. Windows creates a new one.

## Frequently asked questions

### RDP worked yesterday. What changed?

Usually a restart for updates, a firewall change or a new RDP port. Check the server in the VNC console first, then work through causes 2 to 4.

### Can my account be locked instead?

Yes. A locked account shows a different message, not this one. See [the user account has been locked out](https://help.freakhosting.com/portals/other/how-to-fix-the-user-account-has-been-locked-out.md).

### I get an "authentication error" with CredSSP. Is that the same problem?

No. The connection reaches the server, but authentication fails. See [fix the CredSSP encryption oracle remediation error](https://help.freakhosting.com/portals/other/how-to-fix-credssp-encryption-oracle-remediation-error.md).

### Can I use a different port than 3389?

Yes. Change it on the server and allow it in the firewall first. See [change the RDP port](https://help.freakhosting.com/portals/other/how-to-change-the-rdp-port-on-windows-server.md).

## Related guides

> [card] [VPS and dedicated server guides](https://help.freakhosting.com/portals/other/vps-and-dedicated-server-guides.md)
>
> Every guide in this section.

> [card] [Connect with Remote Desktop](https://help.freakhosting.com/portals/other/how-to-connect-to-windows-server-with-remote-desktop.md)
>
> Connect step by step with mstsc.

> [card] [Open a port in Windows Firewall](https://help.freakhosting.com/portals/other/how-to-open-a-port-in-windows-firewall.md)
>
> Allow RDP or a custom port.

> [card] [Change the RDP port](https://help.freakhosting.com/portals/other/how-to-change-the-rdp-port-on-windows-server.md)
>
> Move RDP off 3389 safely.

> [card] [Account locked out](https://help.freakhosting.com/portals/other/how-to-fix-the-user-account-has-been-locked-out.md)
>
> Unlock an account after failed logins.

> [card] [VNC console](https://help.freakhosting.com/portals/vps-panel/how-to-enable-and-use-vnc-console-access.md)
>
> Reach your VPS without RDP.

***

> [!NOTE]
>
> **Checked against [Microsoft Learn: Remote Desktop can't connect to the remote computer](https://learn.microsoft.com/en-us/troubleshoot/windows-server/remote/remote-desktop-cannot-connect-remote-computer) and [General Remote Desktop connection troubleshooting](https://learn.microsoft.com/en-US/windows-server/remote/remote-desktop-services/troubleshoot/rdp-error-general-troubleshooting)** on 4 November 2026. Steps were not tested on a live Windows server for this page; menu names can differ slightly between Windows Server 2019, 2022 and 2025.

> [!NOTE]
>
> ### Need Extra Help?
>
> If you encounter any issues, our support team is ready to assist:
>
> * **Live Chat:** Quick assistance via our website.
> * **Support Ticket:** [Open a Ticket](https://freakhosting.com/clientarea/submitticket.php)
> * **Discord:** [Join our Community](https://discord.gg/freakhosting)
> * **Email:** [support@freakhosting.com](mailto:support@freakhosting.com)

> [!TIP]
>
> ### Save on Your Hosting
>
> Ready to upgrade your hosting? Use code **KB20** at checkout for **20% off** your first order!

***

**Last Updated:** November 2026


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.