RDP not working Windows Server 2019 Standard

jgomila 1 Reputation point
2021-02-06T17:17:58.167+00:00

Windows Server 2019 Standard. Remote Desktop Service is running but port 3389 not listening. Same issue in all Windows Server 2019 Standar instances the we have running.

Found system event related:

Remote Desktop Services is not accepting logons because setup is running.
Log Name: Microsoft-Windows-TerminalServices-LocalSessionManager/Operational
Source: TerminalServices-LocalSessionManager
Event ID: 34

I tried to change RDP port, checked firewall settings, ensure service is running, compared with other servers that are working, read many posts and questions and tried many things without success.

Please, any idea to solve the problem?

Best regards,

Windows for business | Windows Client for IT Pros | User experience | Remote desktop services and terminal services
Windows for business | Windows Server | User experience | Other
{count} votes

8 answers

Sort by: Most helpful
  1. jgomila 1 Reputation point
    2021-02-08T09:45:26.1+00:00

    Hello,

    Thanks for your help.

    I tried to find "Remote Desktop Services Security Filter Driver" but it is missing.

    I googled for that driver and people says it must be in "Device Manager - Hidden Devices - Non Plug and Play" but no "Non Plug and Play" section found, and I full check all device nodes without success.

    Have you other idea?

    Thank you,
    Pepe

    0 comments No comments

  2. jgomila 1 Reputation point
    2021-02-12T08:49:18.457+00:00

    Hi ElevenYu,

    The "UMBus Root Bus Enumerator" system device is there. I also tried to remove and reinstall following your instructions without success. It continues not listening on port 3389 but Remove Desktop Service is running. And also have same system event "Remote Desktop Services is not accepting logons because setup is running.".
    Any case thank you for the help.

    Best regards,

    José


  3. Jon Hatfield 46 Reputation points
    2021-11-17T01:24:25.743+00:00

    I had this same issue on a brand new installation. It turns out that there were a few of the Remote Desktop firewall rules that didn't get enabled properly when the service was turned on.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.