Connect to RDP port 12230 from office, hotel or school Wi-Fi
Some office, hotel and campus networks block uncommon outbound ports such as 12230. Learn how to confirm the block and the safe ways to reach your server anyway.
- Intermediate
- Windows VPS · Admin RDP
- 5 min read
Remote Desktop works from home but fails from the office, a hotel or a campus network. In most cases your server is fine and the local network blocks outbound connections to uncommon ports such as TCP 12230. This guide shows how to prove that, what to ask the network owner, and which workarounds are safe to use.
Why some networks block port 12230
Managed networks often allow only a short list of outbound ports, typically web (80 and 443), DNS and sometimes email. Everything else is dropped. The aim is to stop malware calling home and to keep staff or guests on approved services.
RunRacks moves Remote Desktop off the default port 3389 to cut down bot traffic. A strict network that only allows web ports blocks 12230 for the same reason it would block 3389: it is not on the list.
Signs that the network is the cause:
- Remote Desktop works from home or mobile data, but not from this network.
- The connection times out rather than showing a login error.
- Other people on the same network report the same problem with other remote tools.
Before you start
- Your server's IP address, username and password from the Dashboard.
- A phone with mobile data and hotspot (tethering) enabled, for the comparison test.
- Permission to use the network for remote access. On a work or school network, check the acceptable-use policy before you try any workaround.
Do not try to sneak around a corporate firewall without permission. Many employers treat that as a policy breach. Ask IT first.
Confirm the block with a hotspot test
- On the restricted network, open PowerShell and test the port:
Test-NetConnection 203.0.113.10 -Port 12230 -InformationLevel Quiet- Note the result (
TrueorFalse). - Disconnect from the Wi-Fi, connect your laptop to your phone's hotspot and run the same command.
- Compare the two results.
If the hotspot test returns True and the Wi-Fi test returns False, the restricted network is blocking the port. If both fail, the problem is somewhere else. Follow Test whether RDP port 12230 is reachable for the next checks.
On a Mac, use nc -vz -w 5 203.0.113.10 12230 for both tests instead.
Ask the network owner to allow TCP 12230
The clean fix is a firewall exception. Network teams handle these requests all the time. Give them exactly what they need:
Please allow outbound TCP traffic to 203.0.113.10 on port 12230.
Purpose: Remote Desktop (RDP) to our company Windows server.
Source: my laptop (or the office network).
Protocol: TCP only. No inbound rule is needed.Asking for a single destination IP and port is more likely to be approved than asking to "open port 12230" for everyone. For a hotel or conference venue, the front desk usually cannot change the firewall. Use one of the workarounds below instead.
Workaround 1: use a mobile hotspot
For short sessions, a phone hotspot is the simplest option. RDP uses little data for normal office work, but video, large file copies and high screen resolutions use more. Lower the display size and colour depth in the RDP app if your data plan is limited.
Workaround 2: connect through a VPN
A VPN wraps all your traffic in a tunnel to the VPN server. If the network allows that VPN, your RDP connection travels inside it.
- Company VPN: if your employer provides one, connect to it first and then open Remote Desktop to
203.0.113.10:12230. This is often the approved route. - Your own VPN server: you can run WireGuard or OpenVPN on a separate Linux VPS and route RDP through it. See Remote Desktop over a WireGuard VPN.
Some strict networks also block VPN protocols. OpenVPN over TCP port 443 tends to pass where other VPNs fail, because it looks like normal web traffic on the wire.
Workaround 3: use an SSH tunnel
If outbound SSH is allowed, you can carry RDP inside an SSH connection. This needs an SSH server reachable from the restricted network, such as OpenSSH on your Windows VPS or on a Linux VPS. The full setup is in Tunnel Remote Desktop port 12230 through SSH.
Once the tunnel is open, you connect your RDP app to a local address such as 127.0.0.1:13389, and the tunnel forwards it to port 12230 on the server.
If the network blocks SSH on port 22 too, the tunnel will not work unless the SSH server also listens on a port the network allows.
Check it works
After IT adds the exception, or once your VPN or tunnel is up, test again from the restricted network:
Test-NetConnection 203.0.113.10 -Port 12230TcpTestSucceeded : True means the path is open. Then connect with your RDP app as usual, using 203.0.113.10:12230, or the local tunnel address if you use SSH.
Troubleshooting
- The hotspot test also fails: the network is not the cause. Restart the server from the Dashboard and check the firewall from the browser console.
- IT approved the request, but it still fails: some offices also run a web proxy or a second firewall at another site. Send IT the output of
Test-NetConnectionso they can trace it. - The VPN connects, but RDP still times out: your VPN may use split tunnelling and send only some traffic through the tunnel. Ask the VPN admin to include the server's IP.
- RDP connects but is very slow on hotel Wi-Fi: shared guest networks are often congested. Lower the resolution and turn off visual effects on the Experience tab in mstsc.
Next steps
- Reduce what is exposed once you can connect: Restrict RDP port 12230 to your own IP addresses.
- See how RDP connections work on RunRacks: RunRacks RDP port 12230.
- Need a desktop you can reach from anywhere? See 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
Troubleshooting
Fix Nginx 413 Request Entity Too Large
Nginx returns 413 Request Entity Too Large when an upload is bigger than client_max_body_size. Raise the limit for one site or the whole server, match PHP's limits, and test.
- Beginner
- Linux VPS
- 5 min read
Troubleshooting
Is your ISP or router blocking port 12230? How to tell
Work out whether your internet provider, home router, parental controls or a proxy is blocking RDP port 12230, and collect the details support needs to help.
- Intermediate
- Windows VPS · Admin RDP
- 5 min read
Troubleshooting
Fix "Your credentials did not work" in Remote Desktop
Fix rejected RDP logins: username format, the right password, stale saved credentials, account lockout and Remote Desktop permissions.
- Beginner
- Windows VPS · Admin RDP
- 3 min read