All,
After installing the latest El Capitan Update (10.11.3) my iMac now has broken its AFP connections to my two QNAP NAS's. All software is up to date on both NAS's also (4.2.0).
The iMac looks for the directories but seems to hang trying to get the directory and file info. (Spinning colour wheel)
I would Time Machine back to before the upgrade, but my Time Machine backups are stored on the QNAP, which it can't access.
You are not using a supported Time Machine configuration. To learn how to use Time Machine read Use Time Machine to back up or restore your Mac.
Despite their manufacturers' insistence to the contrary, there are no non-Apple NAS devices that will reliably work with Time Machine. If you want to use your QNAP NAS device to back up your Mac's contents, then use a backup strategy other than Time Machine.
The exhaustive list of devices supported by Time Machine amounts to the following:
That is all.
Use whatever backup device you want, but you should be aware that this site is full of reports of misery from hapless individuals who had been using third party NAS devices for Time Machine backups, only to find that they were incomplete, corrupted, or useless in the dire circumstances in which they were required. Apple won't care if you lose your data while using a Time Machine configuration specifically excluded from their technical support documents.
Umm No this is not the crux of the problem. Time machine has ALWAYS worked fine on this device.
The problem now is that the latest El Capitan update has broken Network drive connections. If the connection wasn't broken by the software update then Time Machine would work just fine as it always has. It has broken connectivity through iTunes, through Lightroom, any ap that needs to access the network shares.
The iMac won't connect via AFP it won't connect via SMB. All started since I updated to the latest El Capitan.
If the connectivity was working I wouldn't need to use Time Machine.
I do not believe you comprehend what I wrote, but I don't know how to explain it any better than that. Good luck.
Well if the software update didn't break Network Drive Connectivity then there would be no need for Time Machine. Pretty simple really....
No broken buggy update, No need for Time Machine.
Thats a simple as it gets.
And it would be nice to have to fixed......I need access to my 64000 photos stored on the NAS.
Same problem here, all of a sudden after "upgrading" to 10.11.3, the time capsule I had setup attached to my asus (merlin) router suddenly started failing, with apple now claiming a "corruption" and need to reinitialize after every back up. This was working flawlessly for months before this. I finally gave up and now have that disk attached locally for regular time machine backups, but what a pain in the ***.
I have the same or at least a similar problem since upgrading to 10.11.3.
After the upgrade I could no longer connect to my Synology in Finder using afp. I can, however, still backup using time machine, which is on the same NAS.
The responses to this problem that I've seen on here have been pretty bad and frankly quite rude.
I managed to get the folders that I was trying to access to show up by going to Finder > Preferences > General and then checking the box to show the folders on my desktop. I hope this helps in some way!
This shows that the problem is in the OSX upgrade as it manages to connect when not going through Finder and I can manage my files this way, I just can't mount the drive properly from within Finder.
In response to John Galt, I have used my Synology as a TM backup for years with no issue, I will use whatever device I like to backup with and I expect the services that I pay Apple a premium for to continue to work. Connecting to an external device is not unsupported functionality.
akaxlm wrote:
... I have used my Synology as a TM backup for years with no issue, ...
Until now.
The fact that Apple's proprietary Time Machine software requires the Time Machine-compliant hardware specified in their published documentation has been beyond dispute for at least as long as those continuing to insist otherwise, and the subject has been beaten to death on this site for over eight years.
... I will use whatever device I like to backup with and I expect the services that I pay Apple a premium for to continue to work.
Tell Apple. I'm sure they will give your stubborn expectations all due consideration. It's your time to waste, and your data to lose.
Hello akaxlm,
Yes it sounds like you have the same problem as me. Any sort of AFP protocol access to a NAS has been broken. I have found a workaround like you, I mount SMB shares at boot which has gotten around the problem, although it is not perfect as the implementation of SMB is a little buggy when dealing with mount points.
Time Machine is working as normal to the NAS (which is strange as it uses AFP) and backing up.
Don't worry about the bad replies, sometimes the Apple Fans don't understand there is a world outside of the Apple ecosphere.
You are still missing the point. I CAN still use the NAS as my time machine backup. That works fine.
I can't connect to the shared folders on the NAS in the same way anymore. It just always fails to authenticate, but works when I connect in another way.
Please try and properly read the problems before attempting to help. It's like you're just desperate to have an argument about something we aren't talking about. Apple supports OSX connecting to external devices via AFP, that is no longer working correctly when connecting via Finder. That is the problem. Nothing to do with Time Machine (which still can connect).
Hi @akaxlm
im having this exact same problem on a QNAP 12 Bay NAS running QTS 4.2
i started seeing this behavior after updating to QTS 4.2 from qts 4.1.3 (4.1.3 - No Probs)
looking through the documentation for QTS 4.1.x and 4.2, the version of AFP used by QNAP has changed, when i say AFP, what i really mean is Netatalk, Netatalk is what QNAP use for AFP connections. (open source version of Apple Filing Protocol - I dont know why they use it, possibly to do with Apple Licensing.)
see here - http://netatalk.sourceforge.net/
now i know that after 10.9.x , the way OS X handled AFP (netatalk) connections changed, this was around the same time as Apple changed the default file sharing protocol in OS X from AFP to SMB/CIFS.
historically other problems i have seen with QNAP and AFP connections have been to do with QNAP's implementation of Netatalk in there QTS software
QNAP usually take a couple of .point releases of qts to update the version of netatalk they are using to be more compatible with the current Verson of OS X
i also wonder how much of this has to do with the SMB 3.0 implementation that QNAP uses.
im still investigating this and looking for a fix. if i find one ill let you know..
HTH
Natas
QNAP QTS 4.2.1 is using Netatalk 3.0.8
current Release version of Netatalk is 3.1.8
looks like QNAP is a few Versions behind.
it is possible to SSH into the Qnap and update the Version manually via Busybox's package manager, i think its apt-get.?
HTH
Natas
natasp wrote:
QNAP usually take a couple of .point releases of qts to update the version of netatalk they are using to be more compatible with the current Version of OS X
i also wonder how much of this has to do with the SMB 3.0 implementation that QNAP uses.
im still investigating this and looking for a fix. if i find one ill let you know..
QNAP are slower at updating their NetAtalk compared to NetGear/ReadyNAS although NetGear have their own foibles. On a separate topic I am frustrated by QNAP not making any progress on implementing BTRFS support, something both NetGear and Synology have already done in some form or the other.
This AFP issue should have absolutely nothing to do with SMB, in fact using SMB instead of AFP to connect to your QNAP might be a workaround.
I have the same problem with my WD My Cloud storage device. I cannot connect to it via "Connect to Server..." (or equivalent) via AFP. It still connects fine via AFP on systems I have running 10.9 and 10.10.
I have tried connecting to it using SMB via "Connect to Server...", as well, with no success.
Well, I continued to research the problem this evening and I fixed the problem on my 10.11.4 system. I deleted the arp cache by starting the Terminal app and using the following command:
sudo arp -a -d
I then restarted my MacBook and had no problem connecting to my WD My Cloud using "Connect to Server..."...
I think it is entirely possible that El Capitan has a problem with arp cache management.
El Capitan 10.11.3 has broken AFP connections to my QNAP NAS
