Use Remote Desktop from Windows 10 or 11 Home
Windows 10 and 11 Home can connect to a remote server with Remote Desktop. Here is how to connect to IP:12230 and why Home cannot accept incoming RDP.
- Beginner
- Windows VPS · Admin RDP
- 5 min read
A common worry is that Windows Home cannot use Remote Desktop at all. That is only half true. Home editions cannot accept Remote Desktop connections, but they can make them, which is all you need to reach a RunRacks Windows VPS or Admin RDP server. This guide shows both built-in ways to connect from a Home PC, using port 12230, and explains the host limitation so you are not caught out by it.
Before you start
- A PC running Windows 10 Home or Windows 11 Home (Pro and Enterprise work the same way).
- Your server's IP address, username and password from the Dashboard.
- The server showing as Running in the Dashboard.
RunRacks servers accept Remote Desktop on TCP 12230, not 3389. Every address in this guide ends in :12230.
Client versus host: what Home can and cannot do
Remote Desktop has two sides:
- The client is the app you sit in front of. It sends your keyboard and mouse to the other machine and shows you its screen.
- The host is the machine you connect to. It runs the Remote Desktop service and accepts the login.
Every edition of Windows 10 and 11, including Home, ships with the client. Only Pro, Enterprise and Education can act as a host. On a Home PC, the Settings → System → Remote Desktop page either does not appear or tells you that your edition does not support it.
For a RunRacks server this does not matter. Your PC is the client, and the server is the host. The host is already set up on port 12230.
If you were hoping to reach your Home PC from somewhere else, Microsoft's Remote Desktop is not the tool. You would need to upgrade that PC to Pro or use a different remote-access product. A RunRacks Windows Admin RDP desktop is another option: you work on the server and reach it from anywhere.
Connect with Remote Desktop Connection (mstsc)
Remote Desktop Connection is the classic client and is built into Home.
- Press Win + R, type
mstscand press Enter. You can also search the Start menu for Remote Desktop Connection. - In Computer, enter the address with the port:
203.0.113.10:12230- Click Connect.
- When asked for credentials, choose More choices → Use a different account and enter the username and password from your Dashboard. Without this step, Windows may try your own PC account, which will fail.
- Accept the certificate warning. RunRacks servers use a self-signed certificate, so the warning is expected the first time.
To launch the same connection from a command, for example in a shortcut:
mstsc /v:203.0.113.10:12230Remote Desktop mstsc command-line options explained lists the other switches, such as full screen and custom window sizes.
Connect with Windows App
Microsoft also offers Windows App, a newer client from the Microsoft Store. It keeps a list of your PCs as tiles, which is handy if you manage several servers. Microsoft has been changing which connection types each client supports, so if Windows App does not offer to add a PC by address on your version, use mstsc instead.
- Open the Microsoft Store, search for Windows App and install it.
- Open it and choose + → Add PC (or the equivalent option to add a device by address).
- Enter
203.0.113.10:12230as the PC name, add your credentials and save. - Double-click the tile to connect and accept the certificate.
Save the connection for next time
In mstsc, click Show Options before connecting. Enter the address and username, then click Save As to create an .rdp file on your desktop. Next time you double-click that file and enter the password. Save a Remote Desktop connection as a one-click shortcut covers pinning it to the taskbar.
Check it works
You should land on the server's desktop. Two quick checks confirm you are on the server and not your own PC:
- The desktop background and taskbar look different from yours.
- Running
hostnamein a PowerShell window inside the session shows the server's name, not your PC's.
If the connection fails before a login prompt, test the port from your Home PC in PowerShell:
Test-NetConnection 203.0.113.10 -Port 12230TcpTestSucceeded : True means the port is open.
Troubleshooting
- "Remote Desktop can't connect to the remote computer": the port is missing or wrong. The address must end in
:12230. Then run the port test above. - Guides tell you to "enable Remote Desktop" in Settings and the switch is missing: that switch is for hosting. You do not need it to connect out, so ignore it on a Home PC.
- "The credentials did not work": you probably sent your PC's account. Use More choices → Use a different account and type the server username exactly as shown in the Dashboard. Fix "Your credentials did not work" has more causes.
- Port test fails on one network only: some office, school or hotel networks block unusual ports. Try a phone hotspot to confirm.
Next steps
- Compare the two server types: Windows VPS vs Windows Admin RDP.
- Make launching quicker: Save a Remote Desktop connection as a one-click shortcut.
- Ready for a server? See Windows VPS plans.
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
Windows VPS & RDP
RunRacks RDP port 12230: how to connect to your Windows VPS and Admin RDP
RunRacks Windows VPS and Admin RDP servers accept Remote Desktop on port 12230, not 3389. Here is how to connect from every device and keep the port open.
- Beginner
- Windows VPS · Admin RDP
- 5 min read
Windows VPS & RDP
Allow or block multiple RDP sessions for one user
Understand why a new Remote Desktop login takes over your old session, how the single-session policy works on Windows Server, and which setting suits a team.
- Advanced
- Windows VPS
- 5 min read
Windows VPS & RDP
Create Windows users with Remote Desktop access
Give each person their own Windows login, add them to Remote Desktop Users, test the account and remove access cleanly later.
- Beginner
- Windows VPS · Admin RDP
- 2 min read