Cannot Connect to Windows VPS with RDP
Short answerIf RDP fails: confirm the VPS is Active/online, verify the primary IP and Administrator password, try the browser noVNC console, then on the server re-enable Remote Desktop and the firewall RDP rules. Most failures are credentials, firewall, or RDP disabled — not the public internet path alone.
Overview
Use this checklist when Remote Desktop will not connect to a VPSGrid Windows VPS. Connection how-to: Connect with RDP. Enable/repair: Enable Remote Desktop. Console recovery: Use the Console When SSH or RDP Fails.
1) Confirm the VPS is online
- Log in to the client area
- Open Services → My Services → your Windows VPS
- Confirm status is Active (not suspended/cancelled) and the VM is powered on
- Use Boot / Reboot if the guest appears stopped, wait a few minutes, then retry RDP
2) Recheck IP and credentials
- Copy the primary IP from the product details page (do not reuse an old IP from a previous VPS)
- Username is usually
Administrator(confirm welcome email / product details) - Passwords are case-sensitive — try pasting carefully, or reset if you changed it and forgot
- If you use a custom RDP port, your client must specify that port
3) Fail over to the browser console
If RDP still fails, open Console / noVNC from the product page. If the console shows a Windows login or desktop, the guest OS is up and the problem is remote access configuration or networking to TCP 3389.
4) On the server: re-enable RDP and firewall
From the console (PowerShell as Administrator):
# Allow Remote Desktop
Set-ItemProperty -Path 'HKLM:\System\CurrentControlSet\Control\Terminal Server' `
-Name 'fDenyTSConnections' -Value 0
# Prefer NLA
Set-ItemProperty -Path 'HKLM:\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp' `
-Name 'UserAuthentication' -Value 1
# Firewall
Enable-NetFirewallRule -DisplayGroup 'Remote Desktop'
# Service
Get-Service TermService | Select-Object Name, Status, StartType
Start-Service TermService
# Is anything listening on 3389?
Get-NetTCPConnection -LocalPort 3389 -State Listen -ErrorAction SilentlyContinue5) Client-side checks
- Try another network (phone hotspot) in case a local firewall/VPN blocks outbound 3389
- On Windows, test with
mstsc; on macOS use Windows App / Microsoft Remote Desktop — macOS guide - Accept/trust the certificate prompt only after confirming the IP is correct
6) Common causes cheat sheet
| Symptom | Likely cause | What to try |
|---|---|---|
| Timeout / cannot connect | VM off, wrong IP, firewall drop | Power on, verify IP, console + firewall rules |
| Credentials failed | Wrong password/user | Reset password via documented process / console |
| Connection refused | RDP service/port not listening | Enable RDP, start TermService, check port |
| Works on console only | Guest firewall / RDP disabled | Step 4 above |
Frequently Asked Questions
Is this different from the RDP troubleshooting article?
This page is the focused “cannot connect” checklist. Broader RDP issue walkthroughs may also exist in related articles — start here, then use enable/secure guides as needed.
Can support RDP into my VPS for me?
On unmanaged plans, you administer the guest OS. Support can help with platform power/network/billing; include whether console works when you open a ticket.
I hardened RDP and locked myself out
Use noVNC, re-enable Remote Desktop firewall rules, then reconnect. Review the Secure RDP guide before applying scoped IP rules again.
Related Articles
Need More Help?
Open a ticket at billing.vpsgrid.net with your service ID, primary IP, exact client error text, and whether noVNC login works.
¿Le ha resultado útil esta respuesta?
