What is RDP? Remote Desktop explained for beginners
A beginner's guide to the Remote Desktop Protocol: what you see when you connect, which app to use on each device, and why RunRacks servers use port 12230.
- Beginner
- Windows VPS · Admin RDP
- 4 min read
RDP, the Remote Desktop Protocol, is how you use a Windows server that sits in a data center. You open an app on your own device, enter the server's address, and the server's Windows desktop appears in a window. This guide explains what happens when you connect, which app to use on each device, and why RunRacks servers listen on port 12230.
Before you start
To follow along with a real server you need:
- A RunRacks Windows VPS or Windows Admin RDP.
- The server's IP address, username and password, all shown on the service page in your Dashboard.
You can read this guide without a server to understand the idea first.
How Remote Desktop works
RDP is a network protocol created by Microsoft. When you connect:
- Your device, the client, opens an encrypted connection to the server.
- You sign in with a Windows username and password.
- The server runs your session and sends screen updates to your client.
- Your client sends keyboard and mouse input back.
All programs run on the server, not on your device. Your device only displays the picture and sends your clicks. That is why a modest laptop or even a phone can control a powerful server, and why the server keeps running programs after you disconnect.
What you see when you connect
After you sign in, you see a normal Windows desktop: the Start menu, taskbar, File Explorer and any apps you install. On a Windows VPS you may also see Server Manager open at sign-in. On an Admin RDP you see a regular desktop for daily work.
Some useful behaviours:
- Clipboard: copy and paste between your device and the server usually works out of the box.
- Full screen: the session can fill your screen. A bar at the top lets you minimise or leave it.
- Disconnect vs sign out: closing the RDP window disconnects and keeps your programs running. Choosing Sign out in Windows closes them.
The apps you need on each device
- Windows 10 and 11: Remote Desktop Connection is built in. Press Win + R, type
mstscand press Enter. - macOS: install the free Windows App (formerly Microsoft Remote Desktop) from the Mac App Store.
- iPhone and iPad: install Windows App from the App Store.
- Android: install Microsoft's Remote Desktop or Windows App from Google Play.
- Linux desktops: use an RDP client such as Remmina.
Each app asks for the same things: the address, the username and the password.
Why RunRacks uses port 12230
Every network service listens on a numbered port. Remote Desktop normally uses port 3389. Automated bots scan the internet for 3389 all day and try common passwords against it.
RunRacks Windows VPS and Admin RDP servers accept Remote Desktop on TCP port 12230 instead. This cuts out most of that background scanning. It does not replace a strong password, but it means fewer failed logins and less noise in your logs.
You connect by adding the port to the address with a colon:
203.0.113.10:12230On Windows you can also start the connection from PowerShell:
mstsc /v:203.0.113.10:12230Guides from other sites usually assume port 3389. On a RunRacks server, always use 12230.
Check it works
- Open your Remote Desktop app and enter
your-server-ip:12230. - Sign in with the username and password from the Dashboard.
- Accept the certificate prompt the first time. RunRacks servers use a self-signed certificate, which is normal.
- You should see the Windows desktop within a few seconds.
Troubleshooting
- "Remote Desktop can't connect to the remote computer": the most common cause is a missing port. Make sure the address ends in
:12230. - "The credentials did not work": copy the username and password from the Dashboard again and watch for extra spaces.
- Black screen after signing in: wait a few seconds. If it stays black, press Ctrl + Alt + End and choose Cancel.
- Works at home but not at work: some office networks block unusual outbound ports. Try another network, such as a phone hotspot, to confirm.
- Cannot reach the server at all: check it shows as running in the Dashboard. If RDP is broken, the browser console in the control panel still lets you in.
Next steps
- Full connection walkthrough: RunRacks RDP port 12230.
- Client setup on every device: connect to your Admin RDP.
- Harden logins next: secure Remote Desktop on Windows Server.
- Compare plans for Windows Admin RDP.
Was this guide helpful?
Still stuck?
Ask RunRacks AI for a quick answer, or open a ticket and our team will take a look at your server.
Related guides
Getting started
Edit files with nano: a beginner's guide
Open, edit, search and save files with the nano text editor on a Linux server, including cutting and pasting lines, showing line numbers and safely editing system config files with sudo.
- Beginner
- Linux VPS
- 5 min read
Getting started
Your first hour with a new RunRacks server
A step-by-step roadmap for the first hour after your RunRacks server is delivered, from finding your login details to changing the password, updating the OS and picking your next guides.
- Beginner
- All
- 5 min read
Getting started
How to choose a server location
Pick a data center location based on where your users, broker or team are, confirm it with ping tests, and weigh the legal and latency points that come with each choice.
- Beginner
- All
- 4 min read