Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

Recently we enabled FIPS 140-2 Encryption Algorithms on our W2K3 server per http://chadamberg.com/drupal/IISCryptography and now my Mac RDP 2.1.1 client won't connect. I get:

"Remote Desktop Connection cannot verify the identity of the computer to which you want to connect...."

My client is set to "Always connect, even if authentication fails" but that doesn't seem to help. I'm guessing there's some incompatibility between FIPS support and Mac RDP. I can still get in via my Win7 RDP client. I tried CoRD as well, but it failed to connect.

Any ideas on how to reinstate Mac RDC to this server, or am I at the mercy of MS updating their Mac client?

share|improve this question
    
Good question... racking my brains for ideas... TS web app won't work due to Active-X requirements... mac client does not support TS gateway redirection... maybe citrix? Personally I'd use vmware view to fix this. –  SpacemanSpiff Jan 24 '12 at 23:04

1 Answer 1

Any ideas on how to reinstate Mac RDC to this server, or am I at the mercy of MS updating their Mac client?

The Mac RDP client is likely not presenting a 'valid' MS client certificate to the other server, so it's refused. Unless the new security features are enabled on Mac RDP it won't work and you'll need to use Windows or something out-of-band.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.