How to Connect to a Windows VPS with RDP: Step-by-Step

To connect to a Windows VPS from a Windows PC, open Remote Desktop Connection, enter the server address supplied by your provider, and sign in with the VPS account. The steps below walk through that first connection, checking the server you reached, and preparing it for everyday use.

This guide uses the built-in Remote Desktop Connection client on Windows 11 and a Windows VPS with a graphical desktop. Your provider's instructions take priority for gateways, account names and password resets. A Server Core image will not show the usual Windows desktop.

Before you start

Have these details ready from your authenticated hosting account or verified provisioning message:

A hosting-account password and a Windows VPS password may be different. Store the VPS password in a password manager, separately from your connection notes.

The VPS must be running, have Remote Desktop enabled, permit your account to connect, and allow the required traffic through its firewalls. Windows Home can be a connecting client, but cannot host incoming Remote Desktop sessions. See Microsoft's Remote Desktop prerequisites.

Step 1: Confirm the VPS is ready

1. Sign in to your provider's control panel through its known official address.
2. Select the correct VPS and check that provisioning has completed and the server is running.
3. Confirm its current address, port and Windows username.
4. If access uses an IP allowlist, confirm that your current public IP is permitted. If it uses a VPN, connect to that VPN first.
5. Locate recovery access before you change passwords or firewall rules.

For an RD Gateway setup, use the supplied connection profile or gateway instructions. Entering the VPS address alone may not be enough.

Illustrative connection diagram. Your provider may use an IP restriction, VPN or RD Gateway.

Step 2: Open Remote Desktop Connection on your PC

Perform this step on your own Windows computer.

1. Press Windows + R.
2. Type mstsc.
3. Press Enter.

You should see the Remote Desktop Connection window. You can also search for Remote Desktop Connection from Start. Microsoft's mstsc reference documents the built-in client and its connection options.

You don't need to enable incoming Remote Desktop on your own PC just to connect to the VPS.

Step 3: Enter the address and review connection options

1. In Computer, enter the provider's server address.
2. If the provider uses a custom port, append a colon and that port.
3. Select Show Options to review the username and connection settings.

These are documentation examples. Replace them with your actual details:

1Default port: 203.0.113.10
2Custom port: 203.0.113.10:3390
3Hostname: vps.example.com

Enter an IP address or hostname, without https:// or a website path. Use port 3390 only if your provider specifically supplied it.

In Local Resources, review clipboard, printer and drive redirection. Under More, check whether local drives are selected. Share only resources you need, particularly when connecting from a computer that contains sensitive files. Server policy may restrict these options.

If you save a connection profile, save it on a trusted device. Avoid saving credentials on shared computers. For the client workflow, see the official Windows RDP connection example; its AWS-specific password retrieval steps do not apply to every VPS.

Step 4: Connect and sign in with the VPS account

1. Select Connect.
2. At the credential prompt, check which account is selected.
3. If Windows proposes your local PC account, use More choices and Use a different account, where shown.
4. Enter the exact VPS username and password, then select OK.

Some servers use a local account; others require a domain-qualified username. Follow the supplied format. Don't assume the account is named Administrator.

Review any certificate or identity warning instead of accepting it automatically. A self-signed certificate can trigger a warning on a newly provisioned server. Confirm the expected certificate fingerprint through the authenticated provider console or a verified support channel where available. Matching the destination IP alone does not authenticate the certificate. The AWS RDP guide shows one provider-specific fingerprint verification method.

If you cannot verify an unexpected warning, cancel and ask the provider to confirm the server identity. The exact prompt order can vary by client and authentication setup.

After a successful login, the remote desktop should appear. The desktop and files inside that window belong to the VPS.

Step 5: Check that you reached the correct server

Before installing anything, compare the remote machine with your provisioning details.

1. Inside the remote session, open Start and search for Command Prompt.
2. Run this read-only command:

1hostname

3. Compare the returned computer name with the provider's record, if supplied.
4. Press Windows + R inside the session, run winver, and check the Windows version.
5. Open Task Manager > Performance to inspect memory and CPU information.
6. Open File Explorer > This PC to check available storage.

The hostname command displays the computer's host name. CPU presentation can depend on the virtualization platform, so ask the provider about an unexplained mismatch.

Check the server timezone too, especially if your application schedules jobs. Record the timezone used for maintenance and logs.

Step 6: Change the initial password and confirm access protections

Use the provider's supported password-change procedure. For a standard Windows account that permits an in-session change:

1. Click inside the remote session.
2. Press Ctrl + Alt + End to open the remote Windows Security screen.
3. Select Change a password, if available.
4. Enter the current password and a strong, unique new password.
5. Save the new password in your password manager.

Microsoft documents Ctrl + Alt + End in its Remote Desktop shortcut reference. Managed or domain accounts may require a different password-change process.

Keep recovery access available, then test a fresh connection using the new password. Update saved credentials on trusted devices if needed.

Confirm that Network Level Authentication is enabled unless the administrator has a documented compatibility requirement. Microsoft recommends NLA for most environments. Also confirm the approved access route and who manages provider-side and Windows firewall rules. A custom RDP port does not replace those controls.

For a team, arrange individual accounts and appropriate permissions instead of sharing the initial administrator login. Test a replacement access route before removing a working one.

Step 7: Install and test the application you need

1. Download software from its official source.
2. Check its Windows compatibility, resource requirements and licensing.
3. Install it using the privileges required by its vendor.
4. Open the application and perform a small test of the real task.
5. Save a test file, reopen it, and check any external service the application needs.

Record where application data and configuration are stored. RDP access does not establish that your hosting plan includes an application licence.

Before relying on the VPS, agree on a backup method and update window. Check how the application starts after a reboot, and test recovery of its data in an isolated environment. Monitor the application itself as well as server availability.

Step 8: Finish the session correctly

Save your work before leaving.

A disconnected session may continue running applications, but time limits, administrator actions, restarts or failures can end them. Microsoft's session behavior documentation explains the difference between disconnecting and signing out.

Illustrative session diagram. Disconnecting does not guarantee that an application will keep running.

For unattended work, use the application's supported Windows service or scheduling method. Confirm its restart behavior before depending on it.

If the connection fails

Start with the symptom you see. Avoid repeated password guesses or disabling protections to make a test pass.

For direct RDP access, you can test TCP reachability from Windows PowerShell on your own PC:

1Test-NetConnection -ComputerName "203.0.113.10" -Port 3389

Replace the example address and port. TcpTestSucceeded : True means a TCP connection succeeded; it does not confirm server identity or prove that your credentials will work. A failed ping alone does not prove RDP is unavailable. This direct test may fail by design when access must go through an RD Gateway.

See Microsoft's Test-NetConnection reference and RDS connectivity checklist.

If you still need help, give the provider the server identifier, error text, time and timezone, client version, and whether you used a VPN or gateway. Never include the password.

Your first-session checklist

• Confirmed the destination and server identity.
• Logged in with the intended Windows account.
• Checked the Windows version, resources and timezone.
• Changed initial credentials through the supported process.
• Confirmed the allowed access route and recovery method.
• Tested the application and identified its data location.
• Recorded backup, update and restart arrangements.

Keep those details in an access record with the server owner and recovery contact. Store secrets separately, and update the record whenever access or configuration changes.

Instructions checked against official documentation on 3 October 2026. A live VPS login was not performed. The cover is a generated conceptual image; the inline visuals are explanatory diagrams.