How to Enable Remote Desktop
Short answerOn the Windows VPS, enable Remote Desktop in system settings, keep Network Level Authentication (NLA) on when possible, allow TCP 3389 (or your custom RDP port) in Windows Firewall, then connect from your PC with the primary IP and Administrator credentials.
Overview
This article covers enabling Remote Desktop on the server (Windows settings + firewall). For client apps on Windows, macOS, Linux, and mobile, see How to Connect to a Windows VPS Using Remote Desktop (RDP).
VPSGrid Windows templates are normally delivered with RDP already available. Use this guide if RDP was disabled, a hardening change blocked it, or you are restoring access after a rebuild/misconfiguration.
Before you start
- Access the VPS with RDP or the browser noVNC / console from the client area (required if RDP is already blocked)
- Sign in as Administrator (or an account in the Remote Desktop Users group)
- Know your primary IP from Services → My Services
If RDP fails, open the console from the product details page first, then re-enable RDP and firewall rules below. See also How to Use the Console When SSH or RDP Fails.
1) Enable Remote Desktop (GUI)
- Open Settings → System → Remote Desktop (Windows Server UI may show System Properties → Remote)
- Turn Remote Desktop On / select Allow remote connections to this computer
- Prefer leaving Network Level Authentication (NLA) enabled
- Confirm your user is allowed (Administrator is typically allowed by default)
- Apply / OK, then keep the session open until you verify an external connection
2) Enable Remote Desktop with PowerShell
# Enable Remote Desktop
Set-ItemProperty -Path 'HKLM:\System\CurrentControlSet\Control\Terminal Server' `
-Name 'fDenyTSConnections' -Value 0
# Prefer NLA (recommended)
Set-ItemProperty -Path 'HKLM:\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp' `
-Name 'UserAuthentication' -Value 1
# Allow RDP through Windows Defender Firewall (built-in group)
Enable-NetFirewallRule -DisplayGroup 'Remote Desktop'
# Confirm the RDP service is running
Get-Service TermService | Select-Object Name, Status, StartTypeRun PowerShell as Administrator.
3) Confirm the firewall and listening port
- Default RDP port is TCP 3389
- If you changed the RDP port, allow that custom port instead and update client connection settings
# Firewall rules related to Remote Desktop
Get-NetFirewallRule -DisplayGroup 'Remote Desktop' |
Select-Object DisplayName, Enabled, Direction, Action |
Format-Table -AutoSize
# Is anything listening on 3389?
Get-NetTCPConnection -LocalPort 3389 -State Listen -ErrorAction SilentlyContinueFirewall how-tos: Windows Firewall Basics · PowerShell firewall rules.
4) Connect from your computer
- From Windows: open Remote Desktop Connection (
mstsc) - Computer: your VPS primary IP
- User:
Administrator(or your allowed account) with the current password
Full client steps for other devices: RDP connection guide.
Important notes
- Enabling RDP is not the same as including a Windows license — Windows VPS plans are BYOL unless your order states otherwise
- Keep strong passwords; consider additional hardening after access works (Secure RDP on Windows VPS)
- Do not disable Windows Firewall entirely to “make RDP work”
Frequently Asked Questions
RDP was working and suddenly stopped
Check VPS power status in the client area, use the console, confirm fDenyTSConnections is 0, re-enable the Remote Desktop firewall group, and verify TermService is running.
Should I turn off Network Level Authentication?
Keep NLA on when your clients support it. Only disable temporarily for troubleshooting old clients, then turn it back on.
Is this the same as the RDP connection guide?
No. This article enables RDP on the server. The connection guide covers client apps and login from your devices.
Related Articles
Need More Help?
Open a ticket at billing.vpsgrid.net with your service ID, primary IP, and whether console access still works.
Was this answer helpful?
