You reach the graphical interface of a Windows VPS with a remote desktop connection (RDP, Remote Desktop Protocol): the server’s desktop appears in a window or full screen on your own computer, and you can work on it as if you were sitting in front of it. You don’t need to install anything on the server: Remote Desktop is already enabled when the server is handed over to you. Below we go through connecting from Windows, macOS, Linux and a phone, then the security settings and common errors.
We tested the Windows and Linux client steps in November 2026 on Hungarian-language Windows 11 (Remote Desktop Connection) and on Ubuntu 26.10 (Remmina 1.4.43, FreeRDP 3.32), and the server-side settings on a Hungarian-language Windows 11 Pro test machine. The menu names below are those of English-language Windows. The macOS and mobile Windows App steps follow Microsoft’s documentation. For how RDP works in general, see our article on RDP.
What will you need?
- The server’s IP address. We send you this, along with the login details, when the server is handed over.
- The username and password. On Windows Server, the initial account is usually the built-in administrator account (
Administrator). - An RDP client on your own device: it is built into Windows, and free to download for other systems.
By default RDP uses TCP and UDP port 3389. If you have not changed the port, the IP address is enough in the client; for a different port, add it after a colon, for example 203.0.113.10:3390.
Without an extra licence, Windows Server allows two remote administrative sessions at a time. If several of you want to work on the server at the same time, you need Remote Desktop Services (RDS) licences; for these, contact us.
Connecting from Windows
The built-in client of Windows 10 and 11 is Remote Desktop Connection.
- Press Win+R, type
mstscand press Enter. (You can also find it by searching for “Remote Desktop Connection” in the Start menu.) - Click Show Options. On the General tab, enter the server’s IP address in the Computer field and the username in the User name field.
- If you like, set up the display and the shared resources (see below), then click Connect.
- In the Windows Security window (Enter your credentials), enter the password. If you tick Remember me, Windows saves the password in its Credential Manager; don’t do this on a shared computer or one that others also use.
- On the first connection you get a certificate warning (see the next section). If you accept it, the server’s desktop appears.
You can save the settings to an .rdp file with the Save As… button on the General tab, so next time you only need to double-click that file.
The certificate warning
By default, Windows Server identifies itself in the remote desktop connection with a self-signed certificate, which your computer cannot trace back to a known certification authority. So on the first connection a warning like this appears: The remote computer could not be authenticated due to problems with its security certificate. The reasons listed include: “The certificate is not from a trusted certifying authority.”
The connection is still encrypted. If you are sure you typed your own server’s IP address, click Yes; before that, you can use View certificate… to check that the certificate is issued to the server’s name. If you tick the option not to ask again for connections to this computer, the client remembers the certificate. If the warning unexpectedly reappears later for a server you have already accepted, and you have not reinstalled the server, don’t connect; contact us instead.
Resolution, multiple monitors, clipboard and drives
The tabs under Show Options have to be set before you connect:
- Display: the Display configuration slider sets the size of the window; at its far right end is Full Screen. The Use all my monitors for the remote session checkbox extends the remote desktop across all your monitors.
- Local Resources: with Clipboard turned on, you can simply copy and paste text and files between the two computers; with Printers ticked, your own printers appear on the server. Click More…, and under Drives you can choose drives of your computer to share: on the server they appear in File Explorer, among the redirected drives. For copying larger files this is more convenient than the clipboard.
- Local Resources › Keyboard: by default, Windows key combinations (for example Alt+Tab) are passed to the server Only when using the full screen. On the remote computer, use Ctrl+Alt+End instead of Ctrl+Alt+Del, for example to change your password.
- Experience: on a slow connection you can turn off the desktop background and the animations here, if you choose the connection speed manually.
As a shared drive and the clipboard open a direct path between your computers, share only what you need for your work.
Connecting from macOS
On a Mac, use Microsoft’s free Windows App (the successor to Microsoft Remote Desktop), which you can download from the Mac App Store. You don’t need a Microsoft account to sign in. On macOS the app has an English interface, and the labels below are taken from it.
- Open Windows App. On the Devices tab, click the + icon, then Add PC.
- Enter the server’s IP address in the PC name field. In the Credentials list, Add Credentials… saves the username and password; if you leave it empty, the app asks for them when you connect. In the Friendly name field you can give the connection a descriptive name.
- On the Display tab you can set the resolution and the Use all monitors and Start session in full screen options. On the Devices & Audio tab you set up the clipboard and printers, and on the Folders tab, turning on Redirect folders shares folders of your Mac.
- Click Add, then double-click the server on the Devices tab.
- At the certificate warning, check the details as described above and click Continue.
Connecting from Linux
Remmina
The desktop editions of Ubuntu and several other distributions include the Remmina remote desktop client; if it is not installed, you can install it on Ubuntu with sudo apt install remmina.
- Start Remmina Remote Desktop Client.
- For a quick connection, leave RDP selected in the protocol selector, type the server’s IP address in the field next to it and press Enter.
- On the first connection Remmina shows the certificate details and asks: Accept certificate? If you typed the address correctly, click Yes.
- In the Enter RDP authentication credentials window, fill in the Username and Password fields, then click OK.
If you connect regularly, save the connection: clicking the + button at the top left opens the Remote Connection Profile window. On the Basic tab you fill in the Server, Username and Password fields; here you also find the Share folder field (a folder shared from your computer), the Enable multi monitor option and the Resolution setting, where Use client resolution passes on the resolution of your own screen. On the Advanced tab you can turn on Share printers. Finally, click Save and Connect.
FreeRDP from the command line
On Ubuntu, the FreeRDP 3 client is in the freerdp3-x11 package (sudo apt install freerdp3-x11). Connecting with dynamic resolution, the clipboard and a folder of yours shared:
xfreerdp3 /v:203.0.113.10 /u:Administrator /dynamic-resolution +clipboard /drive:home,/home/felhasznalo
On the first connection the program prints the certificate details and asks: Do you trust the above certificate? (Y/T/N). Y accepts it permanently, T only for this one connection. Then just press Enter at the Domain prompt and enter the password. Don’t give the password with the /p: option, as anyone could then see it in the computer’s process list (FreeRDP warns about this itself). On the server, the shared folder appears among the redirected drives under the name home.
Connecting from a phone or tablet
On iPhone and iPad, download Microsoft’s Windows App from the App Store; on Android, from Google Play. The labels follow Microsoft’s documentation:
- Tap the + icon, then PC on iPhone and iPad, or PC connection on Android.
- Enter the server’s IP address in the PC Name field. If you like, add the user account and a descriptive name here as well, then tap Save.
- On the Devices tab, tap the server. If you have not saved an account, the app now asks for the username and password. On Android, the Make sure you trust the remote PC before you connect prompt appears before connecting, where you can also choose which local resources (for example the clipboard) to share; then tap Connect.
On a phone, touch can only partly make up for a mouse and keyboard; it is fine for a quick check or restarting a program, but for longer work use a tablet with a keyboard.
Sign out or disconnect?
If you simply close the client window, or click the × button of the bar at the top in full screen, the connection is disconnected, but the session is not closed. Windows says so as well: programs keep running on the remote computer after you disconnect, and you can reconnect to the remote session later by signing in again. This is useful if a program has to keep running while you are away, and next time you continue where you left off.
When you are done and nothing needs to keep running, sign out: on the server, click the user icon in the Start menu and choose Sign out, or run the logoff command. This closes your programs, and the session no longer takes up one of the two simultaneous sessions.
Security: how to protect RDP access
An RDP port reachable from the internet is a common target: automated programs constantly try usernames and passwords on it. The most important steps:
- A strong, unique password. At least 16 characters that you use nowhere else; a password manager helps a lot. We wrote about good passwords in this article. After your first login, change the password you received (Ctrl+Alt+End, then Change a password).
- Network Level Authentication (NLA). With this, the server checks the login details before the session is set up. It is on by default; to check it, press Win+R on the server and run
SystemPropertiesRemote: on the Remote tab, Allow connections only from computers running Remote Desktop with Network Level Authentication (recommended) should be ticked. - Windows Update. RDP has had serious vulnerabilities too, so install the monthly security updates regularly; the server may restart after an update.
- Restricting access. This is the most effective step, see below.
Failed login attempts are shown in the server’s Event Viewer, in the Security log, as events with ID 4625.
Restricting RDP access in Windows Firewall
If you work from a fixed IP address (for example your office internet connection), allow remote desktop from that address only:
- On the server, press Win+R and run
wf.msc. Windows Defender Firewall with Advanced Security opens. - Under Inbound Rules, double-click the Remote Desktop - User Mode (TCP-In) rule.
- On the Scope tab, under Remote IP address, select These IP addresses, add your own IP address with Add…, then click OK.
- Set the same for the Remote Desktop - User Mode (UDP-In) rule as well.
The same from PowerShell (as administrator), regardless of the Windows language, with two allowed addresses:
Set-NetFirewallRule -Name RemoteDesktop-UserMode-In-TCP,RemoteDesktop-UserMode-In-UDP -RemoteAddress 198.51.100.7,198.51.100.8
To remove the restriction, run the same command with -RemoteAddress Any. On our test machine the setting took effect immediately: the client could not connect from an address that was not allowed, but could from an allowed one.
Be careful: if your home or mobile internet IP address changes, the restriction locks you out too. Before saving, check which address you are connecting from now, and if you work from several places, add every address. If you have no fixed IP address, put remote desktop behind a VPN and allow only the VPN’s address in the firewall; our article on setting up your own VPN server covers this. If you have locked yourself out, contact us and we will help you regain access.
Is it worth changing the port?
Changing port 3389 to another number reduces the automated attempts you see in the logs, but it gives no real protection: port scanners find non-standard ports too. It is fine as an extra, but it does not replace a strong password and an IP restriction. If you change it anyway, first allow the new port in Windows Firewall, and only close the old connection once you can log in on the new port; after that you also have to give the port in the client (203.0.113.10:new_port).
Common errors
“Remote Desktop can’t connect to the remote computer for one of these reasons…” The client cannot reach the server. Check the IP address and the port. If the server is restarting (for example after installing Windows updates), wait a few minutes and try again; after a larger update this can take longer. If you have set up an IP restriction, check whether your own IP address has changed. If none of this helps, contact us.
“Your credentials did not work”, “The logon attempt failed”. The username or password is wrong. Watch out for Caps Lock and the keyboard layout (on a Hungarian or German keyboard layout, z and y are swapped). If the client puts your own computer’s name in front of the username, write it like this for the server’s local account: .\Administrator.
“An authentication error has occurred” mentioning CredSSP. According to the error message, “This could be due to CredSSP encryption oracle remediation”: the client and the server are at different update levels. Install the Windows updates on both sides. Don’t use the workaround found on the internet (setting the encryption protection to “Vulnerable”) permanently, as it turns off exactly the protection that the update introduced.
Black screen after login. On the first login or after an update, Windows sometimes spends minutes preparing the session, so wait a little first. If nothing changes, disconnect and connect again. If the problem returns, turn off Persistent bitmap caching on the client’s Experience tab and try connecting with a lower resolution. If that doesn’t help either, contact us and we will look at the server.
Too many users signed in. If both sessions are taken (for example by two disconnected sessions that were never signed out), a third one cannot log in. Windows then offers to disconnect an existing session; the lasting fix is to sign out when you finish working.
You connect to a Linux VPS over SSH, not with remote desktop; this is covered in the article on connecting to a VPS via SSH. We wrote about choosing a Windows VPS, licensing and backups in our guide to renting a Windows VPS.