RDS Farm Error 1722 When Shadowing Session

Greg Stubits 1 Reputation point
2020-10-06T19:46:01.67+00:00

We currently have a 4 server Windows 2016 remote desktop farm. Everything is good except for one issue. When trying to shadow a session from Windows 10 PCs on 1 of the servers, we get the dreaded 1722 error, On the other three servers, we are able to shadow sessions from Windows 10 computers. The server with the problem has the Connection Broker, Gateway, Licensing, Web Access, and Session Host roles installed. The other 3 only have the Session Host installed. The server is a VMWare virtual server and it was not cloned. I am able to ping the server name and it does resolve to an IP address. I checked the RPC startup values in the registry and they are all at number 2, which from what I have read, is what they are supposed to be. All services relating to RPC are running and their startup value is "automatic". As a test, I am allowing all inbound connections through the Windows Advanced Firewall. I made sure file and print sharing was enabled. And as a just in case, I did an ipconfig /flushdns.

I am now at a loss on where to go from here. Any help will be greatly appreciated.

Greg S.

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

2 answers

Sort by: Most helpful
  1. Ilia Ershov 126 Reputation points
    2020-10-07T08:22:05.05+00:00

    I believe the issue is related to poor design but check the following key on problem server
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\AllowRemoteRPC
    1 - allowed
    0 - denied

    0 comments No comments

  2. Greg Stubits 1 Reputation point
    2020-10-07T17:06:11.317+00:00

    That registry key is set to number 1.

    What do you mean by "poor design"? How would poor design come into play with error 1722?

    0 comments No comments