This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(70.4, 0%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGS%3C/text%3E%3C/svg%3E)
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.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(252.8, 30%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EEY%3C/text%3E%3C/svg%3E)
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
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.
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
Shadowed a session from another session host server to the problematic server.......Same error
Here is the screen-shot you requested.
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.
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
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.
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,
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.
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
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.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(217.60000000000002, 28.999999999999996%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EIE%3C/text%3E%3C/svg%3E)
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
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?