Guest TR Posted July 18, 2008 Posted July 18, 2008 I have configured a W2K3 R2 server as a terminal server. I have enabled SSL over RDP on the connection. I have set all the parameters correctly in the Terminal Services Configuration manager per article KB895433 and remote users can successfully connect using SSL, however those who are not changing their security level on their RDP client are still successfully connecting and the Terminal server is not denying them. I cannot seem to force the Terminal server to deny those who do not have high encryption selected on their RDP client. Thanks TR
Guest Vera Noest [MVP] Posted July 18, 2008 Posted July 18, 2008 Re: Using SSL KB 895433 lists many different options. On the server, what did you configure under "Security layer"? Negotiate, or SSL? _________________________________________________________ Vera Noest MCSE, CCEA, Microsoft MVP - Terminal Server TS troubleshooting: http://ts.veranoest.net ___ please respond in newsgroup, NOT by private email ___ "TR" <TR@somehwere.com> wrote on 18 jul 2008 in microsoft.public.windows.terminal_services: > I have configured a W2K3 R2 server as a terminal server. I have > enabled SSL over RDP on the connection. I have set all the > parameters correctly in the Terminal Services Configuration > manager per article KB895433 and remote users can successfully > connect using SSL, however those who are not changing their > security level on their RDP client are still successfully > connecting and the Terminal server is not denying them. I > cannot seem to force the Terminal server to deny those who do > not have high encryption selected on their RDP client. > > Thanks > TR
Guest TR Posted July 18, 2008 Posted July 18, 2008 Re: Using SSL Hi Vera, I configured SSL. All my clients use RDP version 6.0. I have a valid certificate purchased through a CA authority. I have to instruct all remote clients to select 'Do not connect if authentication fails', under the Advanced Tab of the RDP client, however if they forget to change this, the server allows them to connect anyway and the Session is not secure. I have not been able to figure out how to force the server to require SSL and not connect the client if the client's default settings are anything but the 'Do not connect' thanks TR "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in message news:Xns9ADFDC71F4DF9veranoesthemutforsse@207.46.248.16... > KB 895433 lists many different options. > On the server, what did you configure under "Security layer"? > Negotiate, or SSL? > _________________________________________________________ > Vera Noest > MCSE, CCEA, Microsoft MVP - Terminal Server > TS troubleshooting: http://ts.veranoest.net > ___ please respond in newsgroup, NOT by private email ___ > > "TR" <TR@somehwere.com> wrote on 18 jul 2008 in > microsoft.public.windows.terminal_services: > >> I have configured a W2K3 R2 server as a terminal server. I have >> enabled SSL over RDP on the connection. I have set all the >> parameters correctly in the Terminal Services Configuration >> manager per article KB895433 and remote users can successfully >> connect using SSL, however those who are not changing their >> security level on their RDP client are still successfully >> connecting and the Terminal server is not denying them. I >> cannot seem to force the Terminal server to deny those who do >> not have high encryption selected on their RDP client. >> >> Thanks >> TR
Recommended Posts