3389 not listening on 1 server 2019 - Microsoft Q&A
3389 port not listening RDP port not listening on Windows 10 problem makes users unable to remotely control another PC. To help users troubleshoot the annoying problem, here we sort out two effective ways..port 3389 vulnerability
Edit: A netstat shows 3389 not listening until the server or service is restarted. No firewall in place. The port just stops. Edit: We found a workaround, it appears to be some kind of bug in 2022 they don't want to admit to. The solution is to set a GPO that will automatically set the registry key fdenytsconnections to 0 rather than 1 on a ...33890 schneider
The permissions on the MachineKeys folder is correct and the registry specifies port 3389 as being the one it should listen on. There is nothing else using the port and the firewall rules permit the access. I have also tried disabling the firewall but the issue is it is not listening and I can't see any errors in event viewer.
