RDS Farm Error 1722 When Shadowing Session

Greg Stubits 1

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.

Eleven Yu (Shanghai Wicresoft Co,.Ltd.) 10,766 Reputation points Microsoft Vendor

2020-10-08T06:14:16.457+00:00

Hi,

May I know if the user account used to shadow is in the local admin group of the problematic server?

If we totally turn off the firewall on both client and the problematic server, will the error persist?

Thanks,
Eleven
Greg Stubits 1 Reputation point

2020-10-08T19:27:27.033+00:00

The user account IS a member of the local Admin group.

Also, firewalls are off on both the server and workstation. The error still persists.
Eleven Yu (Shanghai Wicresoft Co,.Ltd.) 10,766 Reputation points Microsoft Vendor

2020-10-09T08:04:54.593+00:00

Hi,

If we shadow from one working session host server or the DC to the problematic, will the problem persist?

And could you please share the screenshot of the error message you encountered on the win 10 clients?

Thanks,
Eleven
Greg Stubits 1 Reputation point

2020-10-09T15:31:55.367+00:00

Shadowed a session from another session host server to the problematic server.......Same error

Here is the screen-shot you requested.
Greg Stubits 1 Reputation point

2020-10-09T15:37:45.697+00:00

Also, If I run query user on the problematic server, here is what I get,

PS C:\windows\system32> query user /SERVER:XXXXXXX <-----Fake Name
Error 0x000006BA enumerating sessionnames
Error [1722]:The RPC server is unavailable.
Eleven Yu (Shanghai Wicresoft Co,.Ltd.) 10,766 Reputation points Microsoft Vendor

2020-10-12T06:49:10.2+00:00

Hi,

Please run powershell command "qwinsta /server: xxx" to see if it could display the list of sessions on the problematic server.

If no, please use domain admin account to shadow to see if the issue persists.

Thanks,
Eleven
Greg Stubits 1 Reputation point

2020-10-12T14:25:13.89+00:00

Here is the output of the powershell command.........

PS C:\windows\system32> qwinsta /server: XXXXXX
No session exists for XXXXXX

Logged into my PC with the domain admin account, same message in powershell....No Session exists.
Eleven Yu (Shanghai Wicresoft Co,.Ltd.) 10,766 Reputation points Microsoft Vendor

2020-10-13T01:30:45.11+00:00

Hi,

Can you confirm there is really RDP session on the problematic server?

Or you can let one user to create a new RDP session to the problematic server to ensure there is session. Then run the powershell command to see the result and try shadowing.

Thanks,
Greg Stubits 1 Reputation point

2020-10-13T13:39:09.343+00:00

As I am typing this reply, there are currently 20 remote sessions on that server. If I remotely connect to the problematic server and run server manager, I can shadow sessions. If I run server manager from any other computer or server, I cannot shadow a session on that server.
Eleven Yu (Shanghai Wicresoft Co,.Ltd.) 10,766 Reputation points Microsoft Vendor

2020-10-14T05:59:09.353+00:00

In this case, you might need to capture some dumps or traces to further investigate the issue, which I suggest to contact Microsoft Customer Support and Services where more in-depth investigation can be done so that you would get a more satisfying explanation and solution to this issue.

You may find phone number for your region accordingly from the link below:
Global Customer Service phone numbers
https://support.microsoft.com/en-us/help/4051701/global-customer-service-phone-numbers
Greg Stubits 1 Reputation point

2020-10-15T17:43:19.063+00:00

Problem has been solved. SMB 2 and 3 had to be enabled on that server. For some reason they were disabled. Thank you for your time and effort.

2 answers

Ilia Ershov 131 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
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
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?
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

RDS Farm Error 1722 When Shadowing Session

2 answers

Your answer