Forum Discussion
Cannot connect from RD Client app but can through web client
Up until today, 10-17-2022 we have had no issues connecting to our AVD host pools through the Remote Desktop app. I have a couple pooled host pools with a handful of hosts configured to use FSLogix ...
We are also facing the same issue in our environment, we are using the Remote Desktop client from the Microsoft store as a workaround.
If you find any solution, please let me know.
- AAD joined VMs or Classic/hybrid joined?
- My environment is all hybrid Azure AD joined in the new Azure environment. I recently moved them from classic to the new environment.
janakiram7 that is wild you could access through the Microsoft Store version....it crossed my mind to test that; however, there is no way I could have gotten that installed on all of our endpoints quickly. Fortunately, yesterday 10/17 after wasting nearly an entire day on this issue, it started to work around 3PM Central Time.... is it working for you today?
ITSensei It's still not working for us, it seems to be some issue in the domain controller. Did you make any changes to resolve it?
- We have 4 domain controllers....1 physical on prem, 2 virtual on prem and 1 virtual in Azure. All of our cloud compute resources have the Azure DC machine as the primary. That domain controller had several pending updates that needed installed. I installed all the updates, which required a couple reboots. I didn't think that is what fixed our issue, but now you mentioned it, it most likely could have.
I ran the "Required URL Check tool" on a couple different hosts and they all came back with positive results. I hadn't done that while we were experiencing issues though. That resource can be found here: https://learn.microsoft.com/en-us/azure/virtual-desktop/required-url-check-tool
I am still convinced we have 'something weird' going on in our DNS/DC because while on my AVD resource, or even my Azure VM that is on the same VNet, I cannot get to URL's like the one I just provided above...it errors out.
I'm going to try and manually set the preferred DNS server on my test machine to the on prem DC to see if that fixes any issues.
