Has anyone else dealt with a situation where the Remote Desktop Service is running, but the computer isn't listening on port 3389? I've noticed this issue cropping up after Patch Tuesday, but it seems to affect machines regardless of any patches. Currently, we are working around it by using a script to restart the service on our RDS infrastructure, but it's becoming a hassle. Any insights or solutions would be appreciated!
2 Answers
We've been tackling this for a while, especially after shifting from Windows 10 22H2 to 24H2. The 'solution' is oddly simple but kind of baffling. It turns out that while group policy settings should override the registry, the key under "HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlTerminal Server" called "fDenyTSConnections" can still cause issues. If it's set to "1," just change it to "0" and the machine will start listening on 3389 again—no restart needed! I'm curious if setting this key to "0" permanently helps avoid future hiccups since it’s been working for me so far.
This advice worked wonders for us as well! We're still trying to understand why it became an issue, but it's resolved access problems on machines that couldn't be reached before.
If your Remote Desktop (RDP) isn't responding on port 3389, it might be a firewall issue or a problem with the service itself. I recommend checking your firewall rules first, then restarting the "Remote Desktop Services". You can confirm whether port 3389 is listening by running `netstat -an | find "3389"`. That should help narrow down the issue!
Thanks for this tip! I’ve also encountered this issue on Windows 10 22H2 but haven’t seen it on 24H2 just yet. I had a machine where the Group Policy wasn’t enforced, and the remote setting was off, so I suspect that registry key is the root cause. I've found that same key set to 1 on a machine that has faced lockouts, so I’m keen to investigate further.