ARD Client 3.2.2 update - HD at AirPort unaccessible

After upgrading to ARD Client 3.2.2 via Software Update, I cannot use the drive that is attached to my AirPort Extreme base station anymore from the 10.5.8 Mac ONLY! (Macs running 10.6.2 can use the drive!)
What might be wrong?
Please help!
Thanks,
Carl

After re-programming (back to factory settings) both AirPort base stations, the problem was solved.

Similar Messages

ARD client software too old, update fails - ARD client up to date

I am trying to access a friend's macbook using ARD 3.3. I can find the machine's IP over the internet but cannot access it. Under the info pane it says the the client software on the remote machine is too old, so I created an installer package to get her the right version, I also send her the link to apple's download site to download the latest version. On trying to install either of the packages she prompted with the message that the client software was already up-to-date.
In Apple help I found out that the remote machine needs to be configured to allow remote access, which can be done under System preferences/Sharing/Apple Remote Desktop. I guided her to that location but she said that this pane does not exist. Nor did she ever install ADR client on her computer, which makes me wonder about why the ADR client installer stated that the ADR client software was already running.
Any ideas about what is going on here?

I couldn't find the appropriate forum to post this, hence the double posting (soon to be triple). I'll close down the other two. Thanks for pointing me in the right direction.

HT5170 Why would I be getting this update if I am not, to the best of my knowledge, anyone's ARD client???

Why would I be getting this update if I am not, to the best of my knowledge, anyone's ARD client? I have not installed ARD in this computer, but am constantly getting permissions repair messages regarding remote management from Disk Utility. Very weird...

Yes, it's annoying but the messages are innocuous and you may ignore them. They will be repeated every time you repair permissions. The ARD client was installed by Software Update at some point in the past.
You don't need to repair permissions unless you've received a permissions error message from OS X.

Location of ARD client software

I upgraded the client to ARD3 on several ARD2 admin computers. Now Remote Desktop 2 won't open on these ARD2 admin computers. In order to still be able to use ARD2 on these ARD2 admin computers (until we get to purchase more licenses to update all of our ARD2 admin computers), I think I need to remove the ARD3 client and install back the ARD2 client. What is the location of the client? What other files, if any, do I need to remove before installing the ARD2 client back on the ARD2 admin computers?

Use the instructions here to remove the ARD 3 client. Then you can download the 2.2 client here; it says update, but it will install from scratch.
Regards.

ARD Client Doesn't Show When Using Scanner and Network Range

