Can't Mount SMB/CIFS Shares in OS X Sierra Public Beta 4

You went to the discussion forums ...Apple just moderates but no engineers or devs. bugreport.apple.com for real problems

Of course, Apple's forums are telling me to talk to the NAS vendor...

My suspicion at this point is that the removal of AFP in Sierra is conflicting with the ReadyNAS OS 4 setup that requires AFP to use Time Machine.  The ideal solution would be for an update to ReadyNAS OS4 that allows Time Machine to be run over SMB, allowing a user to disable AFP completely on their device without losing any functionality.

I realize that ReadyNAS 4 is EOL, but I strongly feel this would be a well received update from the ReadyNAS community, showing good will towards older users & hardware.

That aside - is anyone reporting this on newer devices with ReadyNAS OS 6, or is it just the OS 4 devices?  (i.e. - will moving to a newer device actually resolve this, or will the same issue keep happening?)

I'm with you in that an all SMB solution would be fine BUT SMB isn't working for me at all...you? Also, SMB performance has been pretty poor compared to Windows if you haven't tried. The Moderator in here knows some tricks that I believe could improve that. Hoping we get a fix soon so we can run backups as well as use the device. I had stated earlier that given the investment in this device (6 bays) it would be fair to at least make sure it functions even if EOL. Mine is not even 4 years old. 

Sadly, mine went out of warranty at the end of 2015, so I can't claim it's still supported.

SMB works fine for me, although it is noticeably slower than AFP for file access.

I am still looking for confirmation that this same issue is not happening on ReadyNAS OS 6 - it OS 4 is EOL, then it's EOL, but I don't want to pay for a new device if it won't fix the issue.

So you can use SMB with Sierra?? I guess I'm confused. 

Yes, I can use SMB, although it is slower than AFP was.

Because ReadyNAS OS 4 only uses AFP for Time Machine, and Sierrra dropped AFP, Sierra can no longer see my Time Machine disks, which is the main issue I am having.  I would disable AFP completely on my ReadyNAS, but I still need AFP for my other Macs that are not on Sierra yet.

If Time Machine can be configured to use SMB, there will no longer be a need for AFP to be enabled on the ReadyNAS device.  (Performance would still be an issue, though...)

---

GJSchaller wrote:

Of course, Apple's forums are telling me to talk to the NAS vendor...

 

---

Hardly surprising, but they really should have GUI options to enable backwards compatibility even if they are not recommended. I love using Apple products, but there's certainly some things they could do a lot better.

---

GJSchaller wrote:

 

My suspicion at this point is that the removal of AFP in Sierra is conflicting with the ReadyNAS OS 4 setup that requires AFP to use Time Machine.  The ideal solution would be for an update to ReadyNAS OS4 that allows Time Machine to be run over SMB, allowing a user to disable AFP completely on their device without losing any functionality.

---

I can still see AFP on my OS6 ReadyNAS and use it. Haven't tested Time Machine with OS6 yet, but I can still see my OS6 NAS when I look in the Time Machine preference pane.

It will be interesting to see what emerges about SMB and Time Machine in OSX.

---

GJSchaller wrote:


I realize that ReadyNAS 4 is EOL, but I strongly feel this would be a well received update from the ReadyNAS community, showing good will towards older users & hardware.

---

If Apple introduces a bug then they should fix their OS.

I don't have any control over what we do on firmware updates. I can pass on recommendations, but ultimately it is the product manager's decision.

---

GJSchaller wrote:

 

That aside - is anyone reporting this on newer devices with ReadyNAS OS 6, or is it just the OS 4 devices?  (i.e. - will moving to a newer device actually resolve this, or will the same issue keep happening?)

---

We are using recent versions of netatalk (AFP/Time Machine support) and samba (SMB) in OS6 and regularly update these. If there are issues and these get fixed one would expect them to be added to OS6.

I haven't had a chance to play with 4.2.30 and Sierra yet and I really need to get some sleep.

From reports I've read one possible solution to slow SMB performance would be to disable the SMB signing requirement of Sierra (this would require using the Terminal on your Mac, I believe. The setting change could be reversed easily enough if it doesn't help). I haven't read this in relation to RAIDiator-x86 specifically though.

I don't think this is a Bug, this is an intentional move by Apple to move away from an older protocol in macOS 10.12 - it's not something for them to "fix" since it was intentional, and not a bug.

Please pass on to the Product Manager that Apple has made an intentional change to their OS removing AFP, and that the ReadyNAS products need to be aware of this and possibly updated to allow Time Machine over other protocols.

