How to Troubleshoot RDP Connection Issues
Short answerWhen RDP fails, confirm the Windows VPS is Active/online, verify you are using the correct IP and Administrator credentials, check Windows Firewall and Remote Desktop Services, test port 3389, and use the noVNC console if you are locked out.
Overview
Use this guide when Remote Desktop will not connect to your VPSGrid Windows VPS. First-time connection steps: How to Connect to a Windows VPS Using RDP. Enable RDP if never configured: How to Enable Remote Desktop.
1) Confirm the VPS is online
- Log in at billing.vpsgrid.net
- Open Services → My Services → your Windows VPS
- Confirm status is Active
- Use Boot or Reboot if the VM may be offline
- Wait 2–3 minutes after boot — Windows services take longer than Linux on first start
If the VPS is suspended for an unpaid invoice, pay the invoice first — How to Pay an Invoice.
2) Verify RDP client settings
- Open Remote Desktop Connection (
mstscon Windows) - Computer: enter the VPS primary IP only (no
http://prefix) - Connect as Administrator with the password from the welcome email or client area
- On macOS use Microsoft Remote Desktop; on Linux use Remmina or FreeRDP
If certificate warnings appear, confirm the IP matches your service details before accepting.
3) Match the error message
| Error / symptom | Likely cause | Fix path |
|---|---|---|
| Remote Desktop can't connect | VM offline, wrong IP, outbound 3389 blocked locally, inbound RDP blocked in Windows | Steps 1, 4, 5 |
| Credentials did not work | Wrong/expired password, Caps Lock, keyboard layout | Reset Administrator password |
| Immediate disconnect / licensing error | Windows licensing (BYOL) issue | Windows VPS Licensing Requirements |
| Worked before firewall change | Windows Firewall or network profile change | Step 4 via noVNC |
4) Use noVNC when RDP is completely blocked
- On the VPS service page, open noVNC Console
- Log in as Administrator at the local console
- Confirm Remote Desktop Services is running (
services.msc) - In Windows Defender Firewall, enable Remote Desktop (TCP-In) for the active profile
- Run
ipconfigand confirm the IP matches the client area
Console recovery guide: How to Use the Console When SSH or RDP Fails.
5) Test port 3389 reachability
From your workstation:
nc -vz YOUR_VPS_IP 3389
# or: Test-NetConnection YOUR_VPS_IP -Port 3389 # PowerShellIf the VPS is Active but 3389 is closed while you are certain RDP should be enabled, the block is almost always inside Windows Firewall — not the VPSGrid hypervisor.
6) First boot and reinstall notes
- Windows may mark the network as Public on first boot, restricting RDP — set Private or allow RDP on Public in firewall settings via console
- After OS reinstall, credentials change — use the latest welcome email
- Allow a few minutes after reinstall for Windows Update and network profile detection
7) Local workstation checks
- Try from another network to rule out ISP/corporate firewall blocking outbound 3389
- Disable VPN/proxy temporarily for testing
- Do not enable a Remote Desktop Gateway unless your organization requires one
8) After RDP works again
Harden access — How to Secure RDP on Windows VPS. Firewall basics: Windows Firewall Basics.
Frequently Asked Questions
Can I change the RDP port?
Yes via Registry and firewall rules. Document the new port and keep console access ready while testing.
Does VPSGrid include a Windows license?
No — BYOL is required. Licensing issues can cause RDP session problems separate from network connectivity.
RDP connects but disconnects immediately
Check RAM/CPU in Task Manager and review licensing/Group Policy. Undersized plans may struggle under desktop load — VPS Is Slow: How to Diagnose.
Related Articles
Need More Help?
Open a ticket at billing.vpsgrid.net with VPS ID, primary IP, exact RDP error text, and whether noVNC login succeeds.
Was this answer helpful?
