NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Periodic (daily) Time Machine failures
I am running TM on an iMac with 10.5.8 to a Duo running 4.1.6. However I am getting a failure about once a day where TM pops up a dialog saying the network volume could not be mounted because of a pro...
Hi,
after playing a lot with different ways of connecting Macs (and PCs) to ReadyNas-Shares i found that some of the problems that occured where caused by the Macs keychain.
Since i haven't encountered the error in question, i thought it might be helpful to post my keychain-entries (Snow Leopard).
The ReadyNas is used in a mixed environment so i chose to use CIFS and the ReadyNas IP-address to connect to the shares (like this: cifs://10.0.0.1/software).
This creates an entry in the 'Log-In' keychain with the name 10.0.0.1 and the following settings:
(yes, it says smb instead of cifs :wink: )
Using the Time Machine feature left me with another entry, this one in the 'System' keychain, being called A.local (A being the host-name to the IP-adress 10.0.0.1) with the following settings:
(AFP on this ReadyNas is only used for Time Machine, so it is not advertised over Bonjour or Appletalk and the AFP-permissions for each share are disabled, with no user- or groupentries. The box for 'extended AFP rights' (? - mine says 'erweiterte Einstellungen'...) is also unchecked.)
In case anyone is interested, i also stumbled upon a difference in Time Machine behaviour between Leopard and Snow Leopard:
I used to have one backup (and i mean really one backup = one date) created by a MacBook Pro under Leopard.
The name of the Sparsebundle was its device name followed by an underslash and the MAC-address of the ethernet-adapter used to connect to the ReadyNas.
When starting Time Machine (the program, not the backup) on the MBP the mounted volume had a similar name as the sparsebundle. I was able to backup to the same sparsebundle using that MBP, but this time with Snow Leopard.
Then i backed up a mac mini for the first time to the same ReadyNas but directly with Snow Leopard and the volume was mounted with the name 'Time Machine-Backups' and the created sparsebundle was named after the minis device name.
I therefore deleted the MBPs strangely named sparsebundle and did a complete new backup now also directly with Snow Leopard. This time the volume and sparsebundle were named in the like of the ones from the mini.
Maybe someone can find some of this useful...
- Johannes.
after playing a lot with different ways of connecting Macs (and PCs) to ReadyNas-Shares i found that some of the problems that occured where caused by the Macs keychain.
Since i haven't encountered the error in question, i thought it might be helpful to post my keychain-entries (Snow Leopard).
The ReadyNas is used in a mixed environment so i chose to use CIFS and the ReadyNas IP-address to connect to the shares (like this: cifs://10.0.0.1/software).
This creates an entry in the 'Log-In' keychain with the name 10.0.0.1 and the following settings:
(yes, it says smb instead of cifs :wink: )
Using the Time Machine feature left me with another entry, this one in the 'System' keychain, being called A.local (A being the host-name to the IP-adress 10.0.0.1) with the following settings:
(AFP on this ReadyNas is only used for Time Machine, so it is not advertised over Bonjour or Appletalk and the AFP-permissions for each share are disabled, with no user- or groupentries. The box for 'extended AFP rights' (? - mine says 'erweiterte Einstellungen'...) is also unchecked.)
In case anyone is interested, i also stumbled upon a difference in Time Machine behaviour between Leopard and Snow Leopard:
I used to have one backup (and i mean really one backup = one date) created by a MacBook Pro under Leopard.
The name of the Sparsebundle was its device name followed by an underslash and the MAC-address of the ethernet-adapter used to connect to the ReadyNas.
When starting Time Machine (the program, not the backup) on the MBP the mounted volume had a similar name as the sparsebundle. I was able to backup to the same sparsebundle using that MBP, but this time with Snow Leopard.
Then i backed up a mac mini for the first time to the same ReadyNas but directly with Snow Leopard and the volume was mounted with the name 'Time Machine-Backups' and the created sparsebundle was named after the minis device name.
I therefore deleted the MBPs strangely named sparsebundle and did a complete new backup now also directly with Snow Leopard. This time the volume and sparsebundle were named in the like of the ones from the mini.
Maybe someone can find some of this useful...
- Johannes.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
