When Finder fails to display the contents of an SMB network share on macOS, particularly with Synology DiskStation devices, the issue usually stems from corrupted mount points, outdated cache files, or mismatched authentication protocols. This guide provides safe, supported troubleshooting steps to restore visibility without using deprecated commands or destructive file removal.
Understanding the Connection Failure
macOS has significantly changed how it handles network file systems in recent versions. The older method of manually mounting shares using terminal commands likemount_smbfs is no longer recommended and often unavailable in modern operating system releases. Instead, macOS relies on the built-in Network sidebar in Finder and the smb:// protocol handler. When this integration breaks, you might see a spinning wheel that never completes, an error message stating the server cannot be contacted, or simply an empty folder icon where your shared drive should appear.
This problem is common among users connecting to NAS devices like Synology DiskStation. The issue is rarely a hardware failure but rather a software state inconsistency within the Mac’s networking stack or the SMB service configuration on the server side. Before diving into complex fixes, it is crucial to understand that we are dealing with a client-side presentation layer issue, not necessarily a data loss scenario. Your files are likely still safe on the Synology device; they are just not being rendered correctly by the Finder interface.
For more information on ensuring your connections remain stable over time, consider reading Getting Stable Mount Points for SMB Network Shares on macOS for Multiple Users. Establishing a reliable connection structure can prevent these intermittent visibility issues from recurring.
Step 1: Verify Basic Connectivity and Credentials
The most frequent cause of this symptom is a simple authentication glitch or a temporary network hiccup. Before attempting technical repairs, ensure that your Mac can actually reach the Synology device. Open System Settings (or System Preferences on older macOS versions) and navigate to Network. Confirm that your Ethernet or Wi-Fi adapter shows as connected and has received a valid IP address. Next, try accessing the share via a different application. Open Safari or Chrome and type the full SMB URL directly into the address bar, such assmb://192.168.1.100/SharedFolder. If the browser prompts for a username and password and successfully loads the directory listing, then your network path and credentials are correct. This isolates the problem specifically to Finder’s caching or mounting logic.
If the browser also fails, check the Synology DSM interface. Ensure that the SMB service is enabled under File Services > SMB. Also, verify that the user account you are using has read/write permissions for the specific shared folder. A permission change on the server side can sometimes break existing cached sessions on the client.
Step 2: Clear Finder Network Cache
Finder maintains a local cache of discovered network servers and their metadata. When this cache becomes corrupted, Finder may refuse to update its view of available shares. Unlike previous advice suggesting the deletion of entire Finder plist files—which can reset all your Finder preferences and window states—a safer approach involves refreshing the network discovery services. You can force macOS to rediscover network resources by restarting the mDNSResponder service, which handles Bonjour and network browsing. Open the Terminal application and execute the following command to restart the responder:sudo killall mDNSResponder
Step 3: Check SMB Protocol Versions
Synology DiskStation devices allow administrators to configure which versions of the SMB protocol are accepted. By default, newer Synology DSM versions may disable SMBv1 for security reasons, while some older Macs or misconfigured clients might try to negotiate using outdated standards. Conversely, very new macOS versions prioritize SMBv3, which might conflict with legacy NAS settings. On your Mac, when you connect to the share, look at the connection details. If you have access to the Synology Control Panel, go to Control Panel > File Services > SMB. Check the advanced settings to see which SMB encryption levels are enforced. Try toggling the setting between "Enable SMB encryption" and "Disable SMB encryption" to see if compatibility improves. Note that disabling encryption may expose data on unsecured networks, so only do this on trusted private LANs. Additionally, ensure that your Mac’s firmware is up to date. Apple frequently patches SMB client bugs in major macOS updates. If you are running an older version of macOS, consider updating to the latest compatible release to benefit from improved network stack stability.Step 4: Re-add the Server to Favorites
Sometimes, the bookmark stored in Finder’s sidebar becomes invalid. Remove the problematic server from your Finder favorites list. In the Finder sidebar, right-click the Synology share and select Remove from Sidebar. Then, disconnect any active connections to the server by going to Finder > Disconnect in the menu bar. After clearing the old reference, reconnect by selecting Go > Connect to Server (or press Command + K). Enter thesmb:// address again. Once connected, right-click the newly mounted volume in the sidebar and select Add to Sidebar. This creates a fresh, clean link to the resource, bypassing any residual corruption in the old bookmark.
For insights on how Finder handles default folders and navigation contexts, you might find How to Change the Default Starting Folder for a Specific Application Launched from Finder on Mac helpful, as it touches on Finder’s internal state management.
Frequently Asked Questions
Why does my Mac show "Connection Refused" for SMB shares?
This error typically means the Synology device is actively blocking the connection attempt, often due to firewall rules or disabled SMB services. Check the Synology DSM logs to see if the connection was rejected. Ensure that port 445 (TCP) is open and that the SMB service is explicitly enabled in the File Services settings.Can I use SSHFS instead of SMB to fix this issue?
Yes, SSHFS is a robust alternative if SMB continues to fail. It requires installing a third-party FUSE driver on macOS, such as macFUSE, and a terminal tool like sshfs. While it offers better performance for large file transfers, it lacks the seamless GUI integration of native SMB mounts in Finder.Does resetting NVRAM help with network share visibility?
Resetting NVRAM (by holding Option-Command-P-R at startup) clears stored settings like speaker volume and startup disk selection. It rarely affects network connectivity or SMB mount points. This step is unnecessary for fixing Finder display issues and should only be considered if you suspect broader system configuration corruption.What causes the "Server Not Responding" timeout error?
Timeout errors usually result from network latency, packet loss, or incorrect DNS resolution. If your Mac cannot resolve the Synology’s hostname, try using its IP address instead. Additionally, check for interference from antivirus software or firewalls on both the Mac and the router that might be dropping SMB packets.Is it safe to delete the com.apple.finder.plist file?
No, deletingcom.apple.finder.plist is risky and generally discouraged. It resets all Finder preferences, including window positions, sort orders, and sidebar configurations. Modern macOS versions store many preferences in separate databases, making this file less critical than in older versions. Use the killall mDNSResponder method instead for targeted network fixes.