Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


RDC for Mac

  • Please log in to reply
1 reply to this topic

#1 ThomasDG


  • Members
  • 59 posts
  • Gender:Male
  • Location:Carmel, IN
  • Local time:11:39 PM

Posted 28 January 2013 - 09:28 AM

I am using a mac computer at home to connect to my windows 7 computer in the office. I have been able to do this for months, but today began to receive an error. I am able to connect to the static IP and enter my credentials and everything goes through properly. I get the certificate warning and click ok. Then I receive a pop up that says "the remote computer is not allowing connections from the Mac.Make sure that you have permission to connect to the remote computer, and that you typed the correct credentials."

I have changed the security settings of RDC on the MAC to "Always connect, even if authentication fails" as many people have suggested in other posts.

Do you have any other suggestions?


BC AdBot (Login to Remove)


#2 cloudnyn3


  • Members
  • 7 posts
  • Local time:10:39 PM

Posted 01 February 2013 - 01:44 PM

Just a quick question, is your MAC part of a domain (ie. \\work.com) or are you just RDC'ing straight to your 7 client at work?
Also, do you VLAN to the client or are you just making a straight shot over the internet? You need to be logged into the win 7 machine but not using it. If someone moves the mouse or touches the keyboard you'll be kicked immediately because RDC thinks your back at your station.

A firewall is another issue, it may allow you to enter credentials and all that, but is it actually making its way to the client?
You may get stopped by a firewall and the RDC host may just see that as a denial of connection and return an error that it believe to be the cause.

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users