asked on RDP server giving the local machine certificate and not the SSL certificate
Here is the setup
2008 terminal server
domain abc.com
SSL rdp.abc.com
machine internal name rdp.abc 192.168.1.10
External DNS rdp.abc.com 2.2.2.2
firewall routes ports to terminal server
I have imported the certificate into the terminal server in mmc ( add snap-in certificates, computer account). I go into certificates > Remote Desktop> certificates and see the certificate in there.
I go into RemoteApp Manager and look at Digital Signature Settings and see it is green check signing as : rdp.abc.com
When I go and try to connect from external It prompts me for user/password then gives me the error:
The identity of the remote computer cannot be verified. Do you want to connect anyway?
Certificate name
Name in the certificate from the remote computer:
rdp.abc
Certificate errors
The certificate is not from a trusted certifying authority
Why is it using the internal certificate and not the SSL certificate that is installed?
I have rebooted several times
Searches on Google are not giving any tips...
I have the option to connect despite these certificate errors, but I don't want to. I want it to give the correct SSL ( rdp.abc.com) for the session.
Knightdog
2008 terminal server
domain abc.com
SSL rdp.abc.com
machine internal name rdp.abc 192.168.1.10
External DNS rdp.abc.com 2.2.2.2
firewall routes ports to terminal server
I have imported the certificate into the terminal server in mmc ( add snap-in certificates, computer account). I go into certificates > Remote Desktop> certificates and see the certificate in there.
I go into RemoteApp Manager and look at Digital Signature Settings and see it is green check signing as : rdp.abc.com
When I go and try to connect from external It prompts me for user/password then gives me the error:
The identity of the remote computer cannot be verified. Do you want to connect anyway?
Certificate name
Name in the certificate from the remote computer:
rdp.abc
Certificate errors
The certificate is not from a trusted certifying authority
Why is it using the internal certificate and not the SSL certificate that is installed?
I have rebooted several times
Searches on Google are not giving any tips...
I have the option to connect despite these certificate errors, but I don't want to. I want it to give the correct SSL ( rdp.abc.com) for the session.
Knightdog
Windows Server 2008Microsoft 365 EnterpriseMicrosoft Legacy OS
Last Comment
knightdogs
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ram_kerala
- very well said. Most of my experience has been with Terminal Server on Server 2003 and not Server 2008 until recently. Now they call it RDS which makes it confusing.
- very well said. Most of my experience has been with Terminal Server on Server 2003 and not Server 2008 until recently. Now they call it RDS which makes it confusing.
ASKER
I will be working on this tomorrow.
Thanks for all the suggestions.
Thanks for all the suggestions.
Actually I just took over here. All i did was renew the expiring SSL certificate. Now I have to admit that I had not used the RDS server so I don't know if the error was there before I started or not.
DNS resolves correctly from external.