Forum Discussion
RDP Not Working | Not listening the port 3389 in windows server 2016
I'd close this one by marking answers and start a new thread for this new issue.
Dave Patrick Just to throw my hat in the ring here, we are experiencing the exact same issue as described. It is impacting dozens of machines (win 10) where users can no longer RDP to their system. It is the same symptoms laid out by the OP.. the service is running, but the machine does not open the port. We have tried literally everything, including windows repair, with no success. The only solution has been to reimage the desktop.
Might try remove role, reboot add role back, or better yet stand up a new one for replacement.
Dave Patrick any more suggestions for this issue to fix it ?.
- It worked well the last time we encountered an issue that was very widespread. Everyone piled into the same thread, and MS ended up resolving the issue. (https://social.technet.microsoft.com/Forums/windows/en-US/4a782e40-bbd8-40b7-869d-68e3dfd1a5b4/windows-update-scan-high-memory-usage?forum=w7itproperf) What sense would it make to create multiple threads with the exact same problem?
Sounds good. Good luck with that approach.
Dave Patrick I don't agree that a new thread should be started. It's the same issue, and we will just end up with a bunch of threads people will have to search through to find one that may be answered. We should combine all the responses here so there is one place to track this issue.
I'd start a new thread for your issue.
