Forum Discussion
Solved
Windows Virtual Desktop - Your computer can't connect to Remote Desktop Gateway server
I have successfully deployed WVD to my MSDN tenant following the steps 1 and 2 in https://docs.microsoft.com/en-gb/azure/virtual-desktop/tenant-setup-azure-active-directory and https://docs.microsoft...
I think I may have worked out my problem, I have been testing with a user account I setup in Azure AD. I have only just setup the tenant and AD domain to test WVD. I have just tested with an account I had created on the AD Server (Still in Azure but with AD Connect installed to sync to AAD) and this has worked fine. I have also created another AAD account and tried to connect to the desktop but this failed with the same error.
Interestingly I am getting prompted to enter my credentials again upon connection, not sure if I have missed something with the SSO settings?
GuyPaddock Did you get anywhere with this? I have setup a host pool and when i try to connect to the remote desktop i see "opening remote port" then "We couldn't connect to the gateway because of an error. If this keeps happening, ask your admin or tech support for help."
I see the same error as you did
ActivityId : 893b0a57-6f19-4e15-90b4-1950fabb0000
ActivityType : Connection
StartTime : 08/08/2019 14:31:50
EndTime : 08/08/2019 14:31:54
RoleInstances : rdwebclient;mrs-eus2r1c002-rdgateway-prod-staging::RD0003FF459018;mrs-eus2r1c002-rdbroker-prod-staging::RD0003FF45E902;≤dtwvd-0.DTWVD.local≥
Outcome : Failure
Status : Completed
Details : {[ClientOS, Win32 Chrome 75.0.3770.142], [ClientVersion, 1.0.18.5], [ClientType, HTML], [PredecessorConnectionId, ]...}
LastHeartbeatTime : 08/08/2019 14:31:55
Checkpoints : {LoadBalancedNewConnection, TransportConnecting, TransportConnected}
Errors : {Microsoft.RDInfra.Diagnostics.Common.DiagnosticsErrorInfo}
Yes; apologies for not updating with a follow-up. It turned out that we had a role that only users in our "employees" group sync with AADDS. The test account wasn't in that group so they couldn't authenticate with the machine even though I had granted the account access to Azure VDI. I added the user to the employees group, changed the account password, waited about 5 mins to ensure the account synced, and got in.
I got everything working for us a few weeks back I setup as much as I could in advance in Powershell and made sure AZ domain services was running well and everything now works as intended. GuyPaddock
Okay, we don't have AZ Domain Services configured. I noticed that the last 4 VMs I created don't show up in Azure AD under devices. I was talking to my lead Sys Admin about setting up AZ Domain Services and he said it's not needed because we have that role enabled on the DCs that are hosted in Azure. I think we do need to have that configured.
What are your thoughts?
Here's a curious thing about that.
I'm a Global Admin and Owner of the subscription. I was able to access the first VM via the web and new RDP client subscription. The subsequent 4 VMs cannot be accessed by me and the last 2 do not show up when I run the Get-RDSSessionHost command.
If I use the old traditional RDP client I can access the VMs.
- Thanks for getting back so quick, ill take a look into this
