Post by KKI TechnologiesPost by KKI TechnologiesWe have Windows 2003 Terminal Servers set with compatible encryption which,
if I understand correctly, means that the maximum encryption of the client
will be used for encrypting the connection.
It is my understanding that it depends on both parties (the client and the
server). In your case it will depend if the client will support it... of
course the easiest way to test this is to set the server to only allow High
encryption and check if clients can connect :-)
BTW - Check out this whitepaper:
http://www.microsoft.com/downloads/details.aspx?FamilyID=402a0cd1-9e4d-4007-8eaf-c30623e71250&DisplayLang=en
<Snip>
Windows Server 2003 Terminal Services supports four levels of encryption:
Low, Client Compatible, FIPS Compliant, and High. The following list
describes what each encryption level provides:
High: (Recommended) Windows Server 2003 uses this level of encryption by
default. High encryption encrypts the data transmission in both directions
by using a 128-bit key. Use this level when the terminal server runs in an
environment that contains 128-bit clients. Clients that do not support this
level of encryption cannot connect.
RDP traffic is encrypted using 128 bit encryption when connecting to Windows
Server 2003 from a Windows XP client computer. The algorithm used for
encryption depends on the encryption mode. In non-FIPS mode, RC4
(encryption) and MD5 (keyed hashing) are used. In FIPS mode, 3DES and SHA1
are used. By default, both the Web-based and the standalone remote desktop
client send the encrypted RDP traffic over TCP port 3389.
<end Snip>
--
Javier [SBS MVP]
www.msmvps.com/javier
<< SBS ROCKS!!! >>
Post by KKI TechnologiesWe have Windows 2003 Terminal Servers set with compatible encryption which,
if I understand correctly, means that the maximum encryption of the client
will be used for encrypting the connection.
Does anyone know what the encryption setting is for RDP 5.2?
Thanks for the assist.
--
Jonathan Filson
KKI Technologies
Small Business Specialist