RD Gateway certificate woes

[Tinribs]

Hi

Our RDS server has died. We have problems getting agreement numbers for licenses as the relevant staff are unavailable. As a workaround I have installed RDG on one of our other servers. It all works fine internally but could not connect externally. Turns out to be a firewall issue. I had to point the clients at the external IP address for that server. Before I did that the connection would fail with resource unavailable errors.

Once I change the IP the connection is now failing because the certificate isn't trusted. I think this is because the initial cert was created when the RDG was using the FQDN of the server name. When I try to connect using the external IP this obviously doesn't match the name on the cert and it gets angry.

I tried recreating the cert on the RDG using the IP address without the FQDN and also with the FQDN. None of the them work.

Wondering how I get this sorted? I am assuming that as I am seeing this error rather than the first error that I am actually connecting to the server now, and if I get this sorted we'll have a working backup method of connecting, at least for the short term, until the missing info is retrievable.

TIA

MArk P.

[slugshead]

Grab a wildcart cert from godaddy or something, add that in to the deployment under certificates for each of the roles and you should be good to go.

 

Not totally the right way, but when you use a bunch of subdomains it works out the cheaper option