NAS Access in Catalina issues

Hello ropstop,

I do apologize for any confusion.

Quoting Merriam-Webster’s dictionary, broadly speaking, it is the floating wreckage of a ship or its cargo.  It was used from the 16th and 17th century by English speakers to describe claims of ownership to one of the three types of debris left over from a sunken ship.  The word is from the old French “floter”, meaning to float.  It can also mean rubble, ruins, residue.

I used it here to describe "the debris" of various unsuccessfully attempts to fix something. 

OM2

I also have this problem since upgrading to Catalina. The only workaround I have is to re-launch finder at the start of every session. Then I can mount shares via afp from my Synology NAS without problem.

This seems to be a broader issue than simply NAS. It's been bugging me enough these last months to actually get me to register here and make my first post.

I run my Mac through ethernet and use SMB shares to two separate windows machines. One large scale storage server, one local desktop. My network is pretty standard. Fancy Netgear router, server and a couple of smart devices wired to that along with a longer run going to my Time Capsule in bridge mode. The Mac and my PC are then run off that. The PC has no issues whatsoever connecting to the server whereas the Mac shows the same behaviour with either the server or PC.

Connections to either will generally drop out if left idle with no finder window open and once they drop out, I need to relaunch Finder to be able to get it back. If I leave it dropped out, other applications can have a wildly erratic results when they try to access the network shares as well.

The error is always the same.

The operation can’t be completed because the original item for “Network Share” can’t be found.

Just going to the root of the share for that server and trying to disconnect then connect as yields nothing. Finder think's it's disconnected but trying to reconnect offers no response, and opening a new finder window to that server shows that it's still actually connected despite being unable to do anything with it.

This problem first appeared when I upgraded to Catalina. A clean install of Mojave works fine with no issues. I'm on day two of a clean install of Catalina and the issue is already rearing it's head.

This is an unacceptable problem to have when combined with Apple's recent push back into the pro scene. Having to repeatedly relaunch finder and lose tabs is massively jarring to my work flow.

This should have been fixed months ago. No excuses at this point.

Hi all, I have been posting in this subject regularly. I don't know what happened, but the problem has magically resolved and I can now access my NAS again with a fast and stable connection. Not sure what happened.......

It goes deeper than simply this Jamsbe.

I've just gone through and ensured that SMB1 is completely blocked on my desktop, rebooted it and to the surprise of no one with the issue. I still can't connect to it without relaunching Finder.

The changes to Catalina have intrinsically broken SMB file sharing seemingly under some circumstances.

Did you change your NAS as well, so it will only support SMB3? This reconfigures your NAS to default to SMB3, not your Mac. I realize something fundamental changed, but this seems to have resolved the problem for my issue; and my experience was mirroring everyone else’s.

So the Macs on my network are trying to connect to a Mac Mini server (with attached shared drive) via AFP.

Does changing the SMB protocol have any effect on AFP?

And how can I change the SMB on my Mac Mini server? There isn't a 'control pnale' for the attached RAID drive.

The only solution I can find to the Catalina network connection error is to make sure I shut down and restart my laptop every morning, and don't unplug it from the network during the day – pretty annoying when taking the laptop to meetings!

> use these links on favorite sections instead of the one in network.

I've noticed this as well.

BTW, there seem to be some improvement in the way shares can be mounted in 10.15.4 beta 1. Fingers crossed.

Hi,

This is a good clarification and might by why this workaround is effective for me and others who is the finder.

I always access my NAS through the finder side bar in the way Cemento shows. So, when I change my SMB protocol on the NAS, the behavior I experienced of disconnects went away completely.

Well, I would have posted an update sooner but couldn't, due to being banned from this board for the last couple of weeks. Apple's censoring efforts backfired as they prevented me from updating all of you to let you know that my NAS issues have quietly resolved since 10.15.3. They didn't resolve immediately upon updating, but did so at some point within a week or so of the update. My guess is that 10.15.3 fixed the issue (or at least alleviated it), and then once the various cached data/connections were refreshed, the new ones worked correctly. Since then, my Timemachine backups have worked, and the NAS continues to show in my sidebar without issue.

