RDP (Remote Desktop Protocol) is Microsoft’s solution for working on a Windows machine as if you were sitting in front of it, whilst in fact you are accessing it from another computer, laptop or mobile phone. It is part of Windows; there is no need to purchase separate software, and it is used to manage Windows servers, including rented Windows VPSs.

In this guide, we explain how RDP works, what it can be used for, how to connect to a computer or server from various devices, how to secure the connection, what to do if the connection is slow or fails to establish, and when another remote access solution might be a better choice.

How does RDP work?

The RDP operates on a client–server basis:

• The RDP service runs on the remote machine (host). This could be a Windows Server, a Windows VPS or a Windows 10/11 Pro computer.
• The client program runs on your own device, displaying the remote machine’s screen and relaying keyboard and mouse inputs.

The programs run on the remote machine; only the changes to the screen are sent to your device, in compressed form. This means that even a resource-intensive application running on a powerful server can be used smoothly on a low-spec laptop or tablet, and therefore requires surprisingly little bandwidth: just a few Mbps is enough for office work.

By default, RDP accepts connections on TCP and UDP port 3389 and encrypts traffic using TLS. Modern versions also use network-level authentication (NLA): the user is authenticated before the session is even established, which reduces the attack surface.

In addition to the image, RDP also transmits many other things via so-called virtual channels:

• Clipboard: you can copy text and files between your own computer and a remote computer,
• Drives: you can make a folder on your own computer accessible on a remote computer,
• Printers: you can print from a remote computer to your local printer,
• audio, microphone, multiple monitors.

What can it be used for?

• Server management: Windows Servers and Windows VPSs are almost always managed via RDP.
• Centralising business software: you run an accounting or ERP program on a server, and staff can access it via remote desktop from anywhere. The data remains on the server, not on laptops.
• Working from home: you can access your office computer from home, along with the programs and files stored on it.
• Programs running continuously: for example, MetaTrader trading robots or scheduled processes on a VPS, which you check from time to time via remote desktop.
• Development and testing: a Windows test environment that doesn’t put a strain on your own computer.

What do you need for RDP?

On the remote machine

• Windows Server (any edition) or Windows 10/11 Pro, Enterprise or Education. You cannot connect to Windows Home editions via RDP; you can only use them to connect to other machines as a client.
• Remote Desktop is enabled (in Windows 11: Settings › System › Remote Desktop).
• With a user account password (you cannot log in via RDP with a blank password).
• Network access: the Windows firewall must allow remote desktop access, and if the machine is behind a router, it must also be accessible via the router. On a rented Windows VPS, these are configured by default.

Licences

RDP itself is free; it is part of Windows. Two administrator sessions can be connected to a Windows Server at the same time without a separate licence; Remote Desktop Services (RDS) client licences are required for more than two concurrent users. On a Windows 10/11 Pro machine, only one user can work at a time.

On your own device

Tool	Client
Windows	Built-in Remote Desktop Connection (mstsc)
macOS	Microsoft Windows App (from the Mac App Store)
iPhone, iPad	Microsoft Windows App
Android	Microsoft Windows App
Linux	Remmina or FreeRDP

Microsoft replaced its previous Remote Desktop apps with the Windows App on macOS, iOS and Android in 2024–2025.

Step-by-step guide to getting started

1. Obtain the following details: the IP address or name of the remote machine, the username and the password. With an aWh Windows VPS, you’ll receive these via email once the server has been set up.
2. Launch the client: on Windows, press the Win+R keys and type mstsc. On a Mac or mobile device, open the Windows App and add a new computer (PC).
3. Enter the address, and if the service is not running on port 3389, include the port number as well, separated by a colon (for example, 203.0.113.10:3389).
4. Configure the display settings (under ‘Display settings’): resolution, multiple monitors, and, on the ‘Local Resources’ tab, sharing of the clipboard, drives and printers.
5. Log in and enter your username and password.
6. Accept the certificate. When connecting for the first time, the client may warn you that the server’s certificate cannot be verified. If you are certain that you are connecting to the correct address, you can accept it; if the warning reappears unexpectedly later on, this is a cause for concern.

Copying files: the simplest method is to use the clipboard (you copy a file on your own computer and paste it onto the remote computer); for larger volumes, use a shared drive, which appears as a ‘Mapped Drive’ in the remote computer’s File Explorer.

Log out or disconnect? If you simply close the window, your session and programs will continue to run on the server, and you can pick up where you left off next time. If you log out, the programs will close. For an application that runs continuously (such as a trading bot), you should therefore simply disconnect.

Security: how to protect RDP

An RDP port left open on the internet is one of the most common targets for attacks: automated bots constantly try to guess usernames and passwords, and a significant proportion of ransomware attacks begin in this way. A newly installed server is targeted by these attempts within the first few hours.

