Ressourcen für IT-Professionals >
Forenhomepage
>
Terminal Services
>
Gatewayed terminalserver is signed with the wrong certificate
Gatewayed terminalserver is signed with the wrong certificate
- Hi everybody,
I'm using a 2008 server and behind is a 2008 terminalserver. The problem I'm experiencing applies to both full-desktop connections as well as remote apps.
All certs I'm using have been signed by my own CA (let's call it "localdomainname"). Its root cert is trusted by ALL computers involved. In the remote app manager I chose the computer cert with "terminalserver.localdomainname", signed by "localdomainname".
But when I connect I get an error message that's complaining about a cert signed by a non-trusted CA. And that's true because the cert says:
hostname: "terminalserver.localdomainname"
signer: "terminalserver.localdomainname"
What's that supposed to mean? It's definitely not the cert I chose, the validity dates also differ. I have no idea where that cert came from.
I'm already created a new cert for the TS and had that signed by the CA and chose it. But nothing changed.
Anybody got an idea on that? And yes, I'm pretty sure there's no man in the middle ;-)
Best regards,
Jens
Alle Antworten
- Hi Jens,
What is the exact error message you get?
Also, what is the certificate you have installed on the gateway server?
By any chance , is this the gateway server certificate?
Thanks,
Kaustubh - Hi Kaustubh,
the RDP client is complaining that the CA which signed the cert isn't being trusted.
The cert on the gateway server has two hostnames (because the server is accessed from the inside with its local hostname as well as from outside via the external hostname).
It's not the gateway's cert. It's got another hostname (the one of the terminal server) and is supposed to be signed by the terminalserver, not my CA.
Best regards,
Jens
