T
trev
I have one WinXP Pro system and one WinXP MCE system on a local network.
Each system has Terminal Services Client 6.0 installed.
If I enable the "System cryptography: Use FIPS compliant algorithms for
encryption, hashing, and signing" option in GP on only one of the two
systems, I can still connect to that system from the other. However,
the reverse is not true: With that setting enabled on a given system, I
can't connect to the other from it.
To summarize:
FIPS on server => RDP works
FIPS on client => RDP doesn't work
The error I get, immediately upon trying to connect via RDP, is:
The client could not establish a connection to the remote computer.
<----------------------------------------->
The most likely causes for this error are:
1) Remote connections might not be
enabled at the remote computer.
2) The maximum number of connections
was exceeded at the remote computer.
3) A network error occurred while
establishing the connection.
4) The remote computer might not support
the required FIPS security level. Please
lower the client side required security
level Policy, or contact your network
administrator for assistance.
<----------------------------------------->
FIPS is supported by the TSC, not by Windows itself. So...why on earth
would this error occur?
Each system has Terminal Services Client 6.0 installed.
If I enable the "System cryptography: Use FIPS compliant algorithms for
encryption, hashing, and signing" option in GP on only one of the two
systems, I can still connect to that system from the other. However,
the reverse is not true: With that setting enabled on a given system, I
can't connect to the other from it.
To summarize:
FIPS on server => RDP works
FIPS on client => RDP doesn't work
The error I get, immediately upon trying to connect via RDP, is:
The client could not establish a connection to the remote computer.
<----------------------------------------->
The most likely causes for this error are:
1) Remote connections might not be
enabled at the remote computer.
2) The maximum number of connections
was exceeded at the remote computer.
3) A network error occurred while
establishing the connection.
4) The remote computer might not support
the required FIPS security level. Please
lower the client side required security
level Policy, or contact your network
administrator for assistance.
<----------------------------------------->
FIPS is supported by the TSC, not by Windows itself. So...why on earth
would this error occur?