All-
When I use the Scanner in ARD3 to scan a remote Network Range over the internet, the ARD client that I KNOW EXISTS in that same IP range DOES NOT show up (other ARD clients that I'm not interested in do show up, but not the specific ARD client I need to observe/control).
If I then call the user at the remote ARD client on the telephone, and have them give me their IP address (using www.whatismyip.com, for example), I can use the Scanner in ARD3 to "find" the ARD client and add it to my All Computers list. Process: change the popup box to read "Network Address" instead of "Network Range" and set the IP address field to the address provided by the user.
Why doesn't the remote ARD client show up when I scan for it using a Network Range in ARD3? Obviously, I don't want to have to call up each user every time I need to perform maintenance/control a client to get their (dynamic) IP address.
I could use dynamic DNS, but that's overkill. If I know (from experience) that my ARD clients are in IP ranges X, Y, and Z, then I SHOULD be able to simply scan for them (or so I thought).
Any help appreceated.

Updated to ARD3.1 (admin and clients), but that did not solve the issue.
Let me try to restate the problem:
The ARD client is out of state/across the country (i.e., different sub-net) using a dynamically assigned IP adddress. I can (for now) connect to that ARD client successfully, and perform all ARD functions (that I've tried so far) becasue I know (for now) that client's IP address (I called and spoke with the user who used www.whatismyip.com to give me their IP address). So what's the problem, you ask?
Some time in the future, that same ARD client will have a new, dynamically assigned IP address. I'd like to be able to connect to that client without having to call on the telephone and ask the user what IP address they have been assigned now.
My thinking was that I could make a pretty good guess at their IP address (based on their old IP address, and the way Cable and Telco ISPs allocate/lease IP addresses). For example, if their current dynamic IP address is 999.888.777.45, I could guess that a subsequent dynamically assigned IP address would be in the range 999.888.777.2 to 999.888.777.255. With ARD, I could simply scan that range of network addresses using the Scanner and quickly find the ARD client I want.
I tried to do just that, and the ARD scanner did not find my client when I scanned the network range that the ARD client was actually in. It showed other ARD clients (that I do not administer, own, or want to hack into), but not the one I do want to observe/control/maintain (and have a legal right to). Somewhat paradoxically, when I used the Scanner to find the same ARD client by specific IP address, there was no problem.
Why doesn't the ARD Scanner "see" the ARD client when scanning the network range?

Downgrade ARD client software from 3.4 to 2.2?

Hi,
I'm running Apple Remote Desktop 2.2, however the Mac Pros (running 10.5.8) which I want to control have ARD Client 3.4 installed.
Is there any way to downgrade the client software so I can use ARD 2.2?
At the moment, when I try to, for example, send a message using ARD 2.2 to a Mac Pro running ARD Client 3.4 I get an error message reading:
"Failed on all. Status: Newer Client software (3.4)"
Many thanks in advance for any assistance.

ARD 2.2 is not supported on Leopard nor on Intel-based Macs. At least one user (raus), though, posted here that he got ARD 2.2 to work in Leopard, but there are no guarantees. From the finder, navigate to:
/System/Library/CoreServices/RemoteMangement
From the folder, delete (or move) the ARDAgent v3.X file. Reinstall the 2.2 update for ARD on the Apple site. (This may be optional; the original poster just reinstalled the update to be safe.) You can reportedly now run Remote Desktop 2.2 in 10.5. This works for PowerPC and Intel Mac.
Note, though, that this is completely unsupported by Apple and may or may not work, or may cause issues. For proper support for Leopard, you need ARD 3.2 or later. Your best option is to upgrade your administration system to ARD 3.4, which is available through the Mac App Store for only $79.99 for the unlimited-client version.
Good luck.

Error in accessing ARD client 2.2.1 from ARD admin 3.2 via Airport

Hi all,
I was successfullly accessing mac-mini machine having ARD client 2.2.1 which was connected to ethernet cable from ARD admin 3.2. But now when I am trying to access same mac-mini machine which is now connected to airport, I am getting following error:
Machine is having old ARD client/agent.
Even though, ARD 3.2 supports ARD 2.2.1, why am I getting this error? How to resolve this error?
Thanks,
Palav

Because Chicken of the VNC doesn't use the full ARD client, only the VNC portion. The error you reported:
Machine is having old ARD client/agent.
is exactly what I'd expect when accessing a 2.2 client from ARD 3.2. You will need to update the client version to 3.2, and that will require that the ports in the Airport base station be open and forwarded so that the ARD administration application can get full access to perform the client upgrade.

Remote Desktop repeatedly installs ARD Client for standard users...

ARD 3.2 running on OS 10.5.4 on MacBook Core2Duos...
These are machines imaged from an asr disk image...
No issues with admin users...
Every time Remote Desktop is launched by a standard user, a admin user name / password is required and the Apple Remote Desktop Clint is reinstalled. After, ARD runs normally until it is quit and relaunched, even without a user logout...
Making the standard user an admin user resolves the issue. The issue returns when the admin right are removed from the user...
Have run permission repairs, removed and reinstalled Remote Desktop, manually checked permissions, etc...
It appears that from the standard user perspective, the ARD Client software needs to be updated. ...
Any ideas out there? I have to deploy these machines NOW and I am running out of ideas on this...
Thank you! Les

Dave,
Thank you for the ideas. While you are pretty much correct in what you have said, these are unfortunately not my issue(s). I wish they were!
1) ARD will run fine for a standard user (at least it did in Tiger) as long as it is properly setup and licensed by an admin user ahead of time (especially the entry of the license code). This I have done, and the license code is recognized just fine. I too thought of the promote / demote idea and have tried it. While promoted, it launches fine for the user, but upon demotion goes back to reinstalling the ARD Agent at each launch of the program (this install process does not run while the user is promoted)...
2) The systems are from the same disk image. However, I have given system its own unique, valid, legally purchased serial number. Though the program is loaded on the image, it has been installed only. It is not run or licensed on the master, only on the end-user client machines...
It appears to me that from the standard user perspective, the system thinks that the ARD Agent needs to be updated. I have verified with the PackageMaker SnapShot utility that the ARD Agent and its related files are being installed when this happens, and they appear to be the only thing being installed. The Remote Desktop Admin program itself seems to be fine.
Does anybody know exactly what happens at the file system lever when Remote Desktop is launched? I am thinking my standard user is lacking access to a particular file or directory or right, and I am sure I could quickly find it if I new what to trace. Watching fs_usage has yielded lots of information, but nothing that has helped...
I have also removed and reinstalled Remote Desktop to no avail. Disabled all ACLs on the file system, placed known-good receipts and run permission repairs, and forced chmod -R 777 down the path of everything I can find with the names Remote Desktop, ARD, etc...
I am a little worried at this point that the issue is created by the imaging process something like the question marks in docks in the latter updates of 10.4. I have seen similar issues come up (launching apps under Rosetta being one) with users' LaunchServices property lists after moving their home directories from one volume to another, making the issue very hard to track down, as they reside in files that do not contain the name of the app being affected...
Any further ideas would be much appreciated!
Les

