Problem connecting with RDP between Mac and Win2k3 server

Question

I have an iMac running Mac OS X 10.5.8 and the RDP Connection Client 2.0.1.

http://salle.dyndns.org/misc/rdp%5Fproblem1.png

When I try to connect to a Windows 2003 Server on the same network I get a dialog saying "Remote Desktop Connection cannot verify the identity of the computer that you want to connect to".

Picture: salle.dyndns.org/misc/rdp_problem2.png

And when I press the Connect-button in the previous dialog I get the same message in another dialog:

Picture: salle.dyndns.org/misc/rdp_problem3.png

I can connect to the Win2k3 server from a Vista machine, and it used to work from the Mac as well. I stopped working from the Mac after I did some configuration on the win2k3 server, removed and added the the connection in the Terminal Services Configuration:

Picture: salle.dyndns.org/misc/rdp_problem4.png

What do I need to do to be able to connect from the Mac again?

(I have not enough reputation to post multiple links or images)

Answer 1

In Remote Desktop on your Mac open Preferences -> Security.

Make sure that the first 'Always Connect' option is chosen.

After that, you might want to try CoRD (http://cord.sourceforge.net/), which is an open-source Remote Desktop client that has some better tweaks and error messages.

Answer 2

Solved it, I changed encryption level on the connection in the Terminal Services Configuration dialog to "Client Compatible".

http://salle.dyndns.org/misc/rdp%5Fproblem%5Fsolution.png

Answer 3

CoRD solved my problem, and some other minor problems too :) I recommend it!

Answer 4

We just had this same issue with a WS2008R2 and a Mac. Connected from mac via microsofts RDP program. Suddenly disconnected with that message. Subsequent attempts at logon from Mac gave same message and immediate disconnection.

Settings on the server were as user23294 mentioned, set to compatible, and the setup has worked fine up till now (many months).

Solution was to logon from a windows client, close programs and log user off.

Then the user could again log on from a Mac.

Apparently the user session became corrupted somehow, preventing access from a Mac, but not from another Windows client.