You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

elaverdiere Author

Level 1

6 points

I lost access to my NAS share drive since EL Capitan

Hello all,

Since the migration to EL Capitan on my MacBook Pro, I lost the direct access to my NAS Drive under Finder/Shared. My NAS is a Dlink DNS 320 and it is using a standard NETATALK plugin. I have another mac mini with the old Yosemite OS and it is still being able to see my NAS.

When trying to access my DNS320 under my EL Capitan system, because the link is still there under Finder/Shared!, I get two pop-up messages :

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

and

"There was a problem connecting to the server "dns325". Check the server name or IP address, and then try again. If you continue to have problems, contact your system administrator".

I was able to mount some folders by "connecting to server" function under Finder->Go, and using the URL "afp://dns325._afpovertcp._tcp.local". But it doesn't explain to me why the Finder doesn't see anymore, automatically, my NAS.

It seems to be a bug brought by EL Capitan.

Etienne

MacBook Pro with Retina display, OS X El Capitan (10.11)

Posted on Oct 2, 2015 7:42 AM

90 replies

Aizzz

Level 1

0 points

Oct 13, 2015 4:42 AM in response to elaverdiere

Shortly after OS X El Captain version 10.11 was installed on my iMac 2,5 GHz Intel Core i5 it started giving messages.

The disk is a LaCie d2 Quadra V2 1TB, it's connected to the iMac with a Firewire 800 cable.

I checked if the LaCie was still readable on my old G4 with a Firewire 400 cable.

It was, ran a disk utility check, apparently nothing was wrong with it.

The LaCie still doesn't get recognised, although this didn't happen immediately after installing El Captain.

The Question is what to do now.

Oct 13, 2015 5:26 AM in response to Barney-15E

My drive uses AFP, CIFS and SMB. I can connect using CIFS through Finder. I suppose the other problem that has been highlighted is that various manufacturers drives aren't working. People with LaCie drives are reporting problems too and as Apple sell a huge range of their products it seems unusual that they wouldn't still support OS X, I'm not stating that as any kind of fact though, just an observation. Also as I stated before, I spoke to a Mac Tech at the Apple store who stated that it was a bug with El Capitan, he didn't suggest that it was the manufacturer.

Oct 13, 2015 5:28 AM in response to Community User

That's great, I'll try it out when I get home and report back if it worked.

pibby_

Level 1

0 points

Oct 13, 2015 8:15 AM in response to elaverdiere

Same issue. I'm able to connect if I kill the Finder process. Open Terminal and type:

killall Finder

Besides that, only a restart will allow me to connect again, the above it much faster.

lucabrj

Level 1

0 points

Oct 15, 2015 12:56 PM in response to ThiagoA.S.

You made my day!

I had the same problem with my file server on Ubuntu, I solved adding that line.

Thanks for sharing!

Oct 15, 2015 5:49 PM in response to lucabrj

Nice!! Glad I could help 🙂, although it's a bummer that Apple might have changed something on the connection protocol that might have generated this problem in the first place.

Best,

Thiago

Kooksy

Level 1

8 points

Oct 19, 2015 7:10 AM in response to ThiagoA.S.

I've rolled back to Yosemite - not used to Apple products not working if I'm honest so a little disappointed! Will stick with Yosemite for the foreseeable future.

Ledje01

Level 1

0 points

Oct 19, 2015 9:25 AM in response to elaverdiere

Same problem here, I have a Lacie cloud box and in finder it gives a "?". I only can access it via the dashboard. Can I solve this with killall Finder in terminal ?? thanks

WDI

Level 1

83 points

Oct 21, 2015 9:06 PM in response to elaverdiere

Same problem connecting to Lacie Cloudbox after El Capitan update. Today I updated to 10.11.1 hoping it would fix the issue but nope!

Oct 24, 2015 8:43 PM in response to elaverdiere

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

Oct 25, 2015 3:53 AM in response to elaverdiere

Same sort of problem for me. Losing connection in Finder from my Mac to my Synology NAS folders since upgrading to El Capitan.

Have upgraded(!) to the latest public beta 10.11.1 Beta (15B38b) and still the problem exists.

As others have helpfully said, rebooting the Mac (not the NAS) or Killing the Finder process is a workaround for now.

I find Killing the Finder Process through the Activity Monitor is the quickest method.

Hopefully a fix will come soon!!!

hestroy

Level 1

10 points

Oct 25, 2015 12:21 PM in response to elaverdiere

Same problem here. Instead of the icon of my Lacie 5big in Shared I can see the question mark. I don't understand how can Apple release the new system with this bug.