How to Connect to a Windows VPS via RDP (Windows, macOS, Linux & Mobile)
Step-by-step guide to connect to a Windows VPS via RDP from any OS. Covers credentials, troubleshooting common errors, and basic security hardening.
The Remote Desktop Protocol (RDP) is Microsoft’s native protocol for remote access to Windows machines. When you provision a Windows VPS, RDP is how you administer it — installing software, configuring services, moving files. Unlike SSH on Linux, RDP transmits the full graphical interface, so you operate Windows Server exactly as if you were sitting in front of it.
This tutorial is for anyone who has never used RDP and just received VPS access credentials from their provider.
Before you start, make sure you have three pieces of information that your provider sends by email after provisioning: the IP address, the username (usually Administrator), and the password. If you haven’t received them yet, check your spam folder or the Hostini dashboard at /painel.
Prerequisites
A Windows Server VPS (2019, 2022, or 2025) already provisioned and running, a stable internet connection, and the access credentials supplied by your provider. No additional software is required on Windows — the RDP client comes pre-installed.
Your access credentials follow this format:
203.0.113.45 Administrator 3389 The password is randomly generated at provisioning time and sent by email. If you didn’t save it, you can reset it through the VPS management panel — look for “reset administrator password” or an equivalent function.
Connecting from Windows
Windows 10 and 11 ship with the native RDP client, called Remote Desktop Connection. There is nothing to install.
Open the Start menu and type mstsc (Microsoft Terminal Services Client). Press Enter. The remote connection window opens.
You can also use Win + R → type mstsc → Enter.
In the “Computer” field, enter your VPS IP address. If your provider uses a custom port (other than 3389), use the IP:port format:
203.0.113.45
203.0.113.45:33890Click “Connect”.
At the credentials prompt, enter your username and password. If the screen is pre-filled with your local Windows username, click “More choices” → “Use a different account” and type manually:
Username: Administrator
Password: <password sent by email>Only check “Remember me” on personal, trusted machines.
Windows will display a warning that the remote server’s certificate is not trusted. This is expected on a first connection — the certificate is self-signed by default. Check “Don’t ask me again for connections to this computer” and click “Yes”.
After a few seconds, the Windows Server desktop appears in full screen. You are connected.
Before clicking Connect, open “Show Options” and configure resolution, printer redirection, audio, and local drive mapping. Then click “Save As” and store an .rdp file on your desktop — future connections become a double-click.
Connecting from macOS
macOS does not include a native RDP client, but Microsoft distributes the official one for free on the App Store.
Open the App Store, search for “Windows App” (previously “Microsoft Remote Desktop”), and install it. The app is free and maintained by Microsoft.
Open the app and click ”+” → “Add PC”. Fill in the fields:
PC name: 203.0.113.45
User account: Add User Account...
Username: Administrator
Password: <your password>
Friendly name: Hostini VPSClick “Add”.
Double-click the card that appears in the list. Accept the certificate warning by clicking “Continue”. The session opens in a window or full screen depending on your default settings.
Connecting from Linux
On Linux, the current recommendation is Remmina (more user-friendly) or FreeRDP (command-line, more flexible).
Install Remmina and its RDP plugin:
sudo apt update && sudo apt install -y remmina remmina-plugin-rdpLaunch Remmina, click the ”+” button to create a new connection profile, and fill in:
Protocol: RDP - Remote Desktop Protocol
Server: 203.0.113.45
Username: Administrator
Password: <your password>Save the profile and double-click it to connect. Accept the certificate when prompted.
If you prefer the command line, connect with FreeRDP directly:
# Install FreeRDP
sudo apt install -y freerdp2-x11
# Connect — replace values as needed
xfreerdp /v:203.0.113.45 /u:Administrator /p:'YourPassword' /dynamic-resolution /cert:ignoreThe /cert:ignore flag suppresses the self-signed certificate warning. Remove it once you have a valid certificate in place.
Verifying Everything Works
Once connected, run three quick checks inside the RDP session to confirm the VPS is healthy:
Get-ComputerInfo | Select-Object WindowsProductName, OsArchitecture, CsTotalPhysicalMemoryThis returns the Windows Server edition, architecture, and total installed RAM — verify it matches the plan you purchased.
To test outbound connectivity from the VPS:
Test-NetConnection -ComputerName 8.8.8.8 -Port 443The output should show TcpTestSucceeded : True.
Troubleshooting
Error: “Remote Desktop can’t connect to the remote computer”
Usually one of three causes: wrong IP, port 3389 blocked by a local firewall (corporate networks commonly block outbound 3389), or the VPS is powered off. Start with:
ping 203.0.113.45If ping responds but RDP does not connect, the issue is a firewall rule — test from a different network (mobile hotspot works well for diagnosis).
Error: “Your credentials did not work”
Confirm you are using exactly Administrator (capital A, English spelling) and not a localized variant. If the password contains special characters, paste it instead of typing — characters like |, ", and \ can be interpreted differently depending on keyboard layout.
CAL license error after connecting
Windows Server in evaluation mode can block simultaneous RDP connections after 120 days. If you receive “No Remote Desktop License Servers available”, the VPS requires proper licensing — contact your provider’s support team.
If RDP hangs indefinitely on the blue “Configuring remote session” screen, disconnect and reconnect. If it persists, request a reboot through the management panel. Do NOT initiate a reboot through Windows inside the RDP session before confirming you have console access in the panel — you may lose access temporarily.
Next Steps
With the connection working, consider these adjustments for ongoing use:
- Change the Administrator password as soon as you log in for the first time (
Ctrl + Alt + Endinside the session opens the security menu). - Create a non-administrator user for day-to-day tasks and reserve the Administrator account for critical changes.
- Configure Windows Firewall to restrict RDP access to known IP addresses, reducing brute-force attack surface.
- Enable Network Level Authentication (NLA) if not already active — Control Panel → System → Remote settings.
- Explore PowerShell Remoting (WinRM) as an alternative for automation without opening a graphical session.
If you are deploying production applications, a Hostini Windows VPS comes with Windows Server licensing included, a dedicated IP, and DDoS protection at the network edge — you just connect and configure.
Frequently asked questions
Can I connect to a Windows VPS through a browser without installing anything?
It depends on the provider. Some management panels offer an HTML5 console (noVNC or similar) for emergency browser-based access. For regular use, the native RDP client is faster and supports file, printer, and audio redirection — features the web console generally lacks.
What is the difference between RDP and VNC?
RDP is a Microsoft proprietary protocol optimized for Windows, with efficient compression and features like drive and audio redirection. VNC is an open protocol that transmits the raw screen framebuffer and works on any OS, but is heavier on bandwidth. For Windows Server, RDP is always the better choice.
Is it safe to leave port 3389 open on the internet?
Not without hardening. Port 3389 is a constant target for brute-force attacks. Minimum practices are: change to a non-default port, enable NLA, use strong passwords (16+ characters), and ideally restrict access via firewall to known IPs or add a VPN as an extra layer.
How many users can use RDP simultaneously on a Windows VPS?
By default, Windows Server allows 2 concurrent administrative sessions without additional licensing. For more simultaneous users, you need to install the Remote Desktop Services role and purchase CAL (Client Access License) licenses. For personal or administrative use, 2 sessions are usually enough.
Why is my RDP connection slow or choppy?
Common causes: high latency between you and the datacenter (above 150ms causes visible lag), insufficient bandwidth (RDP needs at least 1 Mbps stable), or visual quality set too high. In "Show Options" → "Experience" tab, set the connection speed to "Modem (56 kbps)" for diagnosis — if it improves, the issue is network-side.
How do I transfer files from my computer to the VPS over RDP?
Before connecting, go to "Show Options" → "Local Resources" tab → "More..." → check the drives you want to share. Inside the RDP session, those drives appear under "This PC" in Windows Server, and you can copy and paste files between the two systems normally.