Blog Post

CoRD: Connect to Windows PCs From Your Mac

Stay on Top of Enterprise Technology Trends

Get updates impacting your industry from our GigaOm Research Community
Join the Community!

While many web workers use (and love) Macs (s aapl), most of the rest of the world still uses Windows PCs (s msft). So what do you do if you need to connect to, or control, a client’s Windows machine? Microsoft offers its free Remote Desktop Connection Client, but its interface doesn’t make it that easy to use. There is a free open-source alternative, CoRD, which has just been updated to version 0.5. Andrew over at TheAppleBlog has been taking the new version for a spin, and highly recommends it. He particularly likes the way that CoRD supports multiple connections, selectable from a list. The new version also gets props for support for Windows 7, Windows Vista and Windows Server 2008, and interface and performance improvements.

CoRD is a free download for OS X 10.5 or later. Check out the post over at the TheAppleBlog for more detail.

Do you prefer CoRD or Microsoft Remote Desktop Connection Client?

11 Responses to “CoRD: Connect to Windows PCs From Your Mac”

  1. Coming in late to the party…

    If you’re connecting to Vista or Win7, and using the Aero interface, even if you have themes and backgrounds disabled, the cursor remains an “Aero” cursor. Setting this to _anything_ other than the Aero cursor will pep this right up. This is a known glitch with later versions of the RDP protocol, rdesktop can’t properly handle that cursor.

    CoRD is based upon rdesktop, so we’re hamstrung by their stagnated development process. The codebase hasn’t seen marked improvements since the release of 1.6 a year and half ago. Many of the features of RDP6 and 7 are missing from it, and several RDP5 features are incomplete.

  2. Well, Snow Leopard broke Microsoft’s RDC so I gave CoRD a try. The problem is that it’s very slow even with themes and backgrounds turned off. What I ended up doing since I already run Parallels, is to just use my WinXP to RDC.

  3. As much as I hate to say it, tried CoRD for a couple of days and ended up going back to RDP.

    Typically I have 3 or 4 remote servers opened and CoRD had trouble switching between them. It crashed twice earlier today and had trouble keeping up with my keyboard commands while I used Outlook on my remote Windows desktop.

    I’ll test future versions, but for now I am sticking to what works.

    • I find both CoRD and Microsoft’s RDC 2.0 pretty slow– using the generic rdesktop RDP client via X11 [installed via fink’s unstable package distro] is much faster than both, which is so irritating.

  4. @Klaus S — if that happens (and it’s extremely unlikely) and CoRD doesn’t get updated (also unlikely), you could always switch to the official MS client.

    Whether to use CoRD or the MS client is a matter of personal preference — as both are free, there’s no harm in trying both.

  5. I’d stick to a standard rdp client. If tomorrow Microsoft will change something, all others can turn into a pumpkin :-) Well, though its not likely to happen to RDP, I still don’t find standard remote desktop to be difficult at all.