Issues with intel ARD clients

Blithely installing ARD from disk to update the client on a new intel I seem to have hit a snag.
The machine is no longer accepting observe or control requests. Can see what's happening in the scanner window, chat and get reports etc but no control or observe.
Tedious issue. Any ideas?

That may be your problem. The native ARD client for Intel (2.2.1, I believe) is, to the best of my knowledge, only availble on the install disks that come with the iMac and MacBook Pro. I think perhaps your installation overwrote the Intel-native ARD client with the PPC version, which is trying to run under Rosetta and failing to run correctly. I'd suggest reinstalling the ARD client from the iMac's install disks. I'm not sure if Pacifist, a utility to extract particular packages from the install disks, will work with the Intel Macs or not. If not, then you may have to reinstall Mac OS X.
Hope this helps.

Anyone tried the new ARD Client just released today (2-1-2012)

Has anyone tried installing and running the new ARD Client released today, Feb. 1, 2012? The info provided by Apple about this update seems to be kind of thin in exactly what was changed.3.5.2, It lists only screen sharing and controlling a computer with two displays. If you have installed it what have you found as both improved or degraded. What OS do you have installed on your client systems? Any changes specific to Lion or Snow Leopard?

Today I connected to a remote server running Mac OS X Server 10.6.8 and ran the updater for Apple Remote Desktop 3.5.2.
It successfully completed and I was able to re-connect. Unfortunately I can no longer "drag and drop". When I pick up an icon, for example, I cannot release it (drop). My controlling computer is running OS X 10.7.3.
I may try to revert to the earlier version of ARD if possible. This is a pretty big problem for me; so I'm trying to figure out what is wrong with this updater. It may be that a reboot will fix the problem; but I have to wait for a convenient time to reboot my server. I need to also test connecting from a 10.6.8 workstation instead of 10.7.3, as this may be a "Lion controlling Snow Leopard" issue.
Either way, I would be wary of this updater.

ARD 3.2 won't update 3.1 installation

I have ARD 3.1 on my desktop machine, used to administer three other machines. I just ran Software update, and it installed an update 3.2.1 ARD client. But now ARD (3.1) won't start, since it claims it has an incompatible client. And not only did Software Update not update the ARD admin software, when I downloaded the update it refuses to run because it claims it can't find the ARD admin application.
How do I get out of this Catch-22?

OK, that works. I re-installed from the 3.0 CD, and then ran the 3.2 upgrade, and now ARD will open again and allow me to talk to my clients.
But I still want to know why. This is about the fourth time over the years that an "upgrade" of ARD has required a from-scratch re-install. I know of no other piece of Apple software that does this, certainly not as regularly. Why can't they produce real "upgrade" packages for ARD?

Windows 8.1 clients are not detecting updates deployed to them through SCCM 2012 R2

Hello,
We are using SCCM 2012 R2 to deploy software updates.
On Windows 8.1 SCCM does not show certain updates as being needed and isn't deploying them to the clients even though Windows Update will show them as high importance. These same updates are being detected and deployed to Windows 8 clients successfully.
I believe that the update catalog that WSUS uses may have some incorrect detection rules for the following updates:
2917933
2913320
2913270
2913152
2909569
2904440
2904266
2903939
2899189
2893984
2893294
2892074
2916626
2898785
My automatic deployment rules include Windows 8.1 in the product category. I have even created a standalone rule for Windows 8.1 that builds a new package and the behavior is the same.
We only have a handful of Windows 8+ clients so this hasn't been a big issue but others may want to keep an eye out.

I am also running into this issue. After "checking online for updates" on one of my machines in office I found that there were 21 important updates for my 8.1 box. When I cross reference them in SCCM under All Software Updates, it appears these
8.1 updates are not listed. They are however listed for all other OS.
10 seconds after typing this, I went in to verify my WSUS -> Products and Classifications settings and come to find 8.1 and 2012 R2 weren't selected, even though it's an option in SCCM. Go figure! This wasn't the end though. After
running a Synchronization, my issue still wasn't resolved. Went back to check my settings and they again were changed back to having these OS unchecked. Finally, a solution! I found that in SCCM, under Administration tab, Site Configuration
> Sites > ABC - Mysitename, right click and scroll down to "Configure Site Components" > Software Update Point. This setting (although the same as is in WSUS) takes precedence, thus was rolling my settings back to the original configuration
in WSUS.
So long story short, even though my automatic deployment rules stated approve all windows 7/8/8.1 criticals/importants, 8.1 was getting skipped for the most part because my WSUS server wasn't syncing with Microsoft for all of the updates I required. I
did have a couple of updates that squeezed through because they were categorized as "Security Updates for Windows 8, 8.1".
Not sure if this is the solution you were looking for, but your thread got me started in the right direction, hopefully this response helps in the same way!
Thanks!

