I lost access to my NAS share drive since EL Capitan

I am running a Synology DS414J NAS with the latest drivers and I have the same issue. I can manually connect to the device and drives, but I'm unable to connect though the finder. My auto connect works at login when I drag the drives to the window, but I can't add them via finder either.

Was having the same problem with a LaCie 2Big NAS. Disabled the SMB sharing and it worked. Apple-only environment. Thanks !!

How was this issue noticed upon release in October and still not have a solution? I just updated to El Capitan on my MBP and now I cannot connect to my NAS, even when I try to manually. Luckily my iMac is connected via Ethernet and still connects without issue, but i still need a solution to access my NAS on my MBP.

I too have the same issue with my Seagate Personal cloud. Has there been any resolution since?

Thanks,

this is a $500 tip. I was looking for this like a month and i was almost buying a new storage with out a NAS.

I've read many posts, talk to the people on Dlink and no one thought about that!

There are no problems with the Dlink and the El Capitan, just a config miss understud!

Thanks for it!

The solution is:

hitchysan

I had this same issue and just solved it. I have a Mac Mini and access my DLink StorCenter over the Ethernet connection, which is a separate connection from what I use for the Internet and everything else (I use WiFi for that). When I upgraded to El Capitan I lost connection with my NAS, clicking the drive in Finder would eventually time out but the device was online (I could access from other devices connected to my Ethernet network as normal).

When I checked the Network properties, for some crazy reason the Subnet value for the Ethernet Connection had been changed to 255.255.255.255 rather than 255.255.255.0 which is correct for the network I have.

I updated the Connection properties to manually specify my IP address, Subnet and Gateway and everything started working as normal.

I wonder if there is an issue with the El Capitan upgrade that messes with the network? While this probably isn't the same issue for everyone there is a good chance it is the issue for some of you.

Worth diligently checking your network settings for the connection that you would access your NAS from.

Thanks

Anyone know if the latest 10.11.4 fixes this issue? I've tried what @hitchysan suggested but that didn't resolve the issue for me. I'm using the same gigabit ethernet connection for both LAN and WAN access. My NAS is a Qnap device on a NetGear GS748T managed switch with a NeGear UTM50 firewall. The users MacMini with the issue is only able to reconnect to the NAS when rebooting their system.

I've installed 10.11.4 and will test it out for a couple days to see if Apple in fact has fixed the issue. Will report back my findings. Thanks!

Hello,

I have the same problem on 10.11.4 - lost my connections to NAS(QNAP).

Now when I tried to connect manually, I can just use SMB and even when I connect I coudn't access folders.

Anyone know how to fix this?

Thanks!

I had problems connecting to my Seagate Personal Cloud...I could connect via AFP but the NAS was not recognised either by Time Machine or by Seagate Dashboard (the software you need to manage backups etc)

The solution was in the network settings on the NAS for IPv6 which were disabled. I enabled them and hey presto everything worked. Worth trying

I have the same problem trying to connect from my iPad to my Mac Pro over WiFi since the upgrade to 10.11.4

Hey There,

i have the same Problems with my MBP2009 since upgrade to El Capitan and the Problems with my new MBP Retina.😮😐😠😟

If I Restart my NAS, I have access for some hours. If the MBP wake up from sleep mode, they lost access to the nas

have the same problem just started today connecting to centos 7 share samba version 4.2.10. What I found was mac will not connect using guest account But if I add secure share user and password it works fine and then the guest starts working Old sever running samba 4.2.3 works fine

I fount the solution on my System. It seems the problem is that El Capitan doesn't mount the drive initially via AFP, but through a newer process. If I mount the drive from Finder's "Connect to Server..." menu as such (After unmounting the original attempt.):

afp://server.local/Time Machine

Then it becomes visible in the Time Machine preferences and initializes properly.

Actually, Previously I was unable to correct this with Finder Relaunch, but just tried it again and works for me. Much less disruptive.

Is this issue resolved with Sierra?