Forum Discussion
RDP Not Working | Not listening the port 3389 in windows server 2016
Looks like terminal services service is either not running or not listening on port 3389. You could also do
netstat -aon then lookup the PID's in Task Manager\Processes
Dave Patrick Yes, I am not able to see TCP connection on port 3389 and no process task manager for Session Host: Remote desktop service.
However, I have a Remote desktop service that is running fine in services.
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.
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.
I'd close this one by marking answers and start a new thread for this new issue.
Dave Patrick Yes, but now the issue I can see, the fault server not allowing connection on TCP 3389,
even I tried changed Port Number through Registry and tried but still same issue. Is there any other way to fix this issue ?
Each one will need to be diagnosed separately on its own merits or faults.
- I can see the same thing in another machine which I can do RDP.
Here the server not allowing connection on TCP port 3389 (i tried with telnet localhost 3389) it suppose to open a connection but really not.
I need to find a way to fix this issue, as it is a server which we cant make any stand up a new one. Ok then that's the problem. Might try remove role, reboot add role back, or better yet stand up a new one for replacement.
Dave Patrick I am not able to see Session Hos: Remote Desktop service in task manager, however the service is running fine, below are the screenshot for reference.
Just checking if there's any progress or updates?
--please don't forget to upvote and Accept response if the reply is helpful--
Ok, you're missing the point. Lookup the PID found here
then look for that PID in netstat output
Dave Patrick Hi, The RDS port number 3389, but when I look for in netstat connection, but there is no connection.
Check the port number of the RDS process and look for it in netstat output.
- RDS port number 3389 but I am not able to find it in netstat output.
Also, i am checking, telnet localhost 3389, it says connection time out. Check the port number of the RDS process and look for it in netstat output.
