Hi I don't know if this is the right forum to ask this but I have an issue with TS web apps which I can't find a solution:

I use TS web apps which is registered as : ts.mydomain.com

I have a registered a godaddy certificate with the SAN ts.mydomain.com

The certificate appears to be fine on Vista / 2008 clients and web apps works a charm.

but on the XP clients when the user connects to an application they get a message that says i have the wrong certificate and it seems to think that the certificate should be for the server and not ts.mydomain.com ??? :

if they click proceed it works fine but I just was wondering if there is a solution to this?

the certificate error says that is for the server fqdn myserver

I think its some kind of authentication problem but I don't know what to do next? Do I have to register the server name as well in my certificate and then reinstall the certificate?

Edited July 3, 201016 yr by dubsdj

Have you tried installing windows server 2003 in your servers. Since your XP clients are the ones having problems, maybe using a XP based OS for your server will rule out incompatibilities coming from mixing diferent windows versions.

Which version of the RDC client are you using? The old RDC5.x client that shipped with XP/2003 would have issues with certificates if the cert name didn't match, whereas Vista ships with RDC 6.x (and Win7 RDC 7.x). Also, XP and Vista/Win7 have different certificate underpinnings, so upgrading the RDC client on your XP machines to 7.x might not help, but it's worth a shot.

Which version of the RDC client are you using? The old RDC5.x client that shipped with XP/2003 would have issues with certificates if the cert name didn't match, whereas Vista ships with RDC 6.x (and Win7 RDC 7.x). Also, XP and Vista/Win7 have different certificate underpinnings, so upgrading the RDC client on your XP machines to 7.x might not help, but it's worth a shot.

Well I have just noticed that the issue occurs on windows 7... strange vista and 2008 don't seem to have the problem.

The problem at that point is perhaps the certificate, or more likely, perhaps the chain of trust to the trusted root that spawned that certificate you're using. Using alternate names for the server (and the name you're using to initially connect, and if you're using TS Gateway or not) can all play into this.