remoteapp the remote computer could not be found

The next port of call was to check RD gateway and we found that the second gateway was still part of the RD gateway farm. Make sure the remote computer is turned on and connected to the network, and that remote access is enabled. Remote Desktop can’t connect to the remote computer for one of these reasons:ġ) Remote access to the server is not enabledģ) The remote computer is not available on the network However we received a different error when connecting from external network – but this time the end user’s error was different:

Removed the RD Web Access of the second nodeĬonnecting to the remote desktop farm from internal network worked fine after we have made this change – tested this multiple times and from different machines to confirm that it’s stable.

Removed DNS RR record of the second broker node.

In the server manager console, the following tasks were done: To isolate the issue, we had decided to operate the RDS on a one node configuration to confirm suspicion that whenever a user gets redirected to the broker that’s not configured it would cause a redirection failure (RDCB uses Round Robin DNS for HA). This led me to investigate the RDS configuration: the RDCB was setup in HA mode with a SQL backend however it only has one node configured.

One aspect I discovered was that the same error didn’t occur on the other broker server. Remote Desktop Connection Broker Client failed to redirect the user Remote Desktop Connection Broker Client failed while getting redirection packet from Connection Broker. įarm name specified in user’s RDP file (hints) could not be found.Įrror: The farm specified for the connection is not present. RD Connection Broker failed to process the connection request for user. Contact your network administrator for assistance.Īfter further digging, I found the error below (Event ID 802) on the second broker node: Your computer can’t connect to the remote computer because the Connection Broker couldn’t validate the settings specified in your RDP file. The end user encountered the following error when trying to connect: The broker nodes also host the RD Web Access and RD gateway with one of the nodes assuming the RD Licensing role. The session hosts are 2012 R2 based machines. The Remote Desktop Connection Broker is configured in HA mode using two DNS records pointing to two broker nodes for round robin. The RDS farm consisted of two connection broker servers and two session hosts. This blog summarises the process of identifying the symptoms, possible causes, and the resolution steps. The error occurred intermittently and after a number of retries, client could establish connection normally making the issue not always reproducible. Recently I ran into a problem with an existing Remote Desktop Services 2012 R2 at a client site.

Remoteapp the remote computer could not be found