WSUS throwing 13002, "Client computers are installing updates with a higher than 25 percent failure rate. This is not normal."

Hello,
Within the past two months our WSUS Server started throwing error 13002, "Client computers are installing updates with a higher than 25 percent failure rate. This is not normal." We currently have 252 computers with errors in WSUS,
and 33 updates with errors. We have never had issues up until two months ago. If you keep rebooting the machine, and keep running updates, they eventually all install. I believe I will see the machines with errors go away as the weekly scheduled
WSUS install runs over and over, and the machines reboot.
- We run IE8 in our environment and sometimes IE9.
- We have 300 clients, all running Windows 7 SP1 x64.
- Our WSUS server is running on Server 2008 R2. The WSUS build number is 3.2.7600.262.
- We created an alternate WSUS 4.0 server on Server 2012, and redownloaded all updates. We put one client on it and it is showing errors on 3 updates, KB890830, KB931125, and KB2917500.
- Clients are throwing errors 800F0902, 80242016, and 80070005.
- I've noticed something with the C:\Windows\SoftwareDistribution\Download folder on the clients. When an update runs and fails, there is a "Install" folder created inside this folder. If you try to open it after the failure you get
"Access Denied" If you reboot the machine, the install folder goes away. (I assume this is a temp folder created to run updates). I've checked the permissions on this folder on various machines and all seems normal. I think
this is the root of the problem, and why we need to keep rebooting to get all of the updates to run.
- I tried deleting the Software Distribution folder on a client after stopping the update service, then restarting the update service. The folder redownloads but the client still throws errors.
- I've gone through our Group Policies looking for anything that can cause this and found nothing. We've created a test OU blocking inheritance, and only applying a WSUS policy in it to make it get the updates internally. I then rebuilt multiple
machines using Dell KACE, and still had failures.
- We run SEP 11 and 12 on our clients. I've tried removing the AV, making sure the firewall was off, etc. It still throws errors.
- I've spoken with our network team, and installed wireshark on a few clients looking for network errors and found nothing.
- I've tried various Dell KACE scripted installs on test machines (erasing and rebuilding the machines from scratch), after which I run Windows Updates from WSUS. They have thrown errors.
- I've rebuilt a machine using Dell KACE, undomained it, then ran updates externally from WSUS going to Microsoft's site, and I'm still getting errors.
- I've tried removing all software from the Dell KACE build to where it is just installing the OS and I'm still getting errors.
- I tried taking a plain Windows 7 x64 DVD and installing that on a test machine, then without domaining it and without installing any other software, running updates from Microsofts update site. This seems to work, althrough it does throw some errors
but I believe those are related to having to reboot your machine in order to complete the updates (I can't remember that error code at the moment).
Has anyone else been experiencing this? Any suggestions as to how I can fix this?

Hi,
Error 800f0902
Please try the method in this thread:
Error
Code: 800f0902
Error 80242016
If you receive Windows Update error 80242016 while checking for updates, it might be caused by a connection interruption between your computer and the Windows Update servers.
80070005
Usually means access denied
Since it worked perfectly for a while, did you make any change on the server? Any applications new installed on clients?

Please add the option to be able to upload/link new pdfs with the in-browser editing. I have a restaurant client who is constantly updating their menu! Please help so they can do this themselves!

Please add the option to be able to upload/link new pdfs with the in-browser editing. I have a restaurant client who is constantly updating their menu! Please help so they can do this themselves!

Thank you so much for your help! I am so relieved. I will have explain how to do this to my client, but a big weight is off my back!
A long learning process and actually such an easy fix. So glad you responded. Again thank you...

ARD Client Settings are not saving in System prefs. Any thoughts?

I am using ARD 2.2 from my Powerbook. It is running 10.4.3. Was able to create connections for observing with a G5 iMac running 10.4.5 , another PowerBook (which required an ARD client upgrade) running 10.3.9, and a G3 iBook running 10.3.9 with no issues. When trying to configure a Mac mini running 10.3.9, I am able to enter the System Prefs as the admin, set ARD to run using the admin account (in the exact same fashion as the other machines), turn on all available options and click the OK button. I can then go right back to the Sharing control panel where ARD is turned on but none of the other settings, including the checked account remain active. Has anyone else seen this condition? I tried reinstalling ARD client 2.2 and deleting the remote desktop prefs to no avail. If anyone has any suggestions they would be greatly appreciated.

You might try fixing file permissions (using Disk Utility) on the mini. It kind of sounds like a permissions problem.

ARD Client 3.2.2 update - HD at AirPort unaccessible

Similar Messages

Maybe you are looking for