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

By RunRacks Team · Published

Every RunRacks Windows VPS and Windows Admin RDP server accepts Remote Desktop connections on TCP port 12230, not the usual Windows port 3389. You connect by adding the port to the address, for example 203.0.113.10:12230. This guide shows how to do that on every common device, how to check the port is reachable, and how to keep it open when you change firewall settings.

Why RunRacks uses port 12230

Port 3389 is the first port automated bots try when they hunt for Windows servers. Moving Remote Desktop to 12230 does not replace a strong password, but it cuts out most of that background noise: fewer failed logins in your event log, fewer account lockouts and less wasted CPU.

Nothing else changes. It is the same Remote Desktop Protocol with the same encryption, and it works with the standard Remote Desktop apps from Microsoft.

Before you start

  • Your server's IP address, username and password. All three are on the service page in your Dashboard.
  • A Remote Desktop app:
  • Windows 10/11: Remote Desktop Connection (mstsc) is built in.
  • macOS, iPhone, iPad, Android: the free Windows App (formerly Microsoft Remote Desktop) from your app store.
  • The server must show as Running in the Dashboard. A freshly ordered server can take a little while to finish installing.

Connect from Windows

  1. Press Win + R, type mstsc and press Enter.
  2. In Computer, type the IP address, a colon and the port:
Text
   203.0.113.10:12230
  1. Click Connect. When asked for credentials, choose More choices → Use a different account and enter the username and password from your Dashboard.
  2. Accept the certificate warning the first time. RunRacks servers use a self-signed certificate, so tick Don't ask me again for connections to this computer if you trust the address.

You can also start the connection from PowerShell or a shortcut:

PowerShell
mstsc /v:203.0.113.10:12230

Connect from macOS

  1. Install Windows App from the Mac App Store and open it.
  2. Click + and choose Add PC.
  3. In PC name, enter 203.0.113.10:12230.
  4. Under Credentials, add your username and password, or leave it on Ask when required.
  5. Save, then double-click the new PC tile to connect. Click Continue on the certificate prompt.

Connect from iPhone, iPad or Android

  1. Install Windows App (iOS) or Remote Desktop / Windows App (Android).
  2. Tap + → Add PC.
  3. Enter 203.0.113.10:12230 as the PC name and add your user account.
  4. Tap the PC to connect and accept the certificate.

A phone works well for quick checks, such as confirming a trading terminal is still running. Use a computer for longer sessions.

Check the port is reachable

If a connection fails, first test whether port 12230 answers at all. On Windows, in PowerShell:

PowerShell
Test-NetConnection 203.0.113.10 -Port 12230

TcpTestSucceeded : True means the port is open and the problem is the login details or the app. False means something is blocking the port.

On macOS or Linux, use nc:

Terminal
nc -vz 203.0.113.10 12230

A line ending in succeeded! or open means the port is reachable.

Keep port 12230 open in Windows Firewall

RunRacks servers ship with a firewall rule that allows 12230. If you change firewall settings, keep that rule. To confirm it exists, open PowerShell as Administrator on the server:

PowerShell
Get-NetFirewallPortFilter -Protocol TCP |
  Where-Object LocalPort -eq 12230 |
  Get-NetFirewallRule |
  Format-Table DisplayName, Enabled, Direction, Action

If nothing is listed, add an allow rule:

PowerShell
New-NetFirewallRule -DisplayName "Remote Desktop (TCP 12230)" `
  -Direction Inbound -Protocol TCP -LocalPort 12230 -Action Allow

You can also check which port Remote Desktop is listening on:

PowerShell
Get-ItemProperty 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp' -Name PortNumber

It should return PortNumber : 12230.

Troubleshooting

  • "Remote Desktop can't connect to the remote computer": you probably left the port off. Make sure the address ends in :12230. Then run the port test above.
  • Port test fails: restart the server from the Dashboard control panel and wait two minutes. If it still fails, log in through the browser console and check the firewall rule.
  • "The credentials did not work": copy the password from the Dashboard again, watching for extra spaces. On Admin RDP, use the exact username shown, not Administrator, if they differ.
  • Your office or school network blocks it: some networks only allow common ports outbound. Try a different network, such as a phone hotspot, to confirm. If that is the cause, ask your network admin to allow outbound TCP 12230.
  • Connected, but the screen is black: wait a few seconds, then press Ctrl + Alt + End and choose Cancel. That usually wakes the session.

Next steps

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.

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

RDP over UDP vs TCP: check and choose the transport

Remote Desktop can carry your session over TCP, UDP or both. Learn how each is used, how to see which one your session runs on, and how to force TCP when UDP misbehaves.

  • Advanced
  • Windows VPS · Admin RDP
  • 5 min read