
The firewall port 3389 needs to be opened between the RDweb and the RD Connection broker. It turns out that the problem was the connection between the RDWeb and the RD Connection Broker.

In our case, the remote desktop settings was enabled on the server. The proposed resolution was to enable the remote desktop settings on the target servers. The following error occurred: “23005”.Ī lot of people on internet were pointing to the following link ( (v=ws.10).aspx). The user “XXXXXX”, on client computer “”, met connection authorization policy and resource authorization policy requirements, but could not connect to resource “ZZZZZZZZZZ”. Source: Microsoft-Windows-TerminalServices-Gateway Log Name: Microsoft-Windows-TerminalServices-Gateway/Operational Everything was fine till the warning message was thrown by the connection process.
#Windows 2012 r2 remote desktop services failes windows
Looking into the event viewer, at the Applications and Services Logs > Microsoft > Windows >TerminalServices-Gateway node, we were able to retrieve the connections steps we were performing. So the next logical step was to look into the RD Gateway and see if something was blocking the access to the RD Session Hosts. So, we were sure that the firewall was allowing traffic from the client to the RD Gateway. Using appropriate tools, we were able to assess that an access the RD Gateway servers. While trying to access to the applications on the rd session hosts, an error was thrown or we never were able to perform the connection. At this stage, we encountered a small issue.

Testing the Setup and the Failed connectionsĪfter having implemented all the rds infrastructure, it’s was time to perform some initial tests (load balancing, redundancy, access,…). So, no problem we start performing the installation and working together with the Firewall team, we have opened the necessary ports needed to have such setup working. You can see a high level view of the setup in the following drawing.

However, the RD Connection brokers and RD Session host servers were located on the internal network. These servers were accessible from the outside world. We will explain a small issue we had while the RDS infrastructure was using a DMZ zone…īased on the customer request, we have been asked to place the RD Gateway and the RD Web Access servers on a DMZ zone. With all the info, I’m publishing lately about this topic you should be fed up or you should be really happy to have us sharing all the small hick up we have encountered during our different projects.