Unfortunately, after rebooting both my computer and the NAS, it appears that the issues returned. Today several apps on my computer, including Chrome and Quicktime, froze and could not be quit and restarted. The NAS still showed as connected in Finder, but some of the folders could not be opened, as if the entire shared drive was offline. As before, TimeMachine backups somehow kept happening, despite this (at least partially) bad state. I had to reboot my machine to get things working again, at least until the next occurance.

Apple's moderators need to stop deleting messages from this thread. Their actions are making it nearly impossible to follow the reports and information that are coming in from users.

For instance, anyone reading this thread today would have no idea what caused my issues (and that of other posters) to recur, after appearing to have been resolved by 10.15.3. So in the interests of actually trying to help other users (and Apple, if they actually care), here's what happened:

About a week after updating to 10.15.3, my issues had largely disappeared, so I posted, letting the board know that. Another user, whose post has since been deleted, replied that I should wait and see, as he had also thought 10.15.3 resolved the issues, but they later recurred when he restarted his NAS and his Mac. I told him I'd try it, and unfortunately, upon restarting my NAS and Mac, the issues started recurring.

So, for those folks who believe 10.15.3 fixes their issues, have you tried restarting your NAS and Mac yet? For me, at least, the problems started up again immediately, and I now have to do a hard reboot (holding down the power button) of my Mac at least every day to get my computer functioning again. When the NAS issue occurs, it causes apps (including Finder and Chrome) to freeze and be unquittable. Folder on my NAS appear offline in Finder, even though TimeMachine backups are still happening.

I had to come here share my own findings. Can't say for sure, but seems like a problem only in Finder. Killing Finder and restarting fixes it at least temporarily. Problem happened immediately after upgrade to Catalina from Mojave.

*** Issue description**** Had the same problem. Can't always access my QNAP NAS from finder by clicking on the NAS name for the SMB connection (MyNAS). Sometimes clicking on "connect as" doesn't do anything, and other times it will show the root folders but clicking on any will say directory does not exist. If in Finder I click on the AFP connection to my NAS (MyNAS (AFP)), works fine. IP address also works. My NAS is set to run only SMB 2 & 3.

*** Non-finder connections work**** Strange thing, my TimeMachine backups, pointing to MyNAS(TimeMachine) work fine. It is using SMB and the NAS name (not IP). I have other automated backups running in the background also using SMB, seems to work most of the time—I have some backup issues in another software but not sure if related.

It really seems like it's a Finder issue.

**** Killed finder, works***** Here's something I tried and worked. I killed Finder (Force quit > Finder > Restart), when to my NAS in Finder (the SMB one), and was able to browse the content just fine.

I'm hoping Apple will fix this. I don't want to connect using AFP and don't want to connect using IP. I just want everything to work as intended and as it did before I upgraded to Catalina.

I have been using a QNAP TS-231 P for some time with my MacBook Pro (mid 2014). Since updating to Catalina, connecting to the NAS has been a big pain and very inconsistent. My symptoms are consistent with the vast majority of the complaints in this thread. Based on my observations and struggles, I agree with those who assert that the problem is with Finder.

Please, Apple, fix this soon. All of my other connected machines work just fine with my QNAP (its software is up to date).

I also have the QNAP TS-231P. I don’t think the problem is specific to that model or even QNAP, I’ve seen similar issues described in other NAS brand forums including Synology.

Another symptom of Finder issues is when I try to put a folder from the NAS into my sidebar favorites in Finder, it shows up as ? instead of displaying the folder name.

***Not only Finder?**** It is possibly not only related to Finder. I run a software that backs up my iOS devices to the NAS. After the Catalina upgrade, I’m constantly getting errors like “folder not found”. The connections seem broken.

Apple needs to say something, at least acknowledge they know there is a problem. Right now many people are having issues but there is no solution is sight.