By default, Windows has an Account Lockout policy that will lock the account has many failed login attempts.

We enabled Remote Desktop service by default to the public, so these failed login attempts could be from bots or from our users.

If this locking policy is disabled and your password is weak, the account can be brute forced and it is insecure.

There are several solutions to deal with this:

1. Our web dashboard has a firewall that applies the rules at the level outside of the Virtual Machine; no matter the firewall rules inside of the VMs, the firewall in the web dashboard will act as the first priority. You can use this firewall to restrict the default remote desktop port 3389 to your allowed IPs only.
   
   
   
2. You can disable the Account Lockout policy and use a strong Administrator password. To disable the Account Lockout policy, here are the steps:
    
   • In Windows Settings, Search, Type: Edit Group Policy
   • Computer Configuration -> Windows Settings -> Security Settings
   • Open Account Policies -> Account Lockout Policies
   • Choose Account Lockout Threshold: 0
     
     
3. Change the default Remote Desktop port. Here are the instructions:

https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/clients/change-listening-port

If the account is locked, you can still log in via VNC Console in your dashboard. You can also contact our support team via tickets or live chat, we will help.

In a recent Windows update, there is a bug causing this issue. To fix it, here are the steps:

1. Login to your VPS and Open cmd

2. Run this command to open Local Group Policy Editor: gpedit.msc

3. In the Local Group Policy Editor:

Navigate to: Local Computer Policy> Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections > Select network detection on the server - set to Enabled

Select this on the left window:

Turn off Connect Time Detect and Continuous Network Detect

Then click apply and save.

4. Reboot your server to take effect

You can also contact our support via ticket or live chat so we can help you to fix it,

We have already fix this issue in our latest Windows image, you can also reinstall your VPS with the rebuild function in the dashboard.