Quote:
Originally Posted by dnanian
Maybe delete the Time Capsule entry in Keychain and see if you can get it to connect without typing the password? That password requirement is the problem...
|
Apologies for disappearing for a few days… still doing some testing to see if there are further issues. I was waiting to provided a final report, but that may be many days out yet.
Thanks for the password requirement being the problem clue! It was the root of the problem. Instead of deleting the entry, i selected it (double click or single click to select then the I for info button) in Keychain Access, selected the Access Control tab, then added SuperDuper! to the “Always allow access by these applications” list. Once this change was made and saved in Keychain Access, i had no further problems with the sparse image mounting in SD! for backup.
All of what i’m doing is actually pre-testing for setting this up for a client. With this problem solved, i decided to test on a different Mac which is almost the identical model the client is using (G4 AGP, Tiger). Setting up on that system, i had no problem with SD! accessing the sparse image on the Time Capsule, and i did not need to manually do anything in Keychain Access. Part of the reason may be that i was re-using the pre-existing sparse image already on the Time Capsule from my first test, though i believe the true difference is that with the first test, i didn’t understand when the OS was asking for the Time Capsule password what it really wanted, since the authentication dialog also listed an OS X account name, which Time Capsule does not use. I believe that in the original test, i entered a user account password or something else incorrect, which somehow somewhere got stuck in the OS’s remembered settings and was preventing connection until i overrode it in Access Control. On the second test i knew what to fill in where, so the correct Time Capsule password got entered the first time, thus no need to override. That’s my theory, anyway.
Thanks for your help… all taken care of. I may or may not have further findings (possibly questions) on this process, which i’ll post in this thread or a new one as appropriate (for the benefit of others if i have no new questions).