NAS Access in Catalina issues

exact and so this is not an option and also not a workaround.

As said, my Mac FIND the NAS but they lose performance with preview. Disabling the preview option makes it faster.

But still, something as per each access of NAS stored files makes it slower and slower

==> Preview is buggy ( QuickLookGui or so process hangs )

==> Network layer on Catalina is buggy

DEAR APPLE GUYS, I LEARNED, YOU CHECK THE BLOGS.

SO PLEASE BE SO KIND TO PICK THIS UP ... THIS IS A SYSTEMIC ISSUE.

PLS CHECK BLOG other than this AND YOU FIND EVIDENCE.

Having exactly the same issue with a QNAP NAS and on Catalina 10.15.2. I can connect just fine to the NAS via SMB and only use SMB3 on my NAS for speed anyway. However this problem reared it's ugly head after upgrading to 10.15.2 just before Christmas, when running backups I would get reports that the NAS had disappeared yet the icon still shows for the server as mounted, trying to unmount the server throws the Finder and thus other apps and the machine into a frozen and unresponsive state. Leaving the only option but to hard reboot the machine. The server is still accessible via web interface on other machines and checking the logs the share never drops a connection, this is only appearing on the MacOS side of things. Like others have reported it affects browsing web pages and finder usage.

Apple's testing before pushing updates out has got worse over the years I have noticed more issues popping up with release especially when affecting large implementations of things like SMB for instance. I really hope this can get fixed soon, not being able to run backups is absolutely killing me!!

It is really an apple issue. I have installed windows 10 on my macbook using bootcamp and have no issues at all using my NAS on windows 10, but it’s unworkable in MacOS Catalina.

I wish Apple would recognize this issue and resolve it.

It seems the problem has gotten worse with 10.15.2. It used to be I had show-stopper issues on my MacBook Pro but no real problems on my iMac Pro. After updating, nothing got better for my MBP, but I can no longer trust that my NAS connections will remain stable enough for my video editing software (Davinci Resolve) on my iMac Pro. It's TERRIBLE.

I was already more than halfway inclined to get a Threadripper system instead of a 2019 Mac Pro for 2020, but gosh, if something as as simple as a NAS no longer works with the OSX ecosystem, there's absolutely no reason to remain on Macs of any kind.

So I have as mentioned in my earlier posting been having issues with the backups I ran and after exhaustive questioning and research of our good friend Google it occurred to me to try one last thing. I have my SMB set to version 3 on my QNAP NAS so I have never had issues connecting with Catalina, only that it doesn't seem to hold those connections and one program very sensitive to this has been Bombitch Carbon Copy Cloner when running Local > NAS backups on the drive.

I have on a particular set of backups never got past 20 mins max and consistently around 4/5 mins before the issues rear their head and everything freezes like everyone else has experienced.

I decided to run a DNS flush on my iMac using the usual command of

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

I have since run 2 separate backup tasks to the NAS, one taking a little over 2 hours and the second around 30 mins. This at least has appeared to be a short term fix since I haven't tested it at length but I will continue to do so, I just wanted to let people know in this thread that for me at least, this has worked. Give it a try and see how you get on.

Alas, I've tried flushing my DNS cache but the issue returns. I'm glad you were able to at least get your backups to complete, but the issue comes back for me after 2-3 hours from rebooting.

Perhaps the clever moderator who is deleting many of the posts here can do something productive and try to get an ETA on a fix from Apple? This is a MAJOR bug in Catalina that is rendering Macs unusable on networks with a NAS, and we need more information, not censoring and less information.

I have been having problems with my NAS (QNAP TS-231P) on my MacBook Pro (mid 2014) running Catalina 10.15.2. Clicking on my NAS on the sidebar or via Network gets me a "Connection Failed" and a "Connect As ..." button that does nothing. Connecting via AFP and the NAS network address works temporarily, but the problem keeps coming up. Before 10.15.2, my NAS got along with my Mac just fine. Basically, the same story repeated many times in this thread.

I can log in to my NAS management software on the MacBook via the web interface. All of its software is up to date.

I also run Windows 10 (on an older Mac Mini) and it gets along with the NAS just fine, no changes. So, Apple, I think this one is on you. Please fix soon. This problem is very annoying.

Thanks.

On of the commentors said that they are running the 10.15.3 preview and it seems fixed in that.

this is my main machine, and I can't take the risk, but have others tried that ? Does the preview for .3 really fix the issue ?

If some of you who have the flexibility to try it and report, would be great!

> On of the commentors said that they are running the 10.15.3 preview and it seems fixed in that.

