Re: SSL issue

On the client side there is a setting you can change to require cert validation. If you look under the advanced tab (in RDP 6.0, it might be different for 5.1 and 5.2), you can choose what level of authentication to require. One of the options is to require authentication, if that is set, it will pop an error if the authentication is not met.

--
Josh Rosenberg [MSFT]
SDE - Terminal Services


"Wayne" <wayne@xxxxxxxxxx> wrote in message news:puTSh.13996$JZ3.12273@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I have configured a Win2003 w/sp2 server to be a terminal server. I have configured TLS for the connection, and this works fine. I am using a certificate issued by an internal CA (i.e. did not purchase a cert from VeriSign or someone like it).

When I connect to this Terminal Server from a domain client, which has a certificate pushed to it via group policy, the connection works as advertised.

When connecting with a client that is not joined to the domain, and thus does not have our internal CA listed as a trusted source, I get an error message before I connect warning me that the certificate is not trusted. I click OK to continue and I am able to establish a session.

I don't want this. If there is a problem with a certificate I want the connection to drop, no session established.

I read an article on the MS website, it implied that if the certificate is not trusted, the connection will drop and no remote desktop session will be established, however that was not what I saw in practice. (I'm sorry, I lost the URL to the article)

Did I misconfigure the terminal server somehow? Did I misinterpret something?


.

Relevant Pages

  • Re: L2TP/IPSec from XP client to Windows 2003 Server
    ... ie no valid cert found on client - contacted Microsoft ... Windows Server 2003 Certificate Authority running ... The next step is to install Certificate Services on the Windows Server ... From Networks Connections on the client, ...
    (microsoft.public.security)
  • Unable to read data from the transport connection: An established connection was aborted by the soft
    ... I have created a x509 self signed certificate and installed in my client ... SslPolicyErrors sslPolicyErrors) ... Unable to read data from the transport connection: ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: schannel failure between AD CA and NT Domain
    ... Is the root CA certificates trusted on both the client and server machines? ... I have installed the Windows Certificate ... > connection to the retrieve info. ...
    (microsoft.public.win2000.security)
  • RE: VPN using L2TP
    ... Certificate Stores could not be enumerated. ... The next step is to install Certificate Services on the Windows Server ... At this point it is best to configure a client and verify that base ... From Networks Connections on the client, ...
    (microsoft.public.windows.server.sbs)
  • [PATCH 0/5] [RFC] AF_RXRPC socket family implementation [try #3]
    ... These patches together supply secure client-side RxRPC connectivity as a Linux ... kernel socket family. ... presentation side is left to the client. ... Each connection goes to a particular "service". ...
    (Linux-Kernel)