Connect to a Windows VPS from Windows: RDP Client Walkthrough

Connecting to a Windows VPS from a Windows desktop takes about five minutes once you know where the pieces are: an IP address, a username, a password, and the Remote Desktop Connection client that ships with every edition of Windows. This walkthrough goes through the steps in order so your first login does not turn into a support ticket. If you are still shopping for a server, compare Windows VPS providers on our comparison table first so you know what you are paying for.

Gather your connection details

• Server address: the public IP or hostname from your provider’s welcome email, invoice, or control panel.
• Username: usually Administrator on a fresh Windows Server install, or a custom admin account you created.
• Password: the one you set during provisioning, or a temporary password from the provider (you will be forced to change it on first login).
• Port: 3389 by default. If your provider or your own hardening moved RDP to another port, note it down.

Launch Remote Desktop Connection

Press Win+R, type mstsc, and press Enter. The built-in Remote Desktop Connection client is present on Windows 10 and Windows 11, Home editions included (the restriction on Home editions applies to hosting inbound RDP sessions, not to connecting out to a server). If you prefer the modern client, Microsoft’s “Windows App” from the Microsoft Store is a drop-in replacement with the same settings.

Enter the address and credentials

• In the Computer field, type the IP address or hostname. If RDP runs on a non-standard port, append it with a colon, e.g. 203.0.113.10:3390.
• Click Show Options and fill in the User name: Administrator, or SERVERNAME\Administrator if you use the hostname format.
• Tick Allow me to save credentials if this is a trusted machine, then click Connect.
• Enter the password when prompted. On a fresh server with a temporary password, Windows forces a change before the desktop appears.

You will likely see a warning that “The identity of the remote computer cannot be verified.” That is normal: the server presents the self-signed certificate generated during Windows setup. Verify that the IP or hostname in the warning matches the server you intended to reach, then click Yes. Once you install a real certificate on the server, this prompt disappears.

Your first-login checklist

• Change the temporary password and store it in your password manager.
• Run Windows Update and install pending patches before doing anything else; a fresh template is often several months behind.
• Confirm which accounts can log in remotely: open lusrmgr.msc, check the Remote Desktop Users group, and remove anyone who should not be there.
• Check that NLA is enabled (System Properties > Remote > “Allow connections only from computers running Remote Desktop with Network Level Authentication”). It blocks a large share of automated attacks.
• Verify disk space with df-equivalent — open This PC and confirm the C: drive has room for updates and your workload.

Save the connection as an .rdp file

If you connect regularly, save the settings: with Show Options open, click Save As and store the .rdp file somewhere sensible. Double-clicking it later opens the session with all settings pre-filled. The file is plain text, so you can also edit it to pin the display size or add a gateway address. Keep it out of shared folders — it contains no password by default, but it reveals your server address and username.

When the connection fails

Error message	Likely cause	Fix
“This computer can’t connect to the remote computer”	RDP disabled, or the firewall blocks TCP 3389	Re-enable RDP on the server (System Properties > Remote) and confirm the Windows Defender Firewall inbound rule for RDP is active
“Your credentials did not work”	Wrong username format or password	Use .\Administrator or SERVERNAME\Administrator; reset the password from the provider’s console if needed
“An authentication error has occurred (Code: 0x8009030E)”	CredSSP / TLS version mismatch between client and server	Update Windows on the client, and check the Encryption Oracle Remediation policy on the server
“The user account is not authorized for remote login”	Account missing from the Remote Desktop Users group	Add it with net localgroup "Remote Desktop Users" USERNAME /add from an admin session

Before opening a support ticket, run a quick connectivity check from your own machine: Test-NetConnection 203.0.113.10 -Port 3389 in PowerShell. If TcpTestSucceeded is False, the problem is on the network path or the server firewall, not in the client.

When direct RDP is not an option

Some providers or security policies keep 3389 closed to the internet. The practical alternatives are a Remote Desktop Gateway (one HTTPS endpoint that brokers sessions), a VPN into the server’s network, or PowerShell remoting (WinRM) for scripted administration. All three are supported by the same Windows client tooling, and the gateway approach works from any device. For sizing guidance before you buy, see the full specs and pricing — 2 GB is workable for light RDP use, but IIS, SQL Server, or build agents are far more comfortable with 4 GB or more. Once connected, keep the session patched and the Remote Desktop Users group small; RDP is the most probed service on any public Windows server.