Seems ReadyNAS is not the only one running into this:

https://forum.synology.com/enu/viewtopic.php?t=120107

Do we know what version of SMB ReadyNAS OS 4 is using?  What about the current ReadyNAS OS 6 devices?

So it seems SMB 3 works...does this version of Raidator suppor that? If that could be defatulted, turned on...seems I'd be back in business.

Of note, just in case:

http://kb.netgear.com/app/answers/detail/a_id/24923/~/readynas-os-6%3A-smb-plus-app?cid=wmt_netgear_organic

"ReadyNAS OS 6 supports SMB protocol 3.0 by default."

So there's that, for people that are out of warranty - a newer device should work without issue, it looks like, or at the very least has the proper protocols in place to be supported.

Hmmm... now I am being told AFP was *not* removed in macOS Sierra:

https://support.apple.com/kb/PH25269?locale=en_US

Apologies as I knew that. It wasn't removed. The only difference between you and I seems to be that you can browse via SMB and I can't. I can authenticate to both protoclos and see directories but never see any files. 

Yeah, the commenter on the Apple Discussion boards was talking out of his butt, so that was bad information.  Argh....

The consistent thing I am seeing is a problem with Authentication... AFP forces me to manually reconnect and authenticate each time I want to mount a share.  Time Machine never asks me for credentials, and just fails when trying to connect, presumably because it can't authenticate.  This does sound more like a bug, and less like intentional.

ovrdrvn - try removing all references to authentication to your NAS from your Keychain, see if that clears it up and lets you reconnect, at least by hand?

I have already connected to AFP shares on my OS6 NAS. I'm yet to try Time Machine but I can see the Time Machine disk. I'll give it a try today.

ReadyNAS OS 6.6.0 has the latest version of Netatalk (AFP/Time Machine service for Linux). We are using samba 4.4.x (SMB service for Linux) currently and will continue to evaluate the changes in new versions and decide when to update to newer versions of samba. OS6 is designed to make upgrading these packages as straightforward as possible. We keep these much more current in OS6 than many of our competitors.

Unfortunately Apple has a poor track record of breaking compatibility with older NASes with their software updates and not taking responsibility for fixing what they broke.

I will need to have a look at one of my 4.2.x systems at some point and try and see if there are any workarounds.

Just tested Time Machine backups with Sierra and ReadyNAS OS 6.5.0 (which we released some time ago now, the latest OS6 firmware is 6.5.2) and it's working fine for me.

Running a full (i.e. first) backup now.

I did some experimenting last night, with interersting results.  The plot thickens...

I did the following:

• Removed all references to my NAS from my Keychain
• Removed all mounts, and rebooted.
• Went into the NAS Admin Panel, disabled, and re-enabled AFP on all my shares.

Once I did this, the following things happened:

• SMB is not working - I am getting an error that the device could not be found.
• AFP works fine, once I authenticate for the first time.
• I am unable to connect to the Time Machine that is included with the NAS.  However, if I set up an individual home folder and configure it to be a Time Machine location, and authenticate using that, it works fine - as long as I authenticate using that specific user's credentials.
  • I had specifically done this in the past because I have 4 Macs in my home, and I didn't want one of them crowding out the others.  This way, each Mac has its own dedicated disk space for the Time Machine backup, and one won't compromise another's backup.

It looks to me as if the main issues are: 1) SMB, and 2) Authentication to multiple points on the same NAS using different credentials by Sierra.

Edit: This is how I set up a share as a Time Machine location for a specific user:

https://community.netgear.com/t5/Backing-up-to-your-ReadyNAS/How-to-Setup-multi-Mac-backup-shares-with-quotas-Easy/td-p/909845

---

GJSchaller wrote:

 

• SMB is not working - I am getting an error that the device could not be found.

---

Did you try both the IP address and the hostname?

Perhaps try disabling SMB signing on your Mac. SMB signing is now required by default by Sierra.

Didn't work for me but here's how to do it for anyone else wanting to try:

printf "[default]\nsigning_required=no\n" | sudo tee /etc/nsmb.conf >/dev/null

Any updates from Netgear on this? I have strange performance with AFP (testing more to see how useable it is or not) and CIFS/SMB I can't see any files...only directories. 

ovrdrvn please check what difference reverting the SMB setting change makes.

This disn't help at all. I still have no SMB access, no Time Machine abilty and some AFP access (peformance isn't great and one large volume seems inaccessible but I suspect it's a time out issue)