I'm downloading beta2 now. Will report later. A previous beta of 10.15.2 fixed some other issues for me, so I'm quite keen to try out 10.15.3 beta2. Fingers crossed. I haven't had any feedback on my bug report, so it may not have been fixed yet.

> I'm downloading 10.15.3 beta2 now. Will report later.

Nope, unfortunately. Seemed better for a while, switching user, connecting disconnecting, standby resume, but when turning Wi-Fi off and then back on, the sempiternal "cannot find directory" dialog came back again.

But... there seems to be some progress: I now always see the NAS in the side bar and, when I click on it, the NAS directories. I'm also now always connected to the NAS. And when I press disconnect (yes, that button now works again!), the Finder reconnects automatically.

So, not quite there yet, but some good steps in the right direction. Keep up the good work Apple!

Having the same issues for some time...

I can connect via Finder -> Go -> Connect to Server ... but it doesn't stay connected. Clicking on Connect as... doesn't work like others have mentioned. Restarting the iMac used to fix this issue but that isn't working anymore though I haven't made any changes. Force-quit of Finder also used to work before but that has stopped working as well. So none of the workarounds are really work arounds. Flushing the DNS cache also has no effect.

Somehow TimeMachine continues to be able to back up to the NAS shared folder for me which seems interesting. Keeping my fingers crossed because I don't know when that will stop as well (like the previous workarounds for Finder that stopped working). Really waiting for Apple to fix this.

Hello,

+1 to this issue. I manage a small design team with a Promise Pegasus RAID drive attached to a Mac Mini on our network.

Since upgrading to Catalina, the ability to connect to the Mac Mini via Finder 'Connect As…' results in a Failed message.

We can still connect via Connect to Server (Apple + K) but given how often we need to save or open things on the shared drive, it's very frustrating.

This issue has been getting steadily worse for me. Now my NAS no longer shows up automatically in Finder, even though Bonjour is on. Instead I have to use the Go >> Connect to Server route, and manually connect. The connection is even less stable now, to the point where my TimeMachine backup hangs and never completes. Restarting the computer and even the NAS is no longer clearing the issue. Clearing the DNS cache doesn't help, nor does any other "workaround". My computer is completely unstable on any network with a NAS, and I have to restart constantly as apps that seemingly have no relationship to the NAS hang and cannot be restarted.

This is a SHOWSTOPPER issue, as it not only undermines the stability of OSX, but it jeopardizes user data. There are only so many times that a connection can be improperly broken while running a TimeMachine backup or accessing/updating a remote Photos library before the target data becomes corrupt.

FIX THIS APPLE!

@OM2 -- thank you for your detailed response. At this point I would have sacrificed a small goat if someone had suggested it might fix my problem. I followed your steps to the letter, but alas they did not work for me. I even tried twice, the second time restarting the NAS and clearing all connections from there, but the NAS never appears under Network or in the sidebar. I've checked and rechecked the settings in the NAS to ensure Bonjour is turned on and the NAS is discoverable from the network (keep in mind that I never changed any of the NAS settings from before, when my MacBook was discovering it automatically.) Zilch. Nada. No dice.

The only way I can access the NAS now is from Go >> Connect to Server, and that connection has all kinds of problems. It disconnects (as the connection used to from the sidebar), and even when it is working, backups take forever, despite no issue with the network or the NAS. (I can upload/download large files from Synology Drive without similar delays.)

Whatever this bug is, it's deep enough to destabilize all the apps on my Mac when it's on the same network as my NAS (they run just fine when I'm off the network), and it's persistent (nothing seems to work to clear it out and get back even to the original state.) Worse, because of the improper disconnections between the Mac and the shared folders on the NAS, data is being corrupted and lost. As I mentioned in my last post, there are only so many times that TimeMachine can lose connection, mid-backup, or Photos can lose connection, mid-library-update, before the underlying data is damaged and/or lost.

@OM2

Happy to elaborate:

1) My NAS is networked through an Asus router. Rebooting the router does not resolved this issue.

2) My device name has not changed. The device is auto-discovered and works just fine on pre-Catalina macs.

3) What drive unit are you referring to? The drives in my NAS? The SSD drive in my MacBook Pro?

I appreciate you trying to troubleshoot the issue, but I don't think there's any easy, reliable fix. This is a known issue with Apple and Synology (and I'd guess other NAS manufacturers), and lots of affected users have tried lots of proposed workarounds and fixes, with nothing being a silver bullet. Those of us who are affected are likely stuck until Apple issues a fix.