Apple’s Worldwide Developers Conference to kick off June 10 at 10 a.m. PDT with Keynote address
The Keynote will be available to stream on apple.com, the Apple Developer app, the Apple TV app, and the Apple YouTube channel. On-demand playback will be available after the conclusion of the stream.
The Keynote will be available to stream on apple.com, the Apple Developer app, the Apple TV app, and the Apple YouTube channel. On-demand playback will be available after the conclusion of the stream.
Looks like no one’s replied in a while. To start the conversation again, simply
ask a new question.
I have one computer that will not allow me to observe or control it. However, I am able to copy software to it. The client has been updated. The settings are all just as the other computers. It worked fine one day and then on the next day began giving an error 'connection failed' when trying to control or observe it though I was still able to copy files to it. Please advise.
I am having the same problem with 3-5 computers in my lab. The weird part is that they are all in a row! I can also copy software but I can not control/observe.
I am having the same problem with 3-5 computers in my lab. The weird part is that they are all in a row! I can also copy software but I can not control/observe.
After spending 1 hour and 18 minutes on the phone with an apple tech, we got my issue resolved. Basically I had to delete the client from the problem computer and reinstall. It takes many steps to delete the client and he asked that I not do it without direction of a trained tech. I must say that the tech I was speaking with had never seen the problem and was a bit stumped. He was going to look further into it.
I suggest that you try reloading the client by downloading the update to 3.1 off the website (it contains the full client package) and DO NOT try to delete the client first. If that doesn't fix it, call tech support and tell them to refer to the DELETE APPLE REMOTE CLIENT article so that they can walk you through the steps. It will only take a few minutes to delete it even though I was on the phone for a long time. It took the apple tech a while to figure it out and we tried many other options first.
Just sitting on the phone waiting for Apple support, so thought I'd share what's happening to me...
I have the same problem on 4 out of 9 machines in one network I support. It started after I updated the clients to 3.2.1 using the upgrade client software command from the admin machine. The Admin was already on 3.2.1, and all was working properly until I upgraded these clients. After that, I can generate reports, copy software, run the client software update over and over, however I can't actually control or observe the work stations with the error message of "Connection Failed".
Since the problem occurred last week, I called Apple, requesting the procedure to delete all files and clean reinstall the client software. They instructed me that it was
1. likely the network, which I had rebooted all switches and hubs to no avail; and...
2. if I planned on uninstalling and reinstalling the clients, I should also do a clean install of the admin at the same time. The tech at Apple told me the procedure is written out in full in the manual, and in fact, on page 46-48 of the administrators guide all steps are there. I followed the steps carefully and precisely, and clicked the Y key about 100 times at one point as one of the steps has a remove command with no recursive and it asks you to confirm every file and folder to be deleted. (my strong point is not unix, or otherwise I would have probably caught onto the command and edited it).
3. Finally they wanted me to do a clean install from the original CD, which I attempted. However, after clicking Continue/Agree through the dialog boxes, the final install box had a stop sign on the boot drive, with the message that "You cannot install this software on this volume. A newer version of this package is already installed."
After that, I again did a full uninstall, and terminal told me over and over that the folders/files I was trying to remove did not exist, so obviously my first attempt at uninstalling had been successful. Tried again to install fresh, but got the same message. Rebooted several times and tried again, but still the same message.
I am now on hold (in a holding pattern?!?) awaiting further Apple support. I haven't gotten as far as attempting to uninstall/reinstall any workstation software as the admin software install has come to a halt. I also have no desire to drive the 750 miles on winter roads to fix the problem onsite, so anyone with ideas, please speak up.
Oh, by the way, I access this network externally using Timbuktu from my Laptop, so I can still access the server where ARD admin is installed, but I can't ARD to any of the workstations within the network. does that make sense?
I got an answer from Apple, after a couple of calls and doing a couple of things. There were a couple of old ARD related packages in the Folder /Library/Receipts. These were deleted, but it made no difference.
Finally had some success today...
The conflict I was having of a newer version installed actually referred to the client software, not the server, but the server installer still saw it as a newer version. By deleting the folder "RemoteManagement" which is in /System/Library/CoreServices, Remote Access can be installed successfully. It worked!
I'm told this same folder should be deleted on the workstation if there are upgrade problems on the workstation...
aarrrgggggg... I have the same issue, no real solutions anywhere on this forum, just random (although very creative) solutions, none of which work or would pass QA in the real world, what gives here???
The solution that has worked for is this: log onto the account that is having the problems. Go into the home folder of the user and delete the following
/Users/%user account%/Library/Preferences/com.apple.RemoteDesktop.plist.
When you start ARD it will create a new preference file and you will need to set up ARD again but at least you can use it now. I hope this helps.
Regrettably, I see no such preference file on the remote (client) machines. I do see this preference file on the ARD Administrator machine, and deleting it does temporarily restore ARD's ability to connect, only to see that ability crash once again into the rocks of ARD's incessant bugs. Apparently, more than simply trashing this preference file is needed to truly fix ARD 3.2's connect ability.
To heck with it, I'm off to buy more copies of Timbuktu. It's UI is a blast from the past, the cost is outrageous, but at least it reliably works, and my time is too valuable to squander on any more of Apple's lame and useless software. Adios amigos/amigas.
I had a similar problem trying to access Leopard Macs.
It appears that in Leopard the Application folder, and all folders within it, has permissions set that so that no alterations can be made to any file, application etc. This in some manner is preventing access to Desktop by ARD, plus messes up many minor alterations that you may wish to effect
The solution kindly provided by 'biovizier' is as follows:
I spoke too soon! They maintained ADB Observe/Control functions for a couple of reboots but then failed once again and we're back to where we started - just hanging.
Just encountered one client out of a set of 30 with this same predicament. I have tried several variations on setting changes to no avail. Has anyone come up with a better solution since this thread started a while back?
I'll keep my own results as soon as I get lucky 🙂
I ran into this problem recently trying to setup an ARD client on a server and connect from my laptop. I kept receiving the Authorization Failed message. I tried the uninstall and reinstall bit without success. I performed the "kickstart" command from the terminal "$ sudo /System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources/k ickstart -activate -configure -access -on -restart -agent -privs -all" without success.
Finally, on my Macbook pro I opened the ARD console. I deleted the server from the list "Edit > Delete". Then went to the scanner and scanned from computers and my Mac Server was discovered. This time when I added the computer it allowed me to put credentials in and presto I was able to connect without issue. Seems simple but this answer eluded me for 3 days. Thought I would post it just in case this does the trick for someone else.
"I am unable to share a screen with ANY Networked MacBooks using ARD 3.When I try to share my screen or another with my networked MacBooks, it will work for 1-2 seconds then turn off. I have no problems with other intel machines nor PPC's. I CAN share a screen if the MacBooks are not bound to a server. I have tried binding and unbinding to 2 different servers in different buildings, doing clean installs etc. It does not work when using a G5 admin station either."
This happened to me and my fix was to edit the info for the clients I couldn't observe/control and remove the DNS name entry. Then I could observe/control to my hearts content. That's baffled me for a while as back in March ARD was unable to resolve DNS names and I couldn't ssh into any of my boxes using DNS names.
