Windows 11 ships with a full Remote Desktop client built in, so connecting to a Windows VPS requires no extra downloads. This guide covers the exact settings that make the first login work, how to save a reusable connection, and the fixes for the connection errors people hit most often.
What you need before you connect
- The public IP address of your VPS, found in your provider’s control panel.
- The administrator username — usually
Administrator, though some providers provision a custom name. - The password you set at provisioning, or the temporary one the provider emails you.
If your provider uses a firewall or security group, confirm that port 3389 (or your custom RDP port) is reachable from your IP. Most providers pre-open RDP, but it is worth checking before you blame the client. If you are still picking a provider, compare Windows VPS plans to see which ones include managed firewalls and monitoring.
Launching the Remote Desktop client
Press Win + R, type mstsc, and press Enter. In the Computer field, enter the VPS IP address and click Connect. If you only have the hostname, the IP from the control panel is more reliable because it bypasses DNS issues.
When the Windows Security prompt appears, use this username format:
.\AdministratorThe .\ prefix tells the client to authenticate against the local machine rather than a domain. Enter the password, tick Remember me if this is your own machine, and click OK.
Handling the certificate warning
On the first connection you will see a certificate warning: the VPS presents a self-signed certificate because it is not joined to a domain. Verify that the name or IP in the warning matches the server you intend to reach, tick Don’t ask again for connections to this computer, and click Yes. This is normal for a newly provisioned VPS; if you later install a proper certificate, the warning disappears.
Optimizing the session for your connection
Before connecting, open the Experience tab and pick a performance profile. For a typical office connection, LAN (10 Mbps or higher) is fine; on slower links choose Modem (56 kbps) so the client disables wallpaper and animations. You can also disable the desktop wallpaper inside the session with Win + Alt + W on the fly.
Using the new Windows 11 Remote Desktop app
Windows 11 also ships with a modern Remote Desktop app (available from the Microsoft Store, often pre-installed). Unlike mstsc, it is touch-friendly, supports multiple saved workspaces, and keeps a connection history with thumbnails. The trade-off: it is less suited to a single quick ad-hoc connection and has fewer fine-grained options such as per-session experience profiles. Many admins use the Store app for daily work and fall back to mstsc for troubleshooting or for the /admin switch, which connects to the actual console session:
mstsc /admin /v:203.0.113.25If you use multiple monitors, launch mstsc, open Show Options, go to the Display tab, and select Use all my monitors for the remote session. The session then spans every screen, which is noticeably more productive for server administration than a single 1080p window.
Saving a reusable connection file
Instead of retyping the IP every time, save the connection. Click Show Options, set your username, then on the General tab click Save As and store the .rdp file on your desktop. Double-clicking it later launches the session with your settings pre-filled. To make it truly one-click, add the password with cmdkey:
cmdkey /generic:TERMSRV/203.0.113.25 /user:.\Administrator /pass:YourPasswordNote that storing passwords in .rdp files or cmdkey is convenient on a private machine but a risk on shared computers — only do this on hardware you control.
Common login errors and fixes
| Symptom | Cause | Fix |
|---|---|---|
| Error 0x4 “connection was denied” | RDP service stopped or port blocked | Restart the VPS from the provider panel, or verify the firewall allows 3389 |
| “Your credentials did not work” | Wrong username format or password | Use .\Administrator and re-check the provisioning email |
| Account locked out | Repeated failed attempts triggered the lockout policy | Unlock from the provider’s VNC/console, or wait for the lockout window to expire |
| NLA error 0x104 | Network Level Authentication mismatch | Log in via the provider console once, then re-enable NLA on the server |
| Black screen after login | Graphics session stuck | Disconnect and reconnect; if it persists, restart the VPS |
If you changed the RDP port to something other than 3389, append it to the address: 203.0.113.25:3390. You can verify the port is open from PowerShell before you even try the client:
Test-NetConnection 203.0.113.25 -Port 3389If TcpTestSucceeded returns True, the network path is fine and the problem is on the server side.
After you log in
Once you are in, change the temporary password immediately, install Windows updates, and review the security settings. For a checklist of what to harden first — firewall rules, RDP limits, and update policies — see the Windows VPS features on our main page. Getting the connection working is only the first step; keeping the server locked down is what actually protects your data.
