Skip to main content
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, 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:

​
Before you start

  • You need a way in that doesn’t use RDP. On a VPS, open the VNC console. On a dedicated server, open a ticket 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. 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. If it never reaches the sign-in screen, see Windows Server not booting.

​
Cause 2: wrong IP address or port

Check: compare the address in Remote Desktop Connection with the IP on your server page. If you changed the RDP port, check the port the server listens on:
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:
TcpTestSucceeded : True means the port is reachable. False means something blocks it. Fix: on the server, enable the built-in rules:
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. Also check any rules you added in the FREAKHOSTING firewall panel.
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:
A working server shows both services as Running and a line like:
Fix: start the services, then test again:
Next, check that nothing else uses the port. The PID from both commands must match:
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.

​
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.

​
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.

VPS and dedicated server guides

Every guide in this section.

Connect with Remote Desktop

Connect step by step with mstsc.

Open a port in Windows Firewall

Allow RDP or a custom port.

Change the RDP port

Move RDP off 3389 safely.

Account locked out

Unlock an account after failed logins.

VNC console

Reach your VPS without RDP.
Checked against Microsoft Learn: Remote Desktop can’t connect to the remote computer and General Remote Desktop connection 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.

​
Need Extra Help?

If you encounter any issues, our support team is ready to assist:

​
Save on Your Hosting

Ready to upgrade your hosting? Use code KB20 at checkout for 20% off your first order!
Last Updated: November 2026