Changed RDP listening port, not 3389 wont work

DOYAM

New Member
Messages
7
Changed RDP listening port, now no ports work

I just built a new HTPC, put Windows 8.1 on it, had RDP working fine for days. Even out of my house with port forwarding. Once I got everything where I wanted it, the last step was to change the port for security. I changed the registry Port Number (at HKEY_LOCAL_MACHINE, SYSTEM, CurrentControlSet, Control, Terminal Server, WinStations and RDP-Tcp), to a 5 digit number starting with 13 so its within the limits (also, I used to use the same port previously with Windows 7). Restarted and I could not connect. It did not work. So I tried putting it back to 3389 and its broken now too. I have a laptop on 8.1 also and changed it at the same time, now I have the same issues. I have tried everything I can think of. Check and even turned off the Firewall, used netstat -a and it seems to be listening on the correct port.
It seems to me there is something else at play here. Can anyone help me? This is at a bad time since I have leaving town for a few days and need access, I have to use VNC.
Help please.

FYI, I posted this exact same question here and have gone through some diagnostic steps to no avail: https://social.technet.microsoft.co...tworking#45858022-e0f2-442d-80cc-c24c20f3b2e7
 
Last edited:
Sorry for the late reply. As I mentioned I had it working great before and I have configured my firewall and router. The router does not matter as I am only trying to get it working inside my network right now.
 
Did you remember to use the correct port when requesting a remote desktop connection: 192.168.1.10:3391 ???
Make sure the firewall is configured to listen and accept connections via the new port.
 
Thank you for all your input. I just tried to change it using 3389, 3390 and 3391. I am pretty sure the default RDP port is 3389 but it doesnt really matter. I changed it in regedit as I described above, I changed it in the router's settings as well and I turned off the firewall to make sure that wasnt it. I am doing all this remotely via TightVNC so I know how to configure these things. It like when I changed that listening port, it broke some other setting and I cannot put it back.
 
Thank you guys for your help again. I think this was my mistake and I was not clicking "decimal" when I changed the port. It was on "hexidecimal". It works now.
 
Back
Top