Remote Desktop Can't Connect to the Remote Computer
The client got no answer. Check, in this order:
- The server is running, and you are using the IP address shown in your dashboard.
- The firewall on your server's page in the dashboard allows TCP 3389 from your current address. Home addresses change, so compare with the address the firewall card shows for you.
- Windows Firewall inside the server allows Remote Desktop from your address.
- The network you are on allows outgoing connections to port 3389. Some office and public networks block it.
From Windows PowerShell on your own computer:
Test-NetConnection 203.0.113.10 -Port 3389
TcpTestSucceeded : True means the port is reachable, and the problem is past the network.
Your Credentials Did Not Work
- Type the username as
.\Administrator. The.\tells the client it is an account on the server itself, not on your own computer or a domain. - Check Caps Lock and the keyboard layout, especially if the password has symbols.
- The account may be locked after too many failed attempts, by you or by bots. Sign in through the browser console instead, and restrict Remote Desktop to your address so bots stop trying.
An Authentication Error Has Occurred (CredSSP)
The full message mentions CredSSP encryption oracle remediation. Your computer and the server disagree about a security update for the sign-in protocol, usually because the server has not been updated. Sign in through the browser console, install all Windows updates on the server, and restart it. Do not weaken the policy on your own computer to get around it.
An Internal Error Has Occurred
The connection reached the server but the session could not start. Restarting the Remote Desktop service fixes it more often than not. In the browser console, open PowerShell as administrator:
Restart-Service TermService -Force
If it keeps happening, restart the server, then install pending updates. On the client side, try turning off Persistent bitmap caching under Show Options → Experience.
A Black Screen After Signing In
Wait a minute first: the first sign-in after an update can take a while to build the desktop. Then press Ctrl+Alt+End and choose Task Manager; from there, File → Run new task → explorer.exe brings the desktop back. If it happens every time, turn off Persistent bitmap caching in the client, or disconnect and reconnect at a lower resolution.
The Remote Session Was Disconnected Because There Are No Licence Servers
This only appears when the Remote Desktop Session Host role has been installed and its 120-day grace period has ended. If you only need up to two administrators at once, remove the role in Server Manager and restart; Windows then allows two administrative sessions without licences. If you need more users, buy Remote Desktop licences and set up a licence server.
Keep It Working
Install updates monthly, keep Remote Desktop limited to your own addresses, and set an account lockout policy. Connecting to a Windows VPS walks through each of these.