How to Connect to a Windows VPS with RDP

Quick answer: open your operating system's Remote Desktop client, enter your server's IP address, log in as Administrator with the password from your welcome email, and you are on your Windows desktop in the cloud. The clients are free and already installed on Windows; on Mac and Linux they are one download away.

Where your credentials are

When your Windows VPS finishes provisioning, the welcome email contains the three things RDP needs:

• IP address of the server
• Username, normally Administrator
• Password, generated during installation

Windows Server installs take longer than Linux, so if the email has not arrived a few minutes after ordering, the server is most likely still installing. If it never arrives, check your spam folder before opening a ticket.

Connecting from Windows

The client is built in.

Win + R  >  mstsc  >  Enter

• Enter the server IP in the Computer field and click Connect.
• When prompted, choose More choices > Use a different account and log in as Administrator with the emailed password.
• The first connection shows a certificate warning because the server uses a self-signed certificate. That is expected on a fresh VPS; accept it to continue.

Connecting from a Mac

• Install Microsoft's free Remote Desktop client (currently distributed as the Windows App) from the App Store.
• Add a PC, enter the server IP, and save.
• Double-click the entry, enter Administrator and the password, and accept the certificate prompt.

Connecting from Linux

Remmina is the most common client and ships in most distribution repositories.

sudo apt install remmina remmina-plugin-rdp

Create a new connection with protocol RDP, enter the IP, username and password, and connect. FreeRDP's xfreerdp works equally well from a terminal if you prefer.

First login: change the password

The generated password traveled through email, so replace it on first login:

• Press Ctrl + Alt + End inside the RDP session (this sends Ctrl + Alt + Del to the remote machine).
• Choose Change a password and set a long one you have stored in a password manager.

Keeping RDP safe

RDP on a public IP gets probed constantly by bots. Three habits remove nearly all of the risk:

• Use a long random password. Almost every compromised RDP server was brute-forced through a weak one.
• Restrict who can reach the port. Windows Firewall can limit inbound port 3389 to your own IP address. If your IP changes often, restricting to your country or ISP range still cuts the noise dramatically.
• Install updates. Windows Update on a server is not optional; RDP vulnerabilities are patched fast, but only for servers that patch.

Network Level Authentication is enabled by default on modern Windows Server versions and should stay on; it rejects connections before a full session starts.

Clipboard, disconnect and logoff

Copy and paste works across the RDP session by default: text copied on your desktop pastes inside the server and vice versa, which is the easiest way to move passwords and configuration snippets. For files, the Windows client can map a local drive into the session: in mstsc choose Show Options > Local Resources > More and tick a drive; it then appears in the server's File Explorer.

Know the difference between closing and logging off. Clicking the X on the RDP window disconnects: your programs keep running on the server and reconnecting later drops you into the same session. Choosing Start > Sign out ends the session and closes your programs. For anything that must keep running around the clock, install it as a Windows service instead of leaving it open in a disconnected session.

Troubleshooting

• Connection times out right after ordering: the server is probably still installing Windows. Give it the installation window mentioned in your welcome email before assuming a fault.
• Password rejected: copy-paste can drag a trailing space along. Type the password manually once to rule that out.
• Worked yesterday, refuses today: if you tightened firewall rules recently, check them from the provider console before anything else. Locking your own IP out of port 3389 is a rite of passage.
• Black screen after login: usually transient on first boot while Windows finishes background setup; disconnect, wait a minute, reconnect.

Do not have your Windows server yet? You can deploy a Windows VPS and pay by PayPal or crypto, with RDP credentials delivered automatically when the install completes.