50% off your first hosting order, applied in your cart, on our upgraded infrastructure! Ends in: View Plans →
Türkiye · France · Northern Cyprus05372609483
Cloud VDS

RDP Security on a Windows VDS: 7 Steps to Protect Remote Desktop from Attacks

  • 22 November 2026
  • 4 min read
Contents
    Share this post

    On a Windows server reachable from the internet, the Remote Desktop (RDP) port becomes a target for password-guessing bots within minutes of installation. Most of those attempts fail, but one weak password, a forgotten test account or an unpatched system is enough to lose the server. A large share of ransomware attacks also start through exposed RDP. This guide hardens RDP on your Windows VDS in seven steps.

    Before you start: know the VNC console

    You can lock yourself out while changing firewall rules. On Fiberserver VDS plans, the VNC console in the FiberVM panel gives you screen and keyboard access to the server even when RDP is closed. Open it once before making changes and check that it works; see the FiberVM panel article for details.

    1. Keep the system updated

    Most RDP vulnerabilities are closed by published security updates. Set Windows Update to download and install automatically, and schedule restarts for a quiet hour. If your version no longer receives security updates, the other steps only reduce the risk; see our Windows Server 2016 end of support news.

    2. Strong passwords and a separate admin account

    • Give the Administrator account a password of at least 16 characters that is used nowhere else.
    • Create a separate admin account in your own name for daily work, and keep Administrator as a fallback.
    • The reinstall and password tools in the FiberVM panel work with the Administrator account, so do not delete or rename it.
    • Give accounts created for applications or staff only the rights they need.

    3. Set an account lockout policy

    Open Local Security Policy with secpol.msc and enter these values under Account Policies > Account Lockout Policy:

    SettingRecommended value
    Account lockout threshold5-10 invalid attempts
    Account lockout duration15-30 minutes
    Reset account lockout counter after15-30 minutes

    This turns brute-force attempts from thousands of passwords a minute into a handful an hour.

    4. Keep Network Level Authentication (NLA) on

    In the window opened by SystemPropertiesRemote, "Allow connections only from computers running Remote Desktop with Network Level Authentication" must be ticked. NLA requires authentication before the sign-in screen opens, which reduces both the attack surface and the load on the server.

    5. Open RDP only to your own IP addresses

    This is the most effective step. If your office or home has a static IP address, narrow the Remote Desktop rule in Windows Firewall to allow only those addresses. In PowerShell run as administrator:

    Set-NetFirewallRule -DisplayGroup "Remote Desktop" -RemoteAddress 203.0.113.10,198.51.100.0/24

    On a Windows installation in another language the rule group has a translated name; check it with Get-NetFirewallRule | Where-Object DisplayGroup -like "*Remote*". Without a static IP, the next step and the VPN option fit better.

    6. Change the port (an extra measure)

    Using a port other than the default 3389 is not real security on its own, but it greatly reduces the noise of automated scans. In an administrator PowerShell:

    Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp' -Name PortNumber -Value 3390
    New-NetFirewallRule -DisplayName "RDP 3390" -Direction Inbound -Protocol TCP -LocalPort 3390 -Action Allow
    Restart-Service TermService -Force

    Confirm that you can connect on the new port (server-ip:3390) before closing the old 3389 rule.

    7. Hide RDP completely: VPN

    If several people connect from different places, the most robust solution is not to expose RDP to the internet at all. Install a VPN such as WireGuard on the server and narrow the RDP rule to the VPN network only. The only thing visible from outside is then the VPN port.

    Watch the attacks

    Failed sign-in attempts are written to the Security log with event ID 4625. To see the latest ones:

    Get-WinEvent -FilterHashtable @{LogName='Security'; Id=4625} -MaxEvents 20 |
      Select-Object TimeCreated, @{n='IP'; e={$_.Properties[19].Value}}

    If the list keeps showing different IP addresses, do not postpone step 5 or 7.

    Checklist

    • Windows Update is automatic and the system receives security updates
    • Unique, long passwords on Administrator and other admin accounts
    • An account lockout policy is set
    • NLA is on
    • RDP is open only to specific IPs or to a VPN
    • Regular backups kept off the server: the 3-2-1 backup rule

    If you need a Windows VDS, see our plans in the Türkiye, France and Cyprus locations, where Windows Server 2019, 2022 and 2025 can be installed. For Linux servers, the same topic is covered in the VDS security guide.

    Comments0

    No Comments Yet

    Be the first to share your thoughts.

    Join the Discussion

    Please sign in or sign up to leave a comment.

    Never Miss a Post

    Get our latest tutorials, guides and product news in your inbox.

    You're subscribed to our newsletter.