Since roughly the beginning of this month I am seeing issues with some of my users not being able to remote to their workstations. It does not matter if they users are coming through the VPN or if they are local. They cannot establish an RDP session with the computer. Their workstation is pingable and also manageable via remote management tools (Computer Management, PowerShell)
When attempting to remote over using the mstsc client the connection hangs at “initiating”.
I can log on locally to the machine with no issues.
The below command shows no results meaning that nothing is listening on port 3389:
Netstat -ano | find “3389”
The Remote Desktop Service is running however when I attempt to restart the service it hangs at stopping. I end up having to kill the TermServ process by stopping the Process ID. The service then auto restart and all is good until a couple of days later.
Here is what I have checked:
RDP is enabled in group policy
Windows firewall is set appropriately for our environment
What I mean is that computers that are having this issue have the same firewall settings that other working computers do.
I have verified the RDP protocol is enabled in group policy
I have verified that RDP is enabled via the registry
It seems that the Remote Desktop Service is crashing.
I am reviewing my event logs but nothing is standing out.
Anybody else seeing this?
Joshua
NOTICE: All e-mail sent to or from this address will be received or otherwise recorded by the Badgley Phelps corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to someone other than the recipient.


Sorry, I should have mentioned that this is not related to an RDS installation. This is standard Remote Desktop (mstsc).
Killing the “remote Desktop service” service on the host workstation and letting the service restart on its own fixes this issue.
I am looking for root cause of this.
From: James Iversen <JIve...@nycm.com>
Sent: Friday, August 19, 2022 7:14 AM
To: ntsys...@googlegroups.com
Subject: Re: [ntsysadmin] Remote Desktop Service crashing - Not listening
|
Caution: External sender |
|
To view this discussion on the web visit https://groups.google.com/d/msgid/ntsysadmin/OFAAF942A9.95E03ABF-ON852588A3.004DA291-852588A3.004E3A0C%40nycm.com.
Are you using the windows firewall or a third party firewall?
This sounds very much like the port is being “stepped on”.
Thanks.
Regards,
Michael B. Smith
Managing Consultant
Smith Consulting, LLC
To view this discussion on the web visit https://groups.google.com/d/msgid/ntsysadmin/MW2PR0102MB34517A8FDC37CA678F161C61BB6C9%40MW2PR0102MB3451.prod.exchangelabs.com.
Windows firewall . .but its configured exactly the same as other computers in the office who are not having this problem.
It is strange that the ‘Remote Desktop Service’ service still shows running even though it is no longer listening on port 3389. And why when I restart that service is hangs.
From: Michael B. Smith <mic...@smithcons.com>
Sent: Friday, August 19, 2022 7:20 AM
To: ntsys...@googlegroups.com
Subject: RE: [ntsysadmin] Remote Desktop Service crashing - Not listening
|
Caution: External sender |
|
To view this discussion on the web visit https://groups.google.com/d/msgid/ntsysadmin/0a9c0ba53ae74255bae02cbf78a962c7%40smithcons.com.