Forum Discussion

ian11230's avatar
ian11230
Copper Contributor
May 03, 2019

We couldn't connect to the gateway because of an error

My test account can see the VD in the web browser but I get this error every time I try to connect, it says "opening remote port" and fails. If I try to connect through the app I get told I do not ha...
  • Conrad Agramont's avatar
    Conrad Agramont
    May 13, 2019

    ian11230 If you're using Azure Active Directory Domain Services, you need to make sure the deployed servers are in the "AADDC Computers" OU and you log in using an admin account that is in the "AADDC Users" OU.  Make sure the admin user is a member of the "AAD DC Administrators" group in Azure Active Directory.

     

    When I did this, I was finally able to Remote Desktop directly into the deployed VM's in the hostgroup.

vstefanovic's avatar
vstefanovic
Copper Contributor
May 13, 2019

What about if we have on-premise AD with AD Connect instead Azure ADDS?
Also, one of DCs is in Azure as VM, and HostPool machines are joined to AD.

 

Regards,

CyclopsHelpdesk's avatar
CyclopsHelpdesk
Copper Contributor
Sep 24, 2019

vstefanovic Yes, we are in the same scenario. The error message we get when using the desktop client or the web link is:

"Oops, we couldn’t connect to “USSPA-RDSH”. We couldn’t connect to the gateway because of an error. If this keeps happening, ask your admin or tech support for help.”

 

Any ideas?

Resources