Terminal Server 2008 WildCard Certificate Error

I have a basic Windows 2008 terminal server that I have installed my wildcard Comodo certificate on to try to rid my users of the annoying certificate error when they connect via the RDP client.  Unfortunately, it is not working.  The certificate in the error message has definitely changed from the self-generated one to the *.domain.com cert that I installed, but Windows is still throwing a fit because it does not match the hostname that the users must enter to access the host.  Do wildcards work in TS 2008?  I don't have TS Gateway or Web App set up, just a plain jane 2008 Terminal Server.
LVL 1
marrjAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
CoralonConnect With a Mentor Commented:
Are they entering the full name as they go to access it?  Even if you have a wildcard cert, if you don't use a truly matching name, it will throw an error.

i.e. - if use the shortname of server1 to RDP in, it will throw an error.  But, with the wildcard cert, I should be able to server1.domain.com and it should not throw the error.

Coralon
0
 
btanExec ConsultantCommented:
Understand that Windows Server 2003 Terminal Services implementations don't support wildcard certificates in any of its features. You have to buy named SSL certificates. Server 2008 supports wildcard certificates for all features, such as TS Gateway and TS Web Access

Needed also RDC 6.1 and above on the client.
And For a certificate to be used for RDP it must have Server Authentication ( 1.3.6.1.5.5.7.3.1 )

http://serverfault.com/questions/201451/install-certificate-in-rdp-tcp-properties

Event ID 1054 — Terminal Services Authentication and Encryption
http://technet.microsoft.com/en-us/library/cc775272%28WS.10%29.aspx
0
 
marrjAuthor Commented:
The users are entering an alias of the server name created by an alias in DNS so that they don't have to remember the hostname.
0
 
CoralonCommented:
That won't work.. If you don't want to throw any kind of SSL error, they have to use the full URL.  

Coralon
0
 
btanExec ConsultantCommented:
I am thinking of two possibilities:

a) think it may be more of a need for Subject Alternative Name (SAN) in the certificate.

E.g. SAN attributes take the following form: san:dns=dns.name[&dns=dns.name]

Multiple DNS names are separated by an ampersand (&). For example, if the name of the domain controller is corpdc1.fabrikam.com and the alias is ldap.fabrikam.com, both of these names must be included in the SAN attributes. The resulting attribute string appears as follows: san:dns=corpdc1.fabrikam.com&dns=ldap.fabrikam.com

@ http://support.microsoft.com/kb/931351
@ http://www.bunkerhollow.com/blogs/matt/archive/2009/01/28/install-amp-configure-ts-web-access-for-external-use.aspx


b) I also saw another forum that may have related issue DNS alias issue
http://social.technet.microsoft.com/Forums/en-US/winserverTS/thread/001981f5-62a5-4234-9a09-2b442e7bbccf
0
All Courses

From novice to tech pro — start learning today.