Skip to main content

RDP does not connect on Windows Server: how to solve

When Remote Desktop won't connect, avoid changing multiple settings at the same time. Follow this checklist to identify whether the failure is on the local computer, the network or the Windows Server.

1. Confirm VPS IP and status​

Check in the dashboard that the VPS is connected and that the IP address has not changed. Try:

ping IP_DA_VPS

The lack of a ping response does not prove that the VPS is offline, as the protocol may be blocked.

2. Test the RDP port​

In PowerShell on your computer:

Test-NetConnection IP_DA_VPS -Port 3389

Note TcpTestSucceeded:

  • True: the port responds; review user, password and permissions;
  • False: check firewall, service, route and VPS status.

If you changed the default port, test the configured number.

3. Test another network​

Try connecting via another carrier or trusted connection. If it works, the source may be blocked or has a routing problem.

Do not use public networks to transmit administrative credentials.

4. Review the error message​

Different messages indicate different causes:

  • rejected credentials;
  • account without permission;
  • remote computer unavailable;
  • certificate error;
  • session closed;
  • limit or access policy.

Copy the full text before searching or opening a ticket.

5. Check RDP service​

If you have console access, open PowerShell as an administrator:

Get-Service TermService

The service must be running. To start it:

Start-Service TermService

Do not restart the service during an active session without considering that access may be interrupted.

6. Check if remote access is enabled​

On Windows Server:

  1. open Settings;
  2. access System > Remote Desktop;
  3. confirm that the feature is enabled;
  4. check authorized users.

Microsoft maintains a guide on how to enable Remote Desktop.

7. Check Windows Firewall​

Open Windows Defender Firewall with Advanced Security and check the Remote Desktop inbound rules.

Do not disable the entire firewall. Enable only the rules necessary for RDP.

8. Check credentials​

  • enter the user in the correct format;
  • confirm Caps Lock;
  • remove old credentials in Credentials Manager;
  • test another authorized administrative account;
  • check if the password has expired.

9. Restart only when necessary​

If the VPS is responsive and you have an administrative console, a reboot may recover a crashed service:

Restart-Computer

Wait for the boot to complete.

Frequently asked questions​

Does changing port 3389 resolve attacks?​

It can reduce simple automated attempts, but it is no substitute for strong passwords, updates, IP restriction, VPN, and monitoring.

Can I release RDP to any IP?​

It works, but it increases exposure. When possible, limit the origin to trusted addresses or use a VPN.

Where can I find the official diagnosis?​

See Microsoft's guide for general RDP connection troubleshooting.

What information should I send to support?​

VPS IP, source IP, time, Test-NetConnection result and complete message, not including the password.

If you need help, open a ticket with Nice Hosting support.