Apple Remote Desktop Client
Gibert Chisholm
You can use the Remote Desktop client for Mac to work with Windows apps, resources, and desktops from your Mac computer. Use the following information to get started - and check out the FAQ if you have questions.
We're testing new features on our preview channel on AppCenter. Want to check it out? Go to Microsoft Remote Desktop for Mac and select Download. You don't need to create an account or sign into AppCenter to download the beta client.
If you already have the client, you can check for updates to ensure you have the latest version. In the beta client, select Microsoft Remote Desktop Beta at the top, and then select Check for updates.
A Remote Desktop Gateway (RD Gateway) lets you connect to a remote computer on a corporate network from anywhere on the Internet. You can create and manage your gateways in the preferences of the app or while setting up a new desktop connection.
If you're running macOS X 10.9 and have disabled Displays have separate spaces in Mavericks (System Preferences > Mission Control), you need to configure this setting in the Remote Desktop client using the same option.
Drive redirection is supported for remote resources, so that you can save files created with a remote application locally to your Mac. The redirected folder is always your home directory displayed as a network drive in the remote session.
By default, the remote session will use the same keyboard locale as the OS you're running the client on. (If your Mac is running an en-us OS, it will be used for the remote sessions as well.) If the OS keyboard locale is not used, check the keyboard setting on the remote PC and change it manually. See the Remote Desktop Client FAQ for more information about keyboards and locales.
The only way I managed to resolve this issue was to create a new admin user account on the remote client and re-authenticate (delete or edit details of the the connection) with new details. This then sorted the access denied issue.
Then on the computer you are running Remote Desktop, select All Computers in the left column. Then right-click (tap with 2 fingers) the computer you want to access, select Get info, and then under the Attributes, change the login name to the remote computer's account name without spaces. This should resolve the problem of denied access via Remote Desktop 3.9 (assuming the password is correct).
Or forget Remote Desktop, and instead use Finder, select the shared computer in the left column you want to access, and then select the Share Screen feature. Then login. That method still worked for me, even though I was denied access to the same remote computers via the Remote Desktop app. Go figure.
Note: I had to use the Finder method (share screen) to even get to the remote Mac's in order to fix the problems with Remote Desktop 3.9. I've had similar problems in the past (prior to Yosemite if my memory is correct), and I suspect these are due to the underlying Unix requirement of computer account names that don't have spaces or single quotes as part of the name--causes parsing problems since these characters serve as delimiters in certain contexts. Sigh...
I used the shortform login ID's to temporarily solve the problem but it comes back in spades. What's worse is that i maintain over a hundred computers around the world remotely and this has turned into an absolute catastrophe for me.
I found that after updating the ARD application and all the remote clients, I had to re-enter the credentials to each computer in ARD by getting Info on each one and edit the username/password. If the remote boxes are old version of the OS, also set under the ARD preferences in Security to support older versions.
Internet Gypsy's solution is what finally worked. I created a new Administrator account and used that login info for setting up the client computer and thankfully that solved the problem. Thanks Internet Gypsy!!
I was having the same problem, and after talking with Apple Support, we were able to work around this by making sure that the login information is using the short name of the client instead of the long name. For example, say the client has a login of "Patty Smith" and the short name is "pattysmith", the login settings for that client in Remote Desktop 3.9 must use the short name "pattysmith" otherwise access will be denied.
After discussing the same problem I had with Apple Support, we were able to resolve the problem by making sure we were using the short version of the client user names. For example, if the user name on the client computer is "Patty Smith" with the short version "pattysmith", and in my case I was using the long names, by changing the logins to the short names, I was able to connect.
I wasn't having trouble connecting to older versions of clients after checking the "Allow communication with older clients box in the preferences." But I was having trouble once those clients upgraded to the new ARD 3.9. I was repeatedly getting access denied messages.
3. Go to the ARD Scanner tab > connect to the desired client > on the login screen use the previously noted user home folder name exactly as it appeared on the clients system as the user name, and enter the password.
The short name is not the only problem! All my computers have ALWAYS used short name and none of them work when upgraded to 3.9. I have reinstalled Sierra on the client computers, re-attched them to ARD, and as soon as they are upgraded they lost the ability to SEND UNIX, COPU, INSTALL etc, i.e. Screen Sharing only.
We already had all lower case and no spaces in the name, and it still would get "Access Denied" - though I could still control the remote system. Remove the computer from the "All Computers" and re-adding it removed the "Access Denied", but we still can't perform any tasks (Copy Items, Unix commands), as it gives a "not authorized" error.
I administer a number of Windows machines, and am trying to find a really good application to remote desktop in to them from my Mac. I've tried CoRD, and I really like its library approach to saved sessions (as opposed to Microsoft's file based approach), and tabbed sessions are great when working on a bunch of machines. Unfortunately, it's just too buggy for serious use, and given that it averages less than 2 releases a year, I have little hope that that will change. Microsoft's official client is very bare bones and doesn't support connecting on non-standard ports (which I need).
In my experienced opinion, CoRD and Jump Desktop are the best RDP clients for Mac. CoRD is more for those that know what they're doing - it's simple, stable, fast and reliable. Jump Desktop however is for those that are new to Remote Desktop Connections and want something that makes things easy. It's easily the slickest RDP client for Mac too and looks great. There's a useful extensive review of the best RDP clients for Mac here: -for-mac/
If you are willing to spend some money, there is LogMeIn, which I have used for my home Macs with great success. On the free side, we used to use "Chicken of the VNC" but decided to go with Microsoft's official client for reasons unknown to me. Six of one half dozen of the other, if you ask me. Frankly, the VNC market is pretty banal.
Chrome Remote Desktop is cross-platform. "Provide remote assistance to Windows, Mac and Linux users, or access your Windows (XP and above) and Mac (OS X 10.6 and above) desktops at any time, all from the Chrome browser on virtually any device, including Chromebooks."
I've been using it since Tiger. It began crashing intermittently with OSX Yosemite, then would always crash on quitting with El Capitan before 10.11.4, and often crash on changing screen resolution. After 2 days of use, I have no longer seen a crash with OSX 10.11.4.
try Teamviewer I am not sure about the multiple tabs for easy switch never had a chance to test it. Also you can set it for lan incoming connection so you can connect via a lan rather than internet.You can create a free account and add all machines to it, So you can even see which system is on and connect with one click
I remote access several dozen other computers on a daily basis with the same build as the MacPro. There is no discernable difference between them. ARD is showing the device as accessible and I can use other functions in the Manage and Interact ARD menu (Chat, restart, sleep, wake, etc.)
Something you may have already tried but my usual fix for this - not great I know but, over the years, it's the one that reliably works, generally - is to remove the client from the All Computers list and then re-add it. Call it a 'feature' of the application.
c80f0f1006