It started out of nowhere—my macOS Finder would regularly freeze when trying to access a shared network drive. These weren’t exotic or particularly large drives, just standard Samba (SMB) shares hosted on a reliable NAS in a small office environment. The problem wasn’t immediate; it crept in gradually after a system update, and soon navigating network files became a frustrating, time-wasting ordeal.
TL;DR: If your macOS Finder freezes when accessing SMB network drives, the issue may be related to SMB signing. Disabling SMB signing on macOS can significantly improve network file browsing performance, especially when working with older or underpowered NAS devices. This workaround isn’t ideal from a security perspective, so it’s essential to weigh the trade-offs. Follow the outlined steps carefully to test whether this solution works for your environment.
Understanding the Issue: Finder Freezes on SMB Access
macOS Finder is usually responsive, even when working over a local network. So it was particularly jarring when accessing my file server began causing slowdowns, spinning beach balls, and even full-on system freezes. Logging in to a server via Command + K and mounting the drive worked—but as soon as I clicked on any folder or drilled into a directory that contained a moderate number of files (say 50 or more), the Finder would lock up for 10–20 seconds.
Sometimes, the only fix was to force-quit Finder or even reboot the system. This issue affected daily workflows and made working directly off the network share nearly impossible.
Initial Troubleshooting Attempts
I began with a standard set of troubleshooting tactics that are often successful with local network issues:
- Restarted both the Mac and the NAS
- Tested different macOS user accounts
- Mounted the drives using both the server name and IP address
- Tested on different local networks (wired and wireless)
- Used
smbutil statsharesto check mount stats
These steps ruled out network routing issues, user profile corruption, and even Wi-Fi-specific problems. But the problem remained: Finder struggled (and sometimes failed) to list the contents of network directories. Interestingly, accessing the files via the command line using ls or using third-party file managers was much faster—clearly pointing to something specific within the Finder + SMB interaction.
Suspecting SMB Signing
After diving into macOS documentation and several network-focused forums, I came across multiple users reporting that SMB signing—a protocol feature that ensures the authenticity of SMB packets—was responsible for similar slowdowns. Although SMB signing provides a layer of security, it comes at a performance cost.
Here’s what I found:
- macOS, beginning with Monterey, enforces SMB packet signing more strictly.
- Performance issues often occur when the NAS or SMB server has limited resources or incompatible signing configurations.
- Disabling client-side SMB signing in macOS can boost file browsing performance significantly—especially for local, trusted networks.
The signs pointed toward this being a potential root cause of the Finder freezes. I then decided to test the SMB signing workaround that several users had recommended.
The SMB Signing Workaround
To disable SMB signing on macOS, you need to modify the system’s SMB configuration file. Here’s how I did it:
Step-by-Step Instructions
1. Create or edit the SMB configuration file:
sudo nano /etc/nsmb.conf2. Insert the following lines:
[default]
signing_required=noThis setting tells macOS not to require SMB packet signing for all SMB mounts by default.
3. Save and exit the file: Press Control + X, then Y, and hit Enter.
4. Restart your Mac to apply the changes.
After that, I re-mounted the network shares and started testing folder navigation in Finder.
The Results
Almost immediately, the difference was noticeable. Network directories that previously took 15–20 seconds to open appeared in under a second. Finder no longer froze. The system remained responsive while switching between folders and listing large image libraries and project directories.
The performance, although not identical to browsing local drives, became acceptable and reliable again—restoring a significant chunk of daily productivity.
Security Considerations
It’s crucial to understand the trade-off involved in disabling SMB signing. SMB signing is a security feature that helps prevent man-in-the-middle attacks by validating the authenticity of the server. Disabling it reduces that verification, which could be a concern in open or hostile networks.
In my case, the NAS and Mac were located within a small, secure office LAN with strong physical and logical security policies in place. If you’re accessing files over VPN or untrusted networks, this workaround may not be appropriate or secure enough for your usage.
Other Safety Options
- Instead of disabling SMB signing globally, you can configure it for just specific hosts (see additional options in comments of
/etc/nsmb.conf). - If working within a larger organization, consult your IT department before disabling signing.
- Ensure your NAS has the latest firmware and supports modern SMB versions (preferably SMBv3).
Alternative Fixes Explored
Before arriving at the SMB signing workaround, I explored several other options. Some yielded minor benefits, while others gave no improvement. Here are alternatives you might consider depending on your setup:
- Change the SMB version: You can force macOS to use a specific SMB version like SMB2—which can help with older NAS devices—but this may impact file compatibility.
- Use NFS instead: If your NAS supports NFS and you’re comfortable managing Unix permissions, this protocol often provides better performance than SMB.
- Switching File Browsers: Apps like Path Finder or ForkLift handle network shares differently and sometimes more efficiently than Finder.
Conclusion
When Finder starts freezing in macOS as you access network shares, it doesn’t take long before the issue becomes disruptive. After much frustration and testing, I found that disabling SMB signing on macOS resulted in a significant, consistent improvement in performance. This solution may not be ideal for everyone—especially if security policies require SMB signing—but for trusted internal networks, it’s a workaround worth trying.
Always take a methodical approach—test it in a safe environment first, and consider the broader implications of any system-level changes. For me, this fix brought Finder back to life and made my shared drives usable once again.
If you’re struggling with a similar issue, I hope this breakdown helps you resolve it with fewer headaches than I endured.