1. Restrict access. The most effective measure is to allow port 3389 in the Windows firewall only from your own static IP addresses. If you do not have a static IP address, place RDP behind a VPN, or use Remote Desktop Gateway, which provides access via HTTPS with additional authentication.
2. A strong, unique password. At least 16 characters, using a password manager.
3. Account lockout policy. After a few failed attempts, the account should be locked for a period of time.
4. Your own administrator account. Rename or disable the default ‘Administrator’ account and work with an account of your own choosing.
5. NLA enabled. Do not disable network-level authentication.
6. Updates. There have also been serious vulnerabilities in RDP (the best-known being BlueKeep in 2019), so always install the monthly Windows security updates.
7. Logs. You can see failed login attempts in the Windows Event Log (Security log, event ID 4625).

Changing the port to a different number reduces the number of automated attempts visible in the logs, but this alone does not provide protection: port scanners will still find non-standard ports. It is a useful additional measure, but it is no substitute for IP restrictions and a strong password.

RDP connections are encrypted on public Wi-Fi, but you should pay particular attention to certificate warnings in such cases and, if possible, connect via a VPN.

If your connection is slow

• In the client settings, on the ‘User Experience’ tab, select the profile that matches your connection speed, or disable the background image, animations and text smoothing.
• Reduce the resolution and colour depth, and avoid using multiple monitors unless absolutely necessary.
• Don’t copy large files whilst you’re working, as this will take up bandwidth that could otherwise be used for image transfer.
• When using mobile data or a weak Wi-Fi connection, it often helps if the client uses only TCP instead of UDP, or vice versa.
• If the remote machine itself is slow (high CPU or memory usage), RDP won’t be any faster either: check the Task Manager on the server.

If the connection cannot be established

• “Remote Desktop cannot connect to the remote computer”: check the address and port, ensure the remote machine is running, check that Remote Desktop is enabled, and verify that the firewall (on the machine and on the network) is allowing the connection. If you have set up IP restrictions, your own IP address may have changed.
• “Authentication details did not work”: check the username (for local accounts, you may need to use the format .\felhasználónév) and the password, and ensure the account is not locked.
• Authentication error or CredSSP error message: the client and server are on different update levels; install the updates on both sides.
• Too many users: if there are already two active sessions on the server, a third cannot log in without RDS licences; log out of an old session.

If you’ve locked yourself out of an aWh Windows VPS (for example, due to an incorrect firewall rule), please contact us and we’ll help you regain access.

RDP or another solution?

Solution	What is it for?	Comment
RDP	Daily use of Windows servers and computers, multiple users	The Windows part opens a separate session quickly
TeamViewer, AnyDesk	Remote support: taking control of a user’s computer	Shows the existing screen; paid version for business use
VNC	Sharing a physical monitor on a single machine, Linux	Slower; encryption only available with an add-on (such as an SSH tunnel)
SSH	Command-line management of Linux servers	No graphical interface, very little bandwidth
XRDP, X2Go	Graphical interface on a Linux server	See our guide on remote desktop access for Linux VPS

VPN and RDP are not alternatives to one another, but rather complement each other well: the VPN opens an encrypted tunnel to the network, whilst RDP provides remote desktop access via this tunnel, meaning that the RDP port is not visible from the internet.

Remote Desktop on a Windows VPS

If you want to use a Windows machine running in a data centre that’s always on via remote desktop, a Windows VPS is the simplest solution: you don’t need to keep a computer at home or in the office switched on all the time; the server runs on a stable power supply and network, and is accessible from anywhere. aWh’s Windows VPS plans include a Windows Server licence, RDP access, NVMe SSD storage, unlimited traffic, daily backups and DDoS protection, from €22.85 per month (excluding VAT). We’ve written in detail about how to choose in our Windows VPS rental guide.

Frequently Asked Questions

Is RDP free?

Yes, Windows itself and the client programs are free. On Windows Server, RDS client licences are required for more than two concurrent users.

Can I connect to a Windows computer from a Mac, a Linux machine or a mobile phone?

Yes. On Mac, iPhone, iPad and Android using Microsoft’s free Windows App, and on Linux using the Remmina or FreeRDP client.

Can you connect to Windows Home via RDP?

No, Home editions can only use RDP as clients. To act as a remote desktop host, you need Windows Pro, Enterprise, Education or Windows Server.

What sort of internet connection do you need?

For office work, a few Mbps is enough, as only screen updates are transmitted. For video, graphics work and multiple monitors, you need more. Latency (ping) is just as important as bandwidth.

Which port does RDP use, and do I need to change it?

By default, TCP and UDP port 3389. You can change this, but it is no substitute for proper security: restrict access to your own IP addresses or a VPN.

Can RDP be used on a Linux server?

Yes, with the XRDP server program, the graphical interface of a Linux server can also be accessed using the Windows Remote Desktop client. Linux servers are usually managed via SSH; a graphical interface is only required for specific purposes.

Is RDP secure?

If you don’t leave the port open to the internet, use a strong password and account locking, and install the machine’s updates, then yes. Most RDP-based break-ins can be traced back to ports that are open to everyone and weak passwords.

What should I do if I’ve forgotten my VPS password?

If you’re using an aWh Windows VPS, please contact us and we’ll help you regain access. Once you’ve done that, set a new, strong password and store it in a password manager.

• remote desktop
• windows server
• vps
• guides
• for beginners