Well, I've just spent several days trying to sort a NAS problem which only seems to affect my iMac (El Capitan, highspec). I can do what I want to on Windows 10 (via Bootcamp).
A few days ago, my 3TB WDMyCloud NAS (luckily I don't use it for my FLAC files), decided to refuse to let me write/delete anything on it, giving a variety of error codes - usually "error code -36", although I have seen others as well. Went on t'interweb looking for a solution, and tried the various suggestions, eventually ending up with a full factory reset - which took >24 hours! Of course, that means I have to write >1TB of data back to the NAS now (sigh).
Then had a bit of a kerfuffle before I eventually managed to persuade my Mac to mount the disc. Went back to my BTHomehub 5 settings and checked that I still had a fixed IP address for the NAS.
Thought all was cured, and managed to add a couple of directories to the NAS in readiness to rewrite my data to it. It let me enter 2 Directories (albeit it seemed slow and unresponsive), then up popped error -36 again.
Rebooted in Windows 10, and I can write/delete to the NAS OK on that platform.
I can't think of anything else to do. Any suggestions?
In the meantime, I am relying on the other backups kept on my 6TB Thunderbolt external hard drive, and various other external hard drives.
Posted on: 28 June 2016 by Adam Zielinski
What NAS are you using? I typically mange my NAS through its dedicated soft (from a Safari window) rather than from my MacBook.
Adding new albums is not a problem via a Finder. But anything more complex - I simply use NAS's operating software.
Posted on: 28 June 2016 by Mike1960
Hi Dungassin, is this a file service issue? I use a Synology NAS with my Mac. Your Windows machine is almost certainly accessing your WD NAS with Windows file service. The native file service for Mac is afp. On my Synology under "File Service" I have both enabled.
From Finder in your Mac, select -> Go -> Connect to Server -> afp://xxxxx.local where "xxxxx" is the name of your NAS or you can type it's IP address after afp:// and leave off the ".local" at the end e.g. afp://192.168.0.5 if you know the IP address. This should then ask for your name and password so that you can mount the volume you wish to access. If this is not working then I suspect you have not got afp working. Hope this helps.
Mike
Posted on: 28 June 2016 by Dungassin
What NAS are you using? I typically mange my NAS through its dedicated soft (from a Safari window) rather than from my MacBook.
Adding new albums is not a problem via a Finder. But anything more complex - I simply use NAS's operating software.
The NAS playing up is a WDMyCloud. As I said, I can read/write to it via Windoze, but not via MacOS! So, it's a problem with the Mac.
Posted on: 28 June 2016 by Dungassin
Hi Dungassin, is this a file service issue? I use a Synology NAS with my Mac. Your Windows machine is almost certainly accessing your WD NAS with Windows file service. The native file service for Mac is afp. On my Synology under "File Service" I have both enabled.
From Finder in your Mac, select -> Go -> Connect to Server -> afp://xxxxx.local where "xxxxx" is the name of your NAS or you can type it's IP address after afp:// and leave off the ".local" at the end e.g. afp://192.168.0.5 if you know the IP address. This should then ask for your name and password so that you can mount the volume you wish to access. If this is not working then I suspect you have not got afp working. Hope this helps.
Mike
Thanks, Mike. I'll give that a go later on today (SWMBO is hassling me to repair a couple of her things first). I had some difficulty accessing the WD NAS after the factory reset, but eventually got back in via Finder>GO. It's currently logged in as a smb device. Prior to developing the problems leading to the factory reset, that's the way it was logged into from the Mac (i.e.smb). I had great fun trying to connect even via Finder>GO, until I deleted the username being entered automatically by the Mac (johnmartin) from the login box and just substituted (john). Then logged in without a password (as admin - well, sole user - I can do this on the WD NAS)
Never had this problem with my QNAP NAS.
Posted on: 28 June 2016 by Dungassin
Well, I tried to mount the drive using afp. Didn't work. According to t'interweb, Macs should work perfectly well with smb.
I'm totally fed up with the thing, and as it's really only a NAS backup for ease of access to photos for SWMBO, I think I'll give it to my son-in-law (after all, it works OK with Windows 10), and just keep the backups on my 6TB Thunderbolt drive and external hard drives. SWMBO can just use an external drive if she really wants to look at old photos. First, though, I must try saving/erasing files on the WD NAS using SWMBO's MacBook Pro, just to see if it's just my iMac. That'll have to wait till tomorrow, as she is using it this evening.
What bugs me is that there have been no recent updates to El Capitan or the WD NAS firmware/software to explain the problem.
Posted on: 28 June 2016 by Adam Zielinski
You should not be using AFP at all! It should work with SMB.
What I don't get how Mac is causing problems. You don't need it for streaming - you should be streaming from your NAS, directly into your NDS.
Mac should be just for admin duties of your network.
Posted on: 28 June 2016 by Adam Zielinski
What NAS are you using? I typically mange my NAS through its dedicated soft (from a Safari window) rather than from my MacBook.
Adding new albums is not a problem via a Finder. But anything more complex - I simply use NAS's operating software.
The NAS playing up is a WDMyCloud. As I said, I can read/write to it via Windoze, but not via MacOS! So, it's a problem with the Mac.
No - it's not. If you are running SMB on your NAS you should be able to read and write into your NAS from a Finder window.
One thing - you need to define user rights from your NAS, so that your Mac can actually access it to make changes to the content.
Posted on: 28 June 2016 by Dungassin
What NAS are you using? I typically mange my NAS through its dedicated soft (from a Safari window) rather than from my MacBook.
Adding new albums is not a problem via a Finder. But anything more complex - I simply use NAS's operating software.
The NAS playing up is a WDMyCloud. As I said, I can read/write to it via Windoze, but not via MacOS! So, it's a problem with the Mac.
No - it's not. If you are running SMB on your NAS you should be able to read and write into your NAS from a Finder window.
One thing - you need to define user rights from your NAS, so that your Mac can actually access it to make changes to the content.
As I've said already, I can access and use the drive with no problems from Windows 10 (Bootcamp). Until a few days ago I had no problems using it from my iMac either. I will say, however, that access to any Directory on the NAS using the Mac always seemed to take up to a couple of minutes before the window populated with its contents. The same slow access has always happened with the 3TB of FLAC files on my QNAP NAS. Access to files on the QNAP (and the WD NAS before it started playing silly b*ggers) using Windows 10 (bootcamp) is instant.
No new software etc installed to explain the problem.
I can mount the Server using Finder>GO (I have now introduced a password, just in case that was the problem - it wasn't).
I can get to the WD Server's webpage by typing its IP address into Safari, and can set up New Shares (which still won't let me read/write to them using a Finder Window). I have checked the permissions on this NAS webpage, and all the Shares are Public Access.
If I try running the WDMyCloud software downloaded from their website, its says it can't find the NAS - and that is whether or not I mount it first using Finder>GO
I say again - it just stopped working, and after trying all the usual bits about deleting trash files (there weren't any, BTW), I did a full Factory Reset of the NAS. That should have returned it to the state in which I first bought it, less than a year ago.
So ... why isn't it working with my Mac anymore? 
Posted on: 28 June 2016 by Dungassin
Yeah, that's what I always used to do as well. However, it don't work anymore. Incidentally after my last post, I remembered how to cure the "Slow Finder" problem. Basically you just have to delete a couple of corrupt files from CloudKit.
Before you ask - that hasn't cured the original problem either!
Posted on: 01 July 2016 by Dungassin
Well, I finally managed to get hold of SWMBO's MacBook when she was not busy 'networking'. It was a 2am last night after she'd gone to bed (I'm a bit of an insomniac)
Result? I can access and read/write to the offending WD NAS with no problem from her Macbook, so AFAICS the problem must lie with my iMac. I have no problem with my other (QNAP) NAS.
Looks like the WD NAS will be moving on to a new owner. Bloody annoying, as it means I'll have to keep a laptop external drive with photos/videos available for when SWMBO wants to look at old photos.
