Apple Event: May 7th at 7 am PT

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

After updating to Sierra, Mac won't connect to ReadyNAS device

I have two Macs at home - an iMac, and a MacBook Pro. I also have a ReadyNAS device, which acts as a Time Machine for both.


I updated the iMac to macOS Sierra. The upgrade went without issue, no errors reported. However, once it was back up, I found that the iMac had issues authenticating to the ReadyNAS using AFP (and / or it would authenticate, then drop the connection), and also could not connect to the Time Machine service on the ReadyNAS device.


To be sure it was not the ReadyNAS, I went to my MBP - it's still running OS X 10.11, and is not showing any issues. AFP shares are accessible without issue, and Time Machine works as expected.


Did anything change with the AFP or Time Machine protocols in macOS Sierra, that might cause this?


The ReadyNAS Device is a ReadyNAS Pro 4, running 4.2.28 firmware, if that helps.


Thank you for your help!

iMac, macOS Sierra (10.12)

Posted on Sep 21, 2016 4:16 PM

Reply
45 replies

Sep 24, 2016 11:40 AM in response to John Galt

Regrettably, this is correct. Although Netgear have promoted that their NAS devices are TM-compatible, there have been problems in the past. I use an old ReadyNAS Duo for TM at my parents' house. It works, and has worked, properly and reliably for years. But there was an issue, I think when Lion came out, when it didn't work for a while because Apple had changed AFP and we had to wait for Netgear to reverse-engineer a patch.


I would suggest that you make sure that you have a second drive available for TM, and allow the Mac to back up to both. Then if you have an issue with one, the other is available for recovery.

Sep 27, 2016 4:17 AM in response to Farrukh

I am experencing a similar issue with the mac os sierra photos app

i have a large (260gb) photos library on my synology ds415+ and the photos app


hangs trying to read it and seems to corrupt other finder sessions after that

im assumi g the photos app utilizes afp

t have opened a case with apple (100030957832) and submitted an issue to synology

no response from either thus far

i have both smb and apf enabled on the nas

i was mou ting/connecting with afp

Sep 28, 2016 9:55 AM in response to Geoffrey Schaller

Sierra has made some changes, some of these may be to do with authentication or AFP or Time Machine or something else. This is almost always the case when Apple release a new version of the operating system.


Apple has not yet discontinued AFP but they have previously give a clear indication they intend to. Their previous comment on this subject went along the lines although these are not their exact words that -


  • Everyone can use SMB,
  • SMB is therefore the universal standard for all operating systems, not just Mac
  • All servers - including real servers support SMB but most servers i.e. real servers do not support AFP
  • SMB is faster than AFP (true)
  • As only Mac users use AFP the amount of effort Apple has to put in to developing and maintaining AFP just for the benefit of a relatively small number of Mac users is increasingly hard to justify. This is on top of the effort Apple has to make writing their own SMB implementation as Apple no longer uses SAMBA
  • Ergo we - Apple will phase out AFP in favour of SMB


So for the last few versions of OS X it has already been the case that the Finder will try and use SMB instead of AFP if possible, this remains the case with Sierra.


What has changed is that for the very first time Server.app 5.2 on Sierra can share a volume for use as a network Time Machine destination via SMB! This is something I suggested to Apple myself a couple of years ago after their above comments about AFP, clearly if Apple intend to stop providing AFP at some point they need to change Time Machine to match.


Now that Apple have updated their Server.app Time Machine to support SMB, one can expect either Time Capsule to be similarly updated or replaced or discontinued. Once this is done it maybe that the next macOS upgrade will remove all AFP support, or at least make it invisible and inaccessible to normal users like NFS.


At this point in time I am not aware of it being possible to use any third-party SMB file servers for Time Machine backups. I would expect the SAMBA team to add this feature over the next few months.


Note: Nearly all NAS servers use SAMBA for SMB sharing, and another open-source project called Netatalk for AFP sharing, this includes Synology and Netgear/ReadyNAS.


Note: Apple do not officially support third-party NAS devices. Well duh! Apple don't make them so why should they? This does not mean such devices cannot work. I also use a ReadyNAS as a Time Machine system. I don't expect Apple to help me out if I have a problem with it.


