![]() The end user experience is, from the rdweb webpage user clicks on "remote desktop" downloads the RDP file and launches, then instead of connecting to the desired Session host, the user is presented with a login prompt on the connection broker and is then connected to the desktop of the connection broker. I have searched for where to find the logs that will show what parameters are being rejected, and have had no luck. Target FQDN = redacted FQDN of Connection Broker ![]() Target Netbios = redacted netbios name of session host Target Name = redacted hostname of session host "RD Connection Broker successfully processed the connection request for user domain redacted*user redacted*. This event comes after a different event that shows the user has successfully logged in, and even knows where to send the session to. "Remote Desktop Connection Broker Client failed to redirect the user domain redacted*user redacted*. Issue, the Connection Broker fails to redirect the user, event log shows even 1306 that says the following. ![]() RD-SessionHost on 2 servers, 1 for remote desktop and one for remote apps RD-License and RD-Broker on 1 Server on dedicated subnet for servers Brand new RDS Farm, standard deployment, Server 2019 build 1809, current on updates. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |