Good morning all,
I have a 2012 R2 RDS setup that includes a server with the gateway/web access roles installed, and 2 connections brokers in HA with a 2012 SQL back end. I also have a virtualization host running 2012 R2. I do not have any session hosts as all I am using the system for is providing both personal and pooled desktops.
I am having an intermittent issue where a client cannot connect to either a pooled desktop or personal desktop. I say intermittent because if the client keeps clicking connect after a failure eventually it will work. The issue doesn't seem to be any different if the client uses the webpage, android application, or windows application to connect. I have gone through the logs and it looks like I get the same entries every time a client cannot connect. I have added the log files here:
| Server Role | Date | EventID | Event Type | LogName | Message |
| Gateway | 10/18/2016 19:13 | 302 | Information | Microsoft-Windows-TerminalServices-Gateway/Operational | The user "Domain\Username", on client computer "External IP", connected to resource "Connection Broker Farm Name". Connection protocol used: "HTTP". |
| Gateway | 10/18/2016 19:13 | 300 | Information | Microsoft-Windows-TerminalServices-Gateway/Operational | The user "Domain\Username", on client computer "External IP", met resource authorization policy requirements and was therefore authorized to connect to resource "Connection Broker Farm Name". |
| Gateway | 10/18/2016 19:13 | 200 | Information | Microsoft-Windows-TerminalServices-Gateway/Operational | The user "Domain\Username", on client computer "External IP", met connection authorization policy requirements and was therefore authorized to access the RD Gateway server. The authentication method used was: "NTLM" and connection protocol used: "HTTP". |
| Gateway | 10/18/2016 19:13 | 313 | Information | Microsoft-Windows-TerminalServices-Gateway/Operational | The user "Username@Domain", on client computer "External IP:59040", has initiated an inbound connection. This connection may not be authenticated yet. |
| Gateway | 10/18/2016 19:13 | 313 | Information | Microsoft-Windows-TerminalServices-Gateway/Operational | The user "Username@Domain", on client computer "External IP:59040", has initiated an inbound connection. This connection may not be authenticated yet. |
| Gateway | 10/18/2016 19:13 | 312 | Information | Microsoft-Windows-TerminalServices-Gateway/Operational | The user "Username@Domain", on client computer "External IP:59037", has initiated an outbound connection. This connection may not be authenticated yet. |
| Gateway | 10/18/2016 19:13 | 205 | Information | Microsoft-Windows-TerminalServices-Gateway/Operational | The user "Domain\Username", on client computer "External IP", successfully connected to the remote server "Connection Broker Farm Name" using UDP proxy. The authentication method used was: "Cookie". |
| Gateway | 10/18/2016 19:13 | 302 | Information | Microsoft-Windows-TerminalServices-Gateway/Operational | The user "Domain\Username", on client computer "External IP", connected to resource "Connection Broker Farm Name". Connection protocol used: "UDP". |
| Gateway | 10/18/2016 19:13 | 205 | Information | Microsoft-Windows-TerminalServices-Gateway/Operational | The user "Domain\Username", on client computer "External IP", successfully connected to the remote server "Connection Broker Farm Name" using UDP proxy. The authentication method used was: "Cookie". |
| Gateway | 10/18/2016 19:13 | 302 | Information | Microsoft-Windows-TerminalServices-Gateway/Operational | The user "Domain\Username", on client computer "External IP", connected to resource "Connection Broker Farm Name". Connection protocol used: "UDP". |
| Gateway | 10/18/2016 19:14 | 303 | Information | Microsoft-Windows-TerminalServices-Gateway/Operational | The user "Domain\Username", on client computer "External IP", disconnected from the following network resource: "Connection Broker Farm Name". Before the user disconnected, the client transferred 1960 bytes and received 6717 bytes. The client session duration was 60 seconds. Connection protocol used: "UDP". |
| Gateway | 10/18/2016 19:14 | 303 | Information | Microsoft-Windows-TerminalServices-Gateway/Operational | The user "Domain\Username", on client computer "External IP", disconnected from the following network resource: "Connection Broker Farm Name". Before the user disconnected, the client transferred 1054 bytes and received 4082 bytes. The client session duration was 60 seconds. Connection protocol used: "UDP". |
| Gateway | 10/18/2016 19:14 | 303 | Information | Microsoft-Windows-TerminalServices-Gateway/Operational | The user "Domain\Username", on client computer "External IP", disconnected from the following network resource: "Connection Broker Farm Name". Before the user disconnected, the client transferred 7018 bytes and received 10280 bytes. The client session duration was 60 seconds. Connection protocol used: "HTTP". |
| Connection Broker | 10/18/2016 19:13 | 1301 | Verbose | Microsoft-Windows-TerminalServices-SessionBroker-Client/Operational | Remote Desktop Connection Broker Client received request for redirection. User : Domain\Username RDP Client Version : 5 |
| Connection Broker | 10/18/2016 19:14 | 1306 | Error | Microsoft-Windows-TerminalServices-SessionBroker-Client/Operational | Remote Desktop Connection Broker Client failed to redirect the user Domain\Username. Error: NULL |
| Connection Broker | 10/18/2016 19:14 | 1296 | Error | Microsoft-Windows-TerminalServices-SessionBroker-Client/Operational | Remote Desktop Connection Broker Client failed while getting redirection packet from Connection Broker. User : Domain\Username Error: Element not found. |
| Virtualization Host | 10/18/2016 19:14 | 8480 | Information | Microsoft-Windows-TerminalServices-TSV-VmHostAgent/Operational | Remote Desktop Virtualization Host did not start system boot monitoring for the virtual machine named Personal VM Name . Virtual machine name: Personal VM Name Hresult: 0x8000FFFF |
| Virtualization Host | 10/18/2016 19:14 | 8457 | Information | Microsoft-Windows-TerminalServices-TSV-VmHostAgent/Operational | Remote Desktop Virtualization Host successfully orchestrated the virtual machine named Personal VM Name . Virtual machine name: Personal VM Name Fully qualified domain name=Personal VM Name IP address=Internal IP |
It looks to me that the issue is with the connection broker. I say that because when we have a client that gets an error we get in the gateway log the successful connection is only to the broker farm name and never the end point desktop. If a client is successful we will get a log entry stating the internal IP of the desktop the client connected to. On the connection broker the events state that the connection broker is waiting for a packet from the connection broker, that seem weird. I don’t believe it is a connection to the database as I said it is an intermittent problem. If it is an issue with the connection broker I don't know what it is so, if anyone has any insight it would be greatly appreciated.
Thanks,
Scott