If or more accurately when Apple release a new version of their operating system and it (again) breaks things then the usual pattern is to wait for the relevant open-source project team i.e. Netatalk for AFP to work out what changed and for them to update their software to match. Then there is a further wait for the NAS maker to take the new version of Netatalk and to add it to their own software. Historically Netgear i.e. ReadyNAS were very good at this because they were a top tier contributor themselves to the Netatalk project. I am sadly not as convinced of their speed anymore especially with regards to the now very old 4.x firmware models, current models use 6.x firmware.


For those having AFP problems with NAS devices you need to differentiate between whether it is a complete AFP failure or just a Time Machine failure. You should also double-check your NAS firmware is up-to-date and I can confirm that 4.2.28 is the current version of firmware for that (old) generation of NAS.


Now saying all the above, it remains a potential possibility that this is not actually a deliberate change by Apple but an accidental bug. So, there would be no harm reporting it as such. Apple may respond with their infamous 'works as designed' answer in which case we wait for the Netatalk team to fix it their end.


PS. Both the SAMBA team and the Netatalk teams have added Spotlight support to their software. Sadly many NAS makers have yet to make these features accessible on their NAS boxes. It would be possible to do this on a DIY Linux server.

Sep 28, 2016 2:44 PM in response to Geoffrey Schaller

What worked for me was to map to there NAS share using the slow NFP protocol. Passing the NAS credentials worked without an issue. Then, I was able to connect TM to the share, and now I'm running my first backup (Across WiFi, yes... I have other things to do than to bug test Apple's Sierra OS). But so far its running, and backing up.


A sniff of the traffic shows me a small 64k packet per session (now I don't mind the SMB 164K per packet). Seriously, though, Apple needs to stop rolling back functionality. I may rollback to El Capitan if I discover another missing feature. That will fix them... join me in saying...


No, SMBv3, no Sierra download, No SMBv3, no Sierra OS X download. C'mon people, chant with me!!!

Sep 29, 2016 8:13 AM in response to dwmreg64

I upgraded all of my in MACs at home to Sierra and authentication between them using SMB or AFS file sharing just stopped working. Even with clearing everything out of keychain required me to click the "Connect As" button every time. After seeing the posts now, I should have waited to upgrade. It does not look like the QA team tested the networking features throughly....very frustrating.

Oct 2, 2016 2:53 AM in response to mindphunk

Hi Everybody !
I update my iMac to Sierra just yesterday and I immediately noticed the issue on the connection to shares: it keeps me prompt the Username&Password pop-up window without connecting automatically even if user, pwd and the "save password" flag are filled in, so I have to click on "Connect" and then it works.


This happens both on my QNAP NAS shares via afp:// and on my windows Pc shares via smb://

Luckily (but strange) backup with Time Machine on the QNAP are not affected by this issue.


I tried to delete and create again the password on the keychain but this didn't fix.

Hope next update will fix this because it's very annoying.

Nov 18, 2016 11:49 AM in response to Geoffrey Schaller

I bought a MacBook Pro this week and Sierra was preinstalled. I immediately noticed the same problem with my Synology NAS. When clicking on the NAS in the Finder sidebar, it does not connect and show the shares, I first have to click on "connect as..." and confirm with the "connect" button (the credentials are saved in keychain and filled in).


I also noticed that there is a timeout for connections. If I stay on the NAS item in Finder some time (1-2 mins) before clicking "Connect as...", nothing happens. I then have to click on another item in the Finder sidebar and go back to the NAS.


OSX is preferring SMB over AFP for connections made in the UI by clicking network devices, so I can rule out that this is a problem with AFP. I also see that a CIFS (SMB) connection is active after a successful connection when looking in the "connected users" pane in the Synology resource manager in DSM.

Nov 20, 2016 4:35 PM in response to fcrombez

I have having problems mounting NFS volumes from my ReadyNAS Ultra 6 since upgrading to Sierra. Though I was not (consciously) using AFP, disabling it on the ReadyNAS box resolved the problems and now the NFS mounts are working again. I am thinking that whatever changes Apple is making in OS X on the path to discontinuing support for AFP or adding SMB support for Time Machine is having unintended side-effects.


Thanks for your tip. I would not have thought to try this were it not for your contribution.

After updating to Sierra, Mac won't connect to ReadyNAS device

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.