RDS 2019 - Just....quits

usmguy04 1 Reputation point
2020-08-17T17:40:08.747+00:00

Hi everyone,

Running into a bit of an issue I can't seem to find an answer to. We have one single RDS server (running 2019) setup to allow users to access virtual desktops. A couple of times now, the RDS server just stops receiving RDP requests. I wasn't even able to login to the RDS server via RDP. I could console in - and a reboot got things going again - but after a few days - it happened again. The only error\warning in the event logs I could find that indicates an issue - is when the user attempts to login - and it fails - the event ID 20498 " Remote Desktop Services has taken too long to complete the client connection" shows up. Otherwise - I can't seem to find any clues as to why it would suddenly do that. Any help is greatly appreciated!

Remote Desktop
Remote Desktop
A Microsoft app that connects remotely to computers and to virtual apps and desktops.
4,598 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Falcon IT Services 226 Reputation points
    2020-08-17T20:38:02.603+00:00

    Hello usmguy,

    Please check the security logs for excessive failed login attempts, it could be a brute force attack affecting performance if the RDP is exposed to the Internet.

    Also, update the NIC drivers on the hardware kit and if possible run SFC and DISM image restore to make sure the OS files are intact.

    Lastly, check perflogs CPU utilization, disk and NIC utilization and backlog.

    Regards,

    Miguel Fra
    www.falconitservices.com


  2. Jenny Yan-MSFT 9,336 Reputation points
    2020-08-18T02:29:53.41+00:00

    Hi,

    1. Please check if the server 2019 has been patched to the latest.
    2. When Server stopped receiving remote connections, kindly check the status of RDS service and test if workaround of restarting the service would help instead of rebooting the server. (You could restart the service by below commands)
      $ServicePID = (get-wmiobject win32_service | where { $_.name -eq 'TermService'}).processID
      Stop-Process $ServicePID -Force
      Start-Service TermService
      

    -----Please "Accept as answer" if the reply is helpful----- Best regards, Jenny


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.