How to enter IP:12230 correctly in every Remote Desktop app
Where the port number goes in mstsc, Windows App, Remmina, xfreerdp and mobile Remote Desktop apps, plus the small typing mistakes that stop RDP port 12230 from working.
- Beginner
- Windows VPS · Admin RDP
- 4 min read
RunRacks Windows VPS and Admin RDP servers accept Remote Desktop on port 12230. Every RDP app needs that port, but each one asks for it in a slightly different place. This guide shows the exact format for the common apps and the small mistakes that cause most "can't connect" errors.
The examples use the address 203.0.113.10. Replace it with your server's IP from the Dashboard.
Before you start
- Your server's IP address, username and password, from the service page in the Dashboard.
- The server should show as Running.
- The rule to remember: IP, colon, port, no spaces. For example
203.0.113.10:12230.
The correct format
203.0.113.10:12230- A single colon
:between the IP and the port. - No spaces anywhere.
- No
http://,https://orrdp://in front. - Digits only in the port:
12230.
If the app has a separate port field, put 203.0.113.10 in the address or host field and 12230 in the port field. Do not put the port in both places.
Remote Desktop Connection on Windows (mstsc)
- Press Win + R, type
mstsc, press Enter. - In Computer, type
203.0.113.10:12230. - Click Connect.
From PowerShell or a shortcut, the same address goes after /v::
mstsc /v:203.0.113.10:12230If you save an .rdp file, the address line inside it should read:
full address:s:203.0.113.10:12230Windows App on Windows, Mac, iPhone, iPad and Android
Microsoft's Windows App (formerly Microsoft Remote Desktop) uses one field for the address and port.
- Click or tap + and choose Add PC.
- In PC name, enter
203.0.113.10:12230. - Add or choose a user account, then save.
- Open the PC tile to connect.
The Friendly name field is just a label. The port must go in PC name. For more detail on the Mac version, see Windows App on Mac for Remote Desktop.
Remmina on Linux
- Open Remmina and click + to create a connection profile.
- Set Protocol to RDP - Remote Desktop Protocol.
- In Server, enter
203.0.113.10:12230. - Enter the username and password, then Save and Connect.
You can also type 203.0.113.10:12230 into the quick-connect bar with RDP selected.
xfreerdp on the Linux command line
FreeRDP accepts the port either in the address or as a separate option. Both of these work:
xfreerdp /v:203.0.113.10:12230 /u:adminxfreerdp /v:203.0.113.10 /port:12230 /u:adminOn newer FreeRDP 3 packages the command may be xfreerdp3 or sdl-freerdp. The options are the same. See Use xfreerdp from the Linux command line for more options.
Other apps with a separate port field
Some third-party RDP clients and connection managers show Host and Port as two fields. In that case:
- Host:
203.0.113.10 - Port:
12230
If the port field is pre-filled with 3389, change it. Leaving 3389 there is the most common mistake with these apps.
IPv6 addresses
If you connect over IPv6, wrap the address in square brackets so the app can tell where the address ends and the port begins:
[2001:db8::10]:12230Without brackets, the colons in the IPv6 address confuse the parser.
Common mistakes
- Port left off:
203.0.113.10on its own makes the app try 3389, which is closed. - Wrong separator:
203.0.113.10,12230,203.0.113.10;12230or203.0.113.10 12230will fail. Use a colon. - Spaces after copying: copying from an email or chat can add a space before or after the address. Retype it if in doubt.
- Wrong port:
1223,12320or12330are easy typos. Check every digit. - Port in the username field: the username is just the name, for example
Administratoror the user shown in your Dashboard. - Typing the domain with the port in a browser: RDP is not a web page. Opening
203.0.113.10:12230in Chrome will not work.
Check it works
If an app still refuses to connect, rule out the network with a quick port test from the same computer:
Test-NetConnection 203.0.113.10 -Port 12230 -InformationLevel QuietTrue means the server is reachable and the problem is in the app settings or credentials. False means the network path is blocked. On a Mac or Linux, use nc -vz -w 5 203.0.113.10 12230.
Troubleshooting
- mstsc says "the computer can't be found": the address has a typo or extra characters. Retype it as
203.0.113.10:12230. - Windows App shows error 0x204 on a Mac: usually the port is missing or blocked. Check the PC name, then test the port.
- Remmina connects then closes immediately: try setting Security protocol negotiation to NLA in the profile's advanced settings.
- It worked yesterday, not today: the saved address may have been edited. Open the saved connection and check the port is still there.
Next steps
- Save the connection so you never retype it: Save an RDP connection shortcut.
- Port test failed? Follow Test whether RDP port 12230 is reachable.
- Read the overview: RunRacks RDP port 12230.
- Compare Windows Admin RDP 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