Remote Desktop is usually reliable, but a handful of errors come up again and again on Windows VPS servers. This guide lists the common RDP errors with the quickest fix for each. Keep your provider's VNC/web console at hand: it works even when RDP does not.
Before you start
- The VPS IP, RDP port and an administrator account.
- Access to the provider console for server-side fixes.
"Remote Desktop can't connect to the remote computer"
- Check the VPS is running in your dashboard.
- Test the port from your computer:
Test-NetConnection 203.0.113.10 -Port 3389in PowerShell. - If it fails, log in via the console and check that Remote Desktop is enabled (
SystemPropertiesRemote) and the TermService service is running. - Check Windows Defender Firewall allows RDP from your current IP. If you restricted RDP to an IP that has since changed, update the rule.
- If you changed the RDP port, connect with
IP:port.
"An internal error has occurred"
- Restart the Remote Desktop Services:
Restart-Service TermService -Forcefrom the console (this disconnects active sessions). - On the client, clear saved credentials for the server and try again.
- Check the RDP certificate in
certlm.msc → Remote Desktop: if it expired or was deleted, restarting TermService recreates the self-signed one.
"An authentication error has occurred ... CredSSP encryption oracle remediation"
The client and server have mismatched security updates. Install the latest Windows updates on both sides; that is the proper fix. Avoid lowering the CredSSP policy permanently.
"The remote session was disconnected because there are no Remote Desktop License Servers available"
Someone installed the Remote Desktop Session Host role, which needs RDS licences after a 120-day grace period. If you only need administrative access (up to two sessions), remove the role:
Uninstall-WindowsFeature RDS-RD-Server -RestartIf you need more users, install and activate RDS CALs on a licence server.
"The user account has been locked"
Too many failed logins, often from bots guessing passwords. Wait for the lockout period or unlock from the console:
Unlock-LocalUser -Name mdmadmin(net user mdmadmin /active:yes on older versions.) Then restrict RDP to your IP so bots cannot reach it.
Black screen after logging in
- Wait a minute: updates or profile loading can delay the desktop.
- Press Ctrl+Alt+End and open Task Manager, then run
explorer.exe. - On the client, disable Persistent bitmap caching under Experience and lower the display resolution.
"Too many users are signed in"
Windows Server allows two admin sessions. Sign out disconnected sessions from the console or another session:
query userlogoff 2Always use Sign out instead of closing the RDP window to avoid leaving sessions behind.
"Your credentials did not work"
- Use the right username format:
Administratoror.\Administratorfor local accounts. - Check the keyboard layout when typing the password.
- The password may have expired; reset it from the console with
net user Administrator *.
Slow or laggy sessions
Lower colour depth and turn off wallpaper and font smoothing in the client's Experience tab, or choose a server location closer to you. If the server itself is slow, see the Windows VPS performance guide.
RDP errors FAQ
Where are RDP logs on the server?
Event Viewer → Applications and Services Logs → Microsoft → Windows → TerminalServices-* and RemoteDesktopServices-*, plus Security events 4624/4625.
Can I reset RDP settings without the console?
No: if RDP is unreachable, the provider console (VNC) is the way in.
Should I change the RDP port?
It reduces noise but is not real protection; IP restrictions or a VPN are far more effective.