Windows VPS: plans, Remote Desktop access and troubleshooting
Everything about UnderHost Windows Cloud VPS: plans and locations, connecting with Remote Desktop from Windows, macOS and mobile, securing RDP, running trading platforms, and fixing connection problems.
UnderHost NOC
Network Operations
On this page
An UnderHost Windows Cloud VPS is a virtual server with Windows Server pre-installed and full Administrator access over Remote Desktop (RDP). Use it as an always-on Windows desktop, for business applications, for .NET, IIS and MSSQL, or to run trading platforms such as MT4, MT5 and cTrader around the clock. For your first steps after login, see Getting started with Windows Server.
Plans and locations
| Plan | CPU | RAM | SSD | Bandwidth | Price |
|---|---|---|---|---|---|
| CVWIN 1 | 1 vCore | 1 GB | 25 GB | 1 TB | $29.95 USD / month |
| CVWIN 2 | 2 vCores | 2 GB | 40 GB | 4 TB | $49.95 USD / month |
| CVWIN 3 | 4 vCores | 4 GB | 80 GB | 8 TB | $69.95 USD / month |
| CVWIN 4 | 8 vCores | 8 GB | 120 GB | 16 TB | $99.95 USD / month |
- Every plan includes a dedicated IP address, full Administrator RDP access, a 1 Gbps port, DDoS protection and Windows Server.
- Locations: Netherlands (Amsterdam), Canada (Montreal) and Hong Kong.
- Extra IPv4 addresses are $4.95 USD per month each. Custom configurations are available on request.
- Setup: usually within a few hours during business hours, and up to 24 hours outside them. Your login and IP details are sent by email.
Windows uses more memory than Linux. For a desktop you work on, or more than one trading terminal, start with CVWIN 2 or larger. See current plans on the Windows VPS page.
Which Windows Server version
| Version | Microsoft end of support | Recommendation |
|---|---|---|
| Windows Server 2019 | January 2029 | Choose this for new servers |
| Windows Server 2016 | January 2027 | Only if your software needs it; plan an upgrade |
| Windows Server 2012 | Ended October 2023 | Avoid: it no longer receives security updates |
The version is included at no extra cost. Choose it at checkout, or ask support to reload the server with another version. A reload erases the server, so back up first.
Connect with Remote Desktop
You need three things from your welcome email: the server's IP address, the user name (Administrator) and the password.
| Your device | App | How |
|---|---|---|
| Windows | Remote Desktop Connection (built in) | Press Win + R, type mstsc, enter the IP, then log in |
| macOS | Windows App (formerly Microsoft Remote Desktop), from the App Store | Add a PC with the IP, then log in |
| iPhone, iPad, Android | Windows App / Remote Desktop by Microsoft | Add a PC with the IP, then log in |
| Linux | Remmina or xfreerdp | Choose RDP and enter the IP |
The first time you connect, you see a certificate warning, because the server uses its own certificate. Check that the IP is yours, then accept it. If you changed the RDP port, add it after the IP, for example 203.0.113.10:50123.
Secure your RDP access
Internet-facing RDP is attacked constantly by bots trying passwords. Do these on the first day:
Change the Administrator password
Press Ctrl + Alt + End in the session (or Ctrl + Alt + Del on the console) and choose Change a password. Use a long, unique passphrase.
Install Windows updates
Run Windows Update until no updates remain, and leave automatic updates on.
Limit who can reach RDP
In Windows Defender Firewall with Advanced Security, open the Remote Desktop inbound rules and set Scope → Remote IP addresses to your own IP addresses. This is the most effective protection.
Lock out password guessing
Set an account lockout policy, keep Network Level Authentication on (System Properties → Remote), and create a separate named admin user for daily use.
# allow RDP only from your own IP (replace with yours)
Set-NetFirewallRule -DisplayGroup "Remote Desktop" -RemoteAddress 198.51.100.25
# lock an account for 15 minutes after 5 wrong passwords
net accounts /lockoutthreshold:5 /lockoutduration:15 /lockoutwindow:15
# check that Network Level Authentication is on (1 = on)
(Get-ItemProperty 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp').UserAuthenticationBefore you limit RDP to your IP, check what your current IP is. If your home IP changes often, add a range or keep a second allowed address. If you do lose access, open a ticket and support can help restore it.
Trading platforms and always-on apps
- Close the session, do not log off. Closing the Remote Desktop window disconnects you but keeps your programs running. Sign out stops them.
- Start programs automatically after a reboot: put a shortcut to the terminal in
shell:startupand set the account to log in automatically, or use the platform's own service option. - Pick the nearest location to your broker's servers for the lowest latency: Netherlands for Europe, Canada for North America, Hong Kong for Asia.
- Watch memory. Each terminal and Expert Advisor uses RAM. If Task Manager shows memory near full, upgrade the plan.
If RDP will not connect
| What you see | Likely cause | What to do |
|---|---|---|
| "Remote Desktop can't connect to the remote computer" | Server rebooting or updating, wrong IP or port, or your IP blocked by the firewall scope | Wait a few minutes after a reboot, check the IP and port, and check whether your own IP has changed |
| "The credentials did not work" | Wrong password or user name | Use Administrator (or .\Administrator) and retype the password; check Caps Lock |
| "The user account has been locked" | Too many wrong passwords, yours or a bot's | Wait for the lockout period, or open a ticket |
| Very slow or freezing session | CPU or memory full, or a slow connection | Check Task Manager; lower colour depth and turn off visual effects in the RDP client's Experience settings |
| Black screen after login | Updates finishing, or explorer.exe stuck | Wait, then press Ctrl + Alt + End, open Task Manager and run explorer.exe |
Test whether the port is reachable from your computer with Test-NetConnection 203.0.113.10 -Port 3389 in PowerShell. If it fails and nothing changed on your side, open a ticket with the result.
What support covers
Standard support includes OS installation and reload, reboots and ticket assistance. Full server management, proactive monitoring and off-site backups are available as optional add-ons. See server management. To move to a larger plan, contact support; upgrades are handled with minimal disruption. See Resize your Cloud VPS.
FAQ
Related: Getting started with Windows Server | Resize your Cloud VPS | Choose an operating system | Linux or Windows
Need a Cloud VPS?
Launch an UnderHost Cloud VPS when you need root access, dedicated resources, custom software, or more control than shared hosting.
