Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Isamtron

macrumors newbie
Original poster
Jul 24, 2010
12
0
Hello,

I tried the application from Microsoft called "Remote Desktop Connection Client for Mac 2" to access Windows 7 through Mac but it didn't work... maybe because it's only compatible with Vista and XP?

Any other solutions on how can I access my Win 7 through Mac? I don't want to use BootCamp or virtualization junk.

I have the Mac and the PC at home, getting the internet connection from my Time Capsule.

Please help.
 
It should be fine if you have either Ultimate or Professional editions. However bootcamp or virtualization will run faster because it doesn't need to go over the network.
 
I got RDP to work with my WHS. For some reason it wouldn't connect using the server name. I had to use the IP address of the server instead.
 
As talmy said, first check your version of Windows 7. It needs to be Professional or Ultimate; other versions don't have the component necessary for RDC to connect to.
 
As talmy said, first check your version of Windows 7. It needs to be Professional or Ultimate; other versions don't have the component necessary for RDC to connect to.

And remote settings need to be specifically turned on http://www.howtogeek.com/howto/windows-vista/turn-on-remote-desktop-in-windows-vista/

If the problem is really in the client, you could always give CoRD a try. http://cord.sourceforge.net/.

EDIT: Note that the latest client from Microsoft has worked fine for me to servers running XP, XP64, Vista, Vista64, 7, 764, Windows Server 2003, Windows server 2008.

B
 
+1 for CoRD. The Microsoft RDP client was good around the Tiger timeframe. It seems to have gotten flakier over the years. I have some computers that it just WILL NOT connect to, while other RDP clients have no problems at all.
 
+1 for CoRD. The Microsoft RDP client was good around the Tiger timeframe. It seems to have gotten flakier over the years. I have some computers that it just WILL NOT connect to, while other RDP clients have no problems at all.

The V2 client that was released post Intel transition is actually quite a bit better than CoRD (IMHO, of course). CoRD blows the V1 client out of the water though and is a good cross check when something isn't working.

B
 
The V2 client that was released post Intel transition is actually quite a bit better than CoRD (IMHO, of course). CoRD blows the V1 client out of the water though and is a good cross check when something isn't working.

B

I've been using the V2 client since it was released. It's sketchy for me. Sometimes it connects to a machine, sometimes it doesn't. CoRD (so far) hasn't failed to connect.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.