RDS19 Issues

[cw222]

Hi All,

 

I'm sure i'm missing something super simple - but any help would be highly appreciated. We are bumping up 2012 RDS to 2019.

 

I have 4 RDS Servers Created:

1 Broker/Licensing

1 Web Access and Gateway

1 Application Host

1 Desktop Host

 

2 Collections:

1 Desktop

1 Standalone Apps

 

When Connecting in via mstsc.exe all works fine and I get my remote desktop and apps. I can see that I have connections to the desktop host from within the broker. But we don't want to have to push staff to use this.

 

When connecting in via Servername//RDWeb/WebClient/Index.html I get a correct validation request, I can see the collections and click on the Apps / Desktop.

 

However, when I connect either to the desktop or the apps, I get the error :

 

Servers are connected to the right DCs - and running NSlookup from client the IPs correspond with the servers.

 

Any pointers or areas to look? I've looked via Google and can't find anything really very useful.

 

Kind Regards,

Cw222

[Chaniel]

Are the certificates all correct and DNS all good? e.g. Certificate is for rdsgw.school.org and you're connecting via https://rdsgw.school.org/rdweb/webclient/index.html

 

Pretty sure I ran into that issue and it was because local DNS is school.local, not school.org but I was using a wildcard *.school.org certificate. I added a CNAME for rdsgw.school.org to rdsgw.school.local and this fixed things for me.

[free780]

Do you have NPS security limiting RDS logons to domain joined devices? That can prevent the webclient from working?

[cw222]

Are the certificates all correct and DNS all good? e.g. Certificate is for rdsgw.school.org and you're connecting via https://rdsgw.school.org/rdweb/webclient/index.html

 

Pretty sure I ran into that issue and it was because local DNS is school.local, not school.org but I was using a wildcard *.school.org certificate. I added a CNAME for rdsgw.school.org to rdsgw.school.local and this fixed things for me.

 

Thanks both - this was the exact issue! I will make sure to do this via the gui next time rather than powershell as it was a lot more apparent through the gui!

[MrBrow]

In case anyone else finds this post...

 

I had the exact same error so went playing with DNS with no luck. Instead, I found that a cert for the gateway (easily accessed via Remote Desktop Manager) had expired and a renew of that fixed the Web Client issue. Legacy methods did still work though with the broken cert so was a bit surprised to see this was the error - just Web Client was broken.