Check that Windows is listening on RDP port 12230
Confirm from inside the server that Remote Desktop is configured for port 12230, the service is running and Windows is actually listening, then fix any mismatch.
- Intermediate
- Windows VPS · Admin RDP
- 4 min read
If a port test from outside fails, the next question is whether Windows is listening on TCP 12230 at all. This guide checks three things from inside the server: the configured port in the registry, the Remote Desktop service, and the live listening socket. When they disagree, you will know exactly what to fix.
Before you start
- A way into the server. If Remote Desktop is down, open the browser console from the control panel in your Dashboard.
- An administrator account on Windows.
- PowerShell running as Administrator. Right-click Start and choose Terminal (Admin) or Windows PowerShell (Admin).
Check the configured port
Remote Desktop reads its port from the registry when its service starts:
Get-ItemProperty 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp' -Name PortNumberExpected result:
PortNumber : 12230If you see 3389 or any other number, someone changed it. Follow Restore Remote Desktop to port 12230 after changing it.
Also check that Remote Desktop connections are allowed at all:
Get-ItemProperty 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server' -Name fDenyTSConnectionsfDenyTSConnections : 0 means connections are allowed. 1 means Remote Desktop is turned off. You can turn it back on with:
Set-ItemProperty 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server' -Name fDenyTSConnections -Value 0Check the Remote Desktop service
The service behind Remote Desktop is Remote Desktop Services, short name TermService:
Get-Service TermService, UmRdpService | Format-Table Name, Status, StartTypeBoth should show Running. TermService should normally have a start type of Manual or Automatic; Windows starts it when needed.
If it is stopped, start it:
Start-Service TermServiceIf it will not start, look in Event Viewer under Windows Logs → System for errors from the Service Control Manager or TermService. See Read Event Viewer logs on Windows Server.
Check what is listening
Now check the live socket. With PowerShell:
Get-NetTCPConnection -LocalPort 12230 -State Listen |
Format-Table LocalAddress, LocalPort, State, OwningProcessYou should see one or two lines (for IPv4 0.0.0.0 and IPv6 ::), all in state Listen.
The classic netstat command shows the same thing and works in Command Prompt too:
netstat -ano | findstr :12230Expected output looks like:
TCP 0.0.0.0:12230 0.0.0.0:0 LISTENING 1188
TCP [::]:12230 [::]:0 LISTENING 1188The last number is the process ID (PID). Confirm it belongs to Remote Desktop:
Get-CimInstance Win32_Service -Filter "Name='TermService'" |
Select-Object Name, ProcessIdThe ProcessId should match the PID from netstat. Remote Desktop runs inside a shared svchost.exe process, so the process name alone is not enough to identify it.
Fix mismatches
Restarting the Remote Desktop service disconnects every session, including yours. Keep the browser console open while you work through these fixes.
Compare the three results and act on the first one that is wrong:
- Registry is not 12230: set it back and restart the service. See Restore Remote Desktop to port 12230.
- Registry is 12230, but nothing listens: the service has not picked up the setting, or it is stopped. Restart it:
Restart-Service TermService -ForceThis drops any open Remote Desktop session, including yours, so run it from the browser console if you can.
- Something else owns port 12230: if the PID belongs to another program, that program grabbed the port first. Find it with
Get-Process -Id 1188(use your PID), reconfigure or stop it, then restart TermService. - Everything is correct, but outside tests still fail: Windows is listening, so check the firewall rule for 12230 next. See Allow RDP port 12230 in Windows Firewall.
If the service still refuses to start, restart the whole server from the Dashboard control panel. A full reboot clears most stuck states.
Check it works
Test the port from the server itself first. This skips the network and the external firewall path:
Test-NetConnection 127.0.0.1 -Port 12230 -InformationLevel QuietTrue means Remote Desktop accepts connections locally. Then test from your own computer:
Test-NetConnection 203.0.113.10 -Port 12230If the local test passes and the remote test fails, the cause is the firewall or the network between you and the server.
Troubleshooting
- `Get-NetTCPConnection` returns an error "No matching MSFT_NetTCPConnection objects": nothing is listening on 12230. Work through the registry and service checks above.
- Listening only on `::` (IPv6): that is normal on many systems. The
::socket also accepts IPv4 on dual-stack Windows. Test with the IPv4 address to be sure. - TermService stops again right after starting: a broken certificate or corrupt system file can cause this. Check the System log, then see Repair Windows with SFC and DISM.
- Listening and firewall open, but login fails: the network side is fine. Check the username and password from the Dashboard.
Next steps
- Test from outside: Test whether RDP port 12230 is reachable.
- General connection fixes: Fix Remote Desktop can't connect.
- Compare Windows VPS and 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
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