I lost access to my NAS share drive since EL Capitan

I have this issue too, It briefly went away and has returned with Sierra. Logging out gives me another one time connection. Extremely disruptive to work flow when using photoshop or maya since they can take time to get projects set backup.

The same problem here. I have a LaCie CloudBox and after upgrading my macbook pro to El Capitan I cannot connect to the NAS through Finder/Shared.

The NAS is shown in Finder/Shared, but its icon shown as '?' (question mark) and when I click on 'Connect As', I get this error message:

"There was a problem connecting to the server... The server may not exist or it is unavailable at this time. Check the server name or IP address, check your network connection, and then try again."

The only way to have temporary access to the NAS is by 'Connect to Server', which needs to be repeated every now and then.

There is no problem on my friend's macbook air which runs Yosemite and also I didn't have any problem before upgrading to El Capitan.

I've got what seems to be the exact same issue, I have a Seagate Personal Cloud and three Macs in my house. I updated all three of them to El Capitan and since then I've been unable to connect to the NAS through finder. However, you can use cifs to connect through Finder. To use this you open Finder and press "command + K" and then type in the IP address of your NAS. If you have a username or a password for the NAS you type this in and it should connect.

Hopefully a fix is released for this as I rely upon my NAS and if none the computers in my house will work with it then there's not much point.

I have the same problem with an iomega NAS. For both my MacBookPro and iMac. Only solution I found was to restart. This gives me a one-time only mount of the NAS. If I eject the partition I cannot get in again without a restart.

Same problem. Since installing El Capitan I lost connection to my 2 NAS servers - other devices (iPad and windows machines) can still connect. Also, Time Machine will not see the NAS where Time Machine backups are installed. Not being a techie, I am completely frustrated by this. Has Apple lost the plot launching such a poorly tested OSX?

I might have stumbled upon something.

I have an Ubuntu Server 14.04.3 LTS box acting as a Media/Torrent/Time Machine/File server. Basically it runs Netatalk for the AFP part and AVAHI to advertise the service over the network to my macs. I guess most of the NAS solutions use the same setup. After upgrading my MBP to El Capitan, I wasn't able to connect to my server by clicking its icon on Finder's shared section, but I could connect through Command+K with the url afp://username@servername. Also, my Time Machine backups were still being done hourly, so it got me to conclude this is not a NETATALK issue at first sight.

Long story short, I went through AVAHI's configuration files and this is what my afpd.service file looked like when I created it (the XX:XX part is my server's MAC address masked):

<?xml version="1.0" standalone='no'?><!--*-nxml-*-->

<!DOCTYPE service-group SYSTEM "avahi-service.dtd">

<service-group>

<name replace-wildcards="yes">%h</name>

<service>

<type>_afpovertcp._tcp</type>

<port>548</port>

</service>

<service>

<type>_device-info._tcp</type>

<port>0</port>

<txt-record>model=RackMac</txt-record>

<txt-record>sys=waMA=XX:XX:XX:XX:XX:XX,adVF=0×100</txt-record>

<txt-record>dk0=adVF=0×81,adVN=TimeMachine</txt-record>

</service>

</service-group>

After some trial and error, I got it to work adding the bolded line below to it:

<?xml version="1.0" standalone='no'?><!--*-nxml-*-->

<!DOCTYPE service-group SYSTEM "avahi-service.dtd">

<service-group>

<name replace-wildcards="yes">%h</name>

<service>

<type>_afpovertcp._tcp</type>

<port>548</port>

<txt-record>Username=MyUserName</txt-record>

</service>

<service>

<type>_device-info._tcp</type>

<port>0</port>

<txt-record>model=RackMac</txt-record>

<txt-record>sys=waMA=XX:XX:XX:XX:XX:XX,adVF=0×100</txt-record>

<txt-record>dk0=adVF=0×81,adVN=TimeMachine</txt-record>

</service>

</service-group>

At least for the time being, I'm now able to access my server's shared folders again by clicking it on Finder. I know this was a quick and dirty solution, and I'm not sure how it would work on a NAS being accessed by multiple users, but it might give some clue to others reading as to what the underlying problem may be.

Hope I have helped in some way. Good luck.

Thiago

As soon as I updated my mac to El Captain I lost the MyLacie NAS Cloud box access.

I rolled back to Yosemite and it now works again perfectly.

Will there be a fix any time soon?

Same problem here with my LaCie 2Big NAS. I hope this gets fixed asap!

I have the same problem, in house I have three Mac, 2 upgraded with new OS El Capitan and my iMac 2009 with Yosemite. With Yosemite I can see my NAS cloud box but witht the others mac isn't possible.

Send Apple feedback. They won't answer, but at least will know there is a problem. If enough people send feedback, it may get the problem solved sooner.

Feedback

Or you can use your Apple ID to register with this site and go the Apple BugReporter. Supposedly you will get an answer if you submit feedback.

Feedback via Apple Developer

From just a quick look at the Dlink website that nas is from 2013 right. Most likely you have to contact dlink and see if they have any updated software that is compatible with 10.11. The same goes with the other posts in this thread. Verify the website from your manufacturer to see if they have updated software for 10.11. You should always check if your apps - drives - accessories are compatible before upgrading to a new OS.

These are network drives though. As I stated in a previous reply, using command + K and connecting manually with the IP address works. It appears to be an issue with how El Capitan recognises the drive on the network. I've also tested this on a recently updated Windows 10 PC and it has no issue with recognising my NAS. It seems as though the protocol has been broken in El Capitan and is therefore a bug on Apple's part. There is no information from Apple directly stating that manufacturers should push a fix. I spoke to a Mac Tech at the Apple Store regarding this issue and he stated that it was most likely a bug from Apple and should be reported via feedback. He did not say that it was an issue with the manufacturer as they has not been told anything by Apple regarding this.

Yes I know they are network drives. Doesn't mean it will automatically work in a new OS. Always check before upgrading to a new OS or wait to upgrad. Did you try this. Got it from sea gate support page.

http://knowledge.seagate.com/articles/en_US/FAQ/005532en?language=en_US#Connecti ng%20to%20the%20drive%20with%20a%20Mac:

uarepeople wrote:

These are network drives though.

…that use a hack of Apple's AFP to communicate. Apple isn't going to make sure the netatalk hack is going to work. The manufacturers that use it have to make sure it works. If it used an actual AFP server or CIFS/SMB, then you'd have a point.

Apparently lots of El Capitans' users experience this issue, it's confirmed by WD: http://community.wd.com/t5/My-Cloud/OS-X-10-11-El-Capitan-Finder-Connection-Fail ure/td-p/909279

Here are some links to the other communities:

http://community.wd.com/t5/My-Cloud/Support-os-x-el-capitan/td-p/906456/page/9

http://forum.synology.com/enu/viewtopic.php?f=64&t=105411&p=397217#p397217

El Capitan Synology