Connecting to your Windows Machine Remotely From Your Macintosh

I’m originally a Windows guy, fortunately Small Dog helped me see the light and now I use mostly Macintosh computers. There are several times when I need to use Windows so I keep a few Windows machines around. I’ve attempted to use a VNC server on my Windows machine and Apple Remote Desktop to access it but it’s been really slow and unresponsive every time I’ve tried to do it this way. I pretty much gave up on the idea until today.

I did a quick search on the Apple Discussion forums about how one would go about remotely controlling their Windows PC from their Macintosh computer. The discussion thread that helped me the most was:

Apple Discussion Board Thread

It linked to Microsoft’s website for their Macintosh Remote Desktop Control application. I was stunned, mostly because I couldn’t believe I didn’t know about this program. You can see this website here:

Microsoft Remote Desktop Client

The piece of software is free and works, looks and acts just like the Windows version (which I was pretty used to). The software only works on specific versions of Windows, Windows XP Professional, Windows Server 2003, Windows 2000 Server, Windows 2000 Advanced Server, Windows 2000 Datacenter Server, Windows NT Server 4.0, Terminal Server Edition so no Windows XP Home. You will also need to configure Windows to allow remote desktop control (much like allowing Macintosh to accept remote control). Then you can use the Remote Desktop Control client program to access that Windows machine.

This is especially nice for me in that I can now move my PC away from desk, free up some space and I can remotely control it to use those few Windows applications I need. It’s even nicer because I don’t actually have to be on my home network to access the computer either. I can be in China!

If you’re looking to access your PC from your Mac while connected to another network (example. connecting to a work PC from your Mac at home) this is possible to do and fairly easy to accomplish. If you have a router you will need to forward port 3389 to the computer you want to connect to. If you don’t have a router then all you need is your IP address (http://www.whatismyip.com) and you can use that! While that is a very basic explanation of how to do this, you can use Google to search for more information about doing this.

This link might also prove to be useful to some:

Networking Remote Desktop with Windows

Similar Posts

  • Michael Bartosh, Rest in Peace

    My heart dropped into my stomach this morning when I read the news that Michael Bartosh, an excellent Mac OS X Server technologist,…

  • Powerbooks that Boot Into Sleep Mode

    By Jon@Smalldog.com In this past week, I have come across three Powerbooks that constantly BOOT into sleep mode. Regardless of OS install, these…

  • User Tips Library

    From Art Hendrickson Every Mac user should know how to get help or research an issue when something goes awry with the normal…

  • Google + Nest = Nest+?

    You may have heard that yesterday, Google acquired “*Nest,*”:https://nest.com the company most known for its smarter, simpler thermostat design. Reactions to the sale have been largely negative, at least according to “*fans of Nest on Facebook.*”:https://www.facebook.com/nest/posts/10152167824360681 What would this mean for your privacy? For device support (especially non-Google devices such as iPhone)? ARE WE ALL GOING TO BE WATCHED IN OUR HOMES?

    I’ve been intrigued by Nest’s thermostat design since it was developed by Nest Labs in 2011, and still believe that it has set a standard for innovation and what it means to have a “connected home” — a term that has proven to be highly sought after in the past few years. I mean, you can leave the over-the-top “smart” tech products at CES (except for the WeMo-enabled “*Belkin Crock-Pot*”:http://www.macrumors.com/2014/01/07/belkin-slow-cooker/ … I think I’d love that guy), but Nest makes a lot of sense for the average home.

    Recently, Nest Labs introduced a smarter “*smoke and carbon monoxide detector,*”:https://nest.com/smoke-co-alarm/life-with-nest-protect/ taking on another mundane household staple that they determined significant improvement (for the annoyance factor alone). That brings the total number of products to two. Two. For which Google paid 3.2 billion! Obviously, they were viewed as game-changers.

    So, what do you think Google plans to do with Nest? We’d love to hear your thoughts!

    More on the acquisition “*here.*”http://online.wsj.com/news/articles/SB10001424052702303595404579318952802236612

    More on the Facebook backlash “*here.*”:http://www.adweek.com/news/advertising-branding/most-nests-facebook-fans-dislike-google-deal-154974