NAS Access in Catalina issues

Not sure, if this resolves your problem, but I actually managed to resolve the NAS time machine backup problem and the connection problems for my time capsule in Finer. In the Time capsule settings, the iPv6 connection sharing had to be disabled for internet (advanced options). And it does not matter whether any smb or afp file sharing is enabled on the computer or not. I do not know what changed in Catalina (or perhaps on my providers iPv6 protocol side, but it started after upgrading), but remote backups over Wifi on time machine work again, and also the finder properly connecting to the time capsule drive. So it is not a firmware problem, as an Apple support person indicated, and I do not need to go back to Mojave.

Just wanted to let you know, as quite some other users seems to have the same problem after upgrading.

Tried killing “sharingd” myself and didn’t work much. Tried killing it from Activity Monitor, didn’t seem to work so had to do it in terminal with “killall sharingd”. Worked less than a minute. Had to try several times, would still lose connection right away. Rebooting worked a bit longer but the issue always comes back eventually.

Hi folks,

Since I upgraded to Catalina in March, I am also having the same severe issues with Finder performance and stability, especially affecting working with my NAS (Synology) as described by others.

Access via Finder is extremely unreliable and in such a way that there is no normal way of working anymore. Frequent 'force quit' and 'relaunch' became the new standard, in combination with regular rebooting of my MacBook.

I went through all the 100++ posts and tried out several suggestions myself in the beginning. Only concluding what has been said so many times before: There are good suggestions for a workaround, some may work for a while, but there is no real solution (yet). We are all waiting for Apple to come up with a release that fixes the issue or at lest joining this discussion.

We all know that both hasn't happened. Probably because there are some NAS users who do not have the same problems as we and Apple can claim that we are dealing with individual issues. Personally, I am not convinced that this the case.

So, why not trying out something else within this limited and very knowledgable and active community. Can't we collect some facts that might differentiate our systems from those who do not have the same issue with their NAS?

Let me start:

- Running Catalina 10.15.2 (Dec'19)

- I am using both LAN ports of my DS 412. Directly connected to the router, no switch. 

- Network traffic from my MacBook air goes via LAN, via a Gigabit switch. WLAN is sometimes switched on as well to connect to another network. (But I have deactivated WLAN for the moment and still suffering the same issues).

- I am using different accounts for admin tasks (via DSM web portal), scheduled Backup and normal NAS access. The last two do not have admin rights.

Any other suggestions what information may be relevant to collect?

Anyone else who want to share their specifics?

I respect the suggestion of posting detailed specs here, but I don't think you guys are aware of the full history of this thread. That's because a lot of earlier postings have been deleted, and users banned for talking about the same topic, i.e. how to encourage Apple to finally address these NAS issues. Heck, I'll probably get banned just for mentioning that history, but I think you newer users to the thread have the right to know the full story.

Apple's engineers have had detailed reports and system logs from many of us on these issues for 6+ months. Last fall, several users (including me) were told by senior Apple support people that NAS issues were just a lower priority than issues with conversations of 32-bit apps, but might be addressed after. Now those other issues are long closed, but the NAS issues persist. Whatever is causing them is likely known to Apple, but time-consuming or costly to fix. Apple has no financial incentive, and actually quite a strong disincentive (i.e. revenues for their own storage and cloud solutions), to put in the time to address these issues. NAS support is just not enough of a deal-breaker for enough users to actually affect Apple's sales.

Now, on the other hand, device manufacturers have contracts with Apple to integrate with and license Apple's hardware and software. For those manufacturers, such as Synology, these issues have a much larger impact to their revenues. What Mac user is going to buy a NAS if it's widely known that they don't work with the current versions of OSX? We need to keep filing tickets with the device manufacturers, and encouraging them to push Apple for a fix. That's the only way these issues are likely to get resolved.

It's also worth noting that this goes further than just NAS connectivity issues. I'm having the exact issues described here accessing SMB shares from a large hardware raid running on a windows server box. I suspect anyone who does something like collaborative video production on a Mac over ethernet shares will be running into this issue if they leave their workstations encoding overnight as I typically do.

This isn't specific to the likes of Synology at all. It's an issue with how Finder is handling SMB shares or perhaps even how it resolves DNS locally. I'm always able to connect via IP even when trying to connect via machine name or even sidebar favourites have given up working.

Mac's are superb video editing machines, but this is a pretty significant flaw in that area. Is it time for another Snow Leopard style release yet?

Unfortunately, I believe potential fixes involving DNS, network settings, and local names/network aliases were already tried and ruled out earlier in this thread. Many of us have even tried connecting via a static IP to the NAS, but the issue recurs after some time, especially if the computer and/or NAS are restarted.

To anyone who believes they may have fixed their issue using some process outlined in this thread, please try restarting both your computer and your NAS and see if the issue recurs. So far it appears to have recurred for everyone who's tried.

Yes, I have used the "Go > Connect to server" method, and it only made the problem worse. My machine still lost connection to the NAS, but after rebooting the NAS no longer appeared anywhere, including in the Network sidebar. I had to remove the "Connect to server" configuration, clear all caches and keys, clear out all the connections from the NAS, and then restart my computer several times to get the NAS to show up again in the sidebar.

Sometimes I get the question mark too but then clicking on the icon the link recovers and the share is accessible again. More important, I never had Finder crash with this workaround. However I’m not stressing too much the system since it’s an home network with limited number of hosts and shares.

@Fly_PetitPrince

The Synology NAS is connected by its IP-adress in Finder (GO - Connect to server).

The Time Machine share was dragged to the Finder left column.

I also implemented a Automount app (ConnectMeNow, it is in Dutch), but that does not seem to help very much. If Time Machine is launched, it opens the share directly.

After applying this, I have not had the horrible message above that the TM bundle is corrupted, for more than 1 week now. (always nice to see this in French also...., misere international, non?)

For the sake of reliability, TM is also making a backup on a local USB-drive.

Hope this will help you as well.

Cheers,

Martin

Thanks Martin. I had already done that. If I reboot, it works for a short while but my work around is still working and doing the job. In fact, I copied the mounted folders back to Finder and they still work but clicking on the NAS in finder still doesn't connect. I am OK with that and all my Surveillance and backups have continued to work. I think there may be a bug within Finder.

Final report... running a recursive diff of folders in the Mac file system via a Parallels VM against a Synology NAS. 319 GB (343,550,832,640 bytes). No differences reported so far. I believe that with a Parallels VM of Windows or Linux this is a valid test of backup of data to a NAS. No instability in Finder or the Mac at all, as Finder is not involved and the Mac apparently has not awareness of the VM connection to the NAS.

Not saying that I like it, but it is a workaround while we wait for Catalina to stabilize.

echo "port445=both" | sudo tee -a /etc/nsmb.conf

Hmm... not a long term solution. The "Reconnect as..." button no longer works this morning after waking the computer from standby.

After 4 month and 3 major updates bug is still here. Not solved by 10.15.3.

Good job Apple!

same issue here.

Opened up a case at synology. They pointed me to apple and ask me to open a case at apple support.

the only way is to create a support case at apple.

Please all do this.