For Windows 2003 (32-bit and 64-bit) OS security has been enhanced and as such has the following effects:
Originally Published: 2007-09-12
Article Number
Applies To
Microsoft Remote Desktop
RDP
terminal
service
security
Microsoft Windows
microsoft
Issue
Resolution
The enVision appliance OS using Windows 2003 has been configured to require strong encryption to be negotiated for applications that must use the cryptographic services. Strong encryption may be Federal Information Processing Standard (FIPS)-compliant encryption.
- This setting affects Terminal Services in Microsoft Windows Server 2003. By default, when this setting is not enabled on the client or on the server, the Remote Desktop Protocol (RDP) channel between the server and the client is encrypted by using the RC4 algorithm with a 56-bit key length. After this setting is enabled, the RDP channel is encrypted by using 3DES in Cipher Block Chaining (CBC) mode with a 128-bit key length, if the client supports it. Also, a client must use the RDP client version 5.2 or a later version to connect.
- Encrypting File System (EFS) is also affected by this setting. By default, Windows XP uses the Data Encryption Standard (DESX) algorithm with a 56-bit key length. If the Windows high encryption pack is installed, the key length for this algorithm is Triple-DES (3DES) or 128 bits. By default, on Windows XP Service Pack 1 (SP1)-based and Windows Server 2003-based computers, EFS uses the Advanced Encryption Standard (AES) algorithm with a 256-bit key length. However, if you enable the System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing setting on these computers, the operating system will use 3DES with a 128-bit key length instead.
More information can be found at http://support.microsoft.com/kb/811833 - Installing applications via RDP
Related Articles
Issue with FSM file shares being lost until the server is rebooted. 1Number of Views Which signature algorithms are supported when re-signing server certificates? 24Number of Views Access Requests and Workflows rely on the Application Server and Database Server times to be in synch in RSA Identity Gove… 28Number of Views How to disable the automatic startup of RSA Identity Governance & Lifecycle when the server is rebooted 78Number of Views Aveksa Hardware Appliance did not start after a reboot 25Number of Views
Trending Articles
RSA Authentication Manager Upgrade Process RSA Release Notes for RSA Authentication Manager 8.8 RSA RADIUS Server service failed to start in the RSA Authentication Manager 8.1 Operations Console Microsoft Entra ID External MFA - Relying Party Configuration Using OIDC - RSA Ready Implementation Guide RSA Release Notes: Cloud Access Service and RSA Authenticators
Don't see what you're looking for?