NAS Access in Catalina issues

I have a work around that appears to be working for me on Catalina 10.15.6. If I reboot the Mac, Finder works when I click on the NAS but after 30 mins or so, it just won't connect. So this is what I have done

1. Reboot and click on the NAS. For about 30 mins, you should have access.
2. All the folders appear
3. Make an Alias for any folders required and copy these to your desktop
4. Double click the Alias and the folders are mounted and accessible even when they aren't in Finder

Whether this solves everyones problem, I don't know but hope it is helpful.

@Rob-VB

Perhaps is helps if you setup your NAS on fixed-IP and reserve a fixed-IP address in your DHCP-server for the NAS (typically your internet modem).

And then declare this IP-address in Finder (Go server) and place the associated NAS shares in the Finder left column, or on the Desktop. Please see previous posts.

This worked for me.

Cheers, Martin

A fix that seems to constantly make things start working (temporarily, until it breaks again of course) for me is to run this command from the terminal / shell prompt:

sudo killall NetAuthSysAgent

Many of us have been having SMB stability proble\ms for ages, and it's extremely frustrating. SMB file share access is a major part of most professional environments, and for Apple to have issues with it for years is just an embarrassment. If Apple can't write a functioning SMB client - and it's quite clear and obvious at this point that they lack that competence - they should just integrate SAMBA and be done with it.

It's not just NAS devices. Windows Server (2012, 2016, and 2019) shares are problematic as well. This is a joke. Get your act together, Apple.

I have perhaps traced it to the Parallels Desktop Toolbox that ships with the latest versions. Disabled that, and fingers crossed things are working for over 12 hours now.

I have this problem too. My hardware includes a Synology DS1819+ and a LaCie 2big NAS, both with latest patches. My macOS is patched as well to the latest supplemental update of macOS 10.15.4. After a while, I will eventually experience loss of connection to both NAS.

Here are my observations: I can use an alternative to Finder, Path Finder to be specific, to mount, unmount and access both NAS even after Finder has given up. I can access the mounted shares from the Terminal. And, if I enter the path to a mounted share with Cmd-Shift-G in Finder, I can access the share too, while accessing the very same share through the sidebar server location > share crashes Finder.

My conclusion: It seems to be an OSI layer 6 or most likely a layer 7 problem in macOS. That is, restarting, changing protocols AFP/SMB, clearing caches etc. will only provide a temporary relief.

Hello,

To let you know that while it was working fine for few weeks, I also suddenly had the problem again, quite the same time than Datajack, rather strange that we are affected the same days ?

My case @ sinology was not answered so far by Synology on my side...

Finally, the solution proposed by Datajack to kill process called "sharingd" solves the problem temporarily, until it re-appears again. My Time Machine on Synology is strangely not affected.

Fly_PetitPrince

I have the same problem on one of my Macs, an iMac Pro, this happens in combination with a nas from netgear Connection is ok to start with after a reboot and after a while seems gone in finder, the shares are still shown but who clicking them I get an error message. At the same time from the computer the time machine backup on the same nas is still working. A reboot of the computer fixes the connection again but strangely enough also just a restart of the finder. So it seems really a finder issue in Catalina, strangely enough it does not show up on my other mac mini

Dnsmasq is running on an OpenWRT router providing the IPv4 addresses in my network. I defined a static lease for my diskstation (Network -> DHCP and DNS -> Static Leases) so it is always assigned the same IPv4 address and also has a defined hostname (in my case "diskstation"). In the general settings (Network -> DHCP and DNS -> General Settings) is an option for "Local domain" which is "lan" by default. So for all host names (like "diskstation") this local domain suffix is appended. So in my network i can access my diskstation with "diskstation.lan".

This is also the name which can be used to access the network share on MacOS: "smb://diskstation.lan"

Looks like this issue is definitely fixed by 10.15.6.

:-)

For those who had some problems with Time Machine, it's finally confirmed to be a Norton Problem --> https://community.norton.com/en/forums/norton-security-857-broke-time-machine-backup

Fly

Last month I wrote that Numbers and Pages were not working on a SMB share, while all my other programs had no problem.

It turns out it has something to do with a share added as a favourite in Finder (the solution to make SMB work in previous versions of Catalina). When I save from Numbers or Pages to a SMB share which isn't in favourites it works fine.

Hi all,

Apple just released 10.15.3. I just installed it and it seems network share support is working now. Early days to tell, would like to know how you guys and faring.

Cheers

Most of the people is reporting that updating to 10.15.6 fixes the issue with shares no more available. Is not working for you?

I'm very sorry to hear "no joy"!

A few questions, if I may be nosey:

1. How does your MacBook "network" with the NAS? Is there a switch and/or router somewhere in there? Right after Catalina was released and I installed it, I was able to resolve a connectivity problem by just re-booting my router. If there are other network devices involved, and both MacBook and NAS have "static" IP addresses, you might try temporarily connecting them directly to see if your network devices are contributing to your problem.
2. What device name is associated with your NAS? (I don't expect an answer, BTW.). If you changed it from the default, you might check to see if it now contains any spaces. Just to make sure, however, if you did change it, maybe try renaming the NAS back to the original factory default.
3. And speaking of factory default, do you have a "non-destructive" (data) option to factory default your drive unit? I do remember having a non-related issue with my drive that required I default the unit. It only affected the operating system and left data intact.

Best regards,

OM2

A few comments earlier was the hint about standard finder and PowerPoint using different libraries and therefore have different positive and negative effects.

I have do not have up to now any mount-issues with my Synolgy BUT i have a comparable effect re Finder and preview.

What happens:

Select two handful of files with find on NAS Drive, e.g. 10 PDF with total 25 MB size

Try to Drag & Drop somewhere.

==> The first time it works, the second time finder freezes because a QucikLookGuiService ( or so ) freezes.

Kill finder and restart ... still dead.

What I want to says with that is, that the "improvements" around finder seem to contribute significantly to the NAS communication issues.

Doing the same exercise with local files is as well unsexy slow, but finder und QuickLook service do not get hung.

<apple>+<k> ands smb:\\ and SMB2 min on synololgy as well as Finder Dsiplay Optio "no preview" makes ist stable even for the Drag&drop exercise.

Apple guys, pls check FINDER Libraries and the PREVIEW Funktion together with Network to resolve all theses issues

So I am finally able to see the NAS again in Finder, under Network. To get to this point, I:

• Cleared all the credentials for the NAS from Keychain, as @cemento suggested
• Removed all favorite and recent servers from Finder > Go > Connect to Server
• Removed any connections from my Mac within the NAS
• Restarted my computer

For some reason the NAS still doesn't show directly in the sidebar of Finder, but only under Network (it used to show in both, before I tried the proposed workaround of connecting via IP with Finder > Go > Connect to Server), but at least it's there somewhere.

Unfortunately, the original problem persists, and the connections are still going into a bad state after some time. I would agree that there seems to be an issue in the kernel or one of the low-level libraries that causes the Mac to improperly manage the connection/mount for the NAS; however, it seems that there may be other, related issues as well (such as in Finder) that are complicating attempts to isolate the issue. The connect via IP workaround, in particular, only managed to make things worse for me.