I lost access to my NAS share drive since EL Capitan

Install Fing app on your iPhone. It will show all IP addresses on your local network when the iPhone is connected. If you do not have an iPhone, I think it is also available for Android.

This is still an issue as of yesterday (12/16/15) with my rMBP running 10.11.2 and my Synology DS213. After attempting multiple fixes (WINS settings, SMB and AFP settings, network settings, etc...) from several posts both on here and the Synology pages, my fix was simply resetting my Airport Extreme.

The second it reset the NAS showed back up in my finder. Hopefully this will help someone else that's still in the same situation 🙂 I feel slightly dumb for not doing a router reset at first haha...live and learn I guess. Apple seriously needs to address this issue since the problem is so wide-spread.

Hi, i dont want to reset the router. i dont even remember what settings i have created in the router. I have100s of things configured and its going to painful if i reset the router.

Is there any other way to detect the nas other than "writing a simple piece of code in TERMINAL" (which is "killall Finder")

Sorry I should have used better terminology. If you just power cycle your router you wont lose any settings and it should have the same effect, at least it did in my instance.

thanks mate!

I did powercycle but my problem still stays the same. Finder detects nas drive as a local drive but after macbook goes to sleep it just doesnot let me get into the nas drive until i run a command in TERMINAL and kill finder windows. It starts connecting as a local drive once that command is performed.

this doesnot happen in my imac and mac mini.

In airport utility I assigned a static IP address to my NAS then remotely rebooted the router.

After rebooting the computer Finder connected to the NAS instantly. I cannot say if static address or simple router reboot solved the problem. The bottom line is it has been solved.

the same problem here 😟 temporary solution is restart the Finder process but I hope for some fix soon

I have just bought a Seagate Personal Cloud and can't connect on my Mac running El Captain. I have managed to access the drive through connect to server but it runs so slowly, it's unusable. I can't even stream videos, the lag is that bad! Am I doing something wrong or is it normal for slow speeds using this method?

Which IP address do you use?

http://knowledge.lacie.com/articles/en_US/FAQ/007619en

Rebooting worked for me as well. The problem arose when my macbook pro was already running and my NAS was offline. I couldn't reestablish a connection. Rebooting fixed it. Why it can connect on boot, but not reconnect is a mystery.

Would this be the reason my Time Machine Back Up keeps asking me to start a new backup because it couldn't verify the back up spares bundle?

I have had issue due to Time Machine not finding my LaCie CloudBox. Interestingly enough even when I use the LaCie Network Assistant to auto mount volumes from the drive Time Machine still can verify backups.

I have tried creating a new backup by selecting the mounted volume. Interestingly I had two option for volumes of the same drive.

aft://LaCie-CloudBox.Local/{volume name} & aft://lacie-cloudbox.Local/{volume name}.

Notice the difference in case. Since the Network Assistant was mounting my volume from the lower case name I have tried rebuilding a time machine back up on that. I will see if once it has backup and the volumes are still mounted if Time Machine will work with it.

It's almost as if connecting to the same volume but via different paths is causing the confusion for 10.11.

Time Machine will continue to backup as long as the drives are mounted manually.

I've just managed to fix this my turning off SMB/Windows sharing on our NAS (Synology) and leaving only AFP enabled - Not a workaround for mixed environments but if you're a 100% Apple shop hopefully this will get you back up and running!