Connection Drops with SMB Servers on macOS Sequoia 15.1

Since the update to macOS Sequoia 15.1, I've had the problem that the connection disconnects with some SMB servers when copying large files from the server to itself. Copying files from the computer to the server works, as does copying from the server to the computer.


In other posts, the firewall has already been mentioned, but it is not active. Has anyone experienced a similar problem and found a solution? Making changes to the nsmb.conf file did keep the connection active, but it resulted in corrupted files being written, so it's not a viable solution.


The nsmb.conf that maintained the connection but resulted in corrupted files:

[default]

streams=yes

soft=yes

signing_required=yes

dir_cache_off=no

protocol_vers_map=6

port445=no_netbios

notify_off=yes

mc_prefer_wired=yes


The problem occurs with a Synology RS2418RP+ (DSM 7.2.1-69057 Update 3).

SMB Version client: SMB_3.1.1


Does anyone have a solution or a similar issue?

Posted on Nov 6, 2024 3:43 AM

Reply
Question marked as Top-ranking reply

Posted on Jan 4, 2025 8:52 PM

I had these same issues. My shares mounted in macOS with no issue however, during file transfer, it would kill my whole network stack. I am talking the transfer would stall after 20 seconds to 2 minutes, then the entire network services on macOS would failover, then NAS share disconnects and transfer failed.


My setup was mounting to some Synology NAS shares (DSM 6 and 7), TrueNAS shares, and just regular old linux box shares.


All other client (non macOS) were rock solid, either via SMB or NFS. macOS clients, absolute garbage with SMB.


I tried all sorts of suggestions and configurations to /etc/nsmb.conf. I tried all manner of permissions and service configurations with DSM and exports. These SMB transfer fails are HEROIC failures with macOS.


What has finally worked for me is the absolute DUMBEST fix for an issue I have come across in my 23+ years of user/admin of such environments.


When authenticating to mount the shares, change one character of your user name to be a CAPITAL letter. For example, if you normally mount with a user name of:


nasuser1


Change the user name to be:


Nasuser1


As far as I can tell, adding a capital to any character in your user name has the same effect.


This 100% fixed my file transfer problems on macOS SMB mounts. All clients.


I do not know if this is an artifact of keychain drift over time, some odd formatting of saved credentials, whatever.


Just in case, I am pasting my nsmb.conf content here if it is useful to anyone. A few things are specific to my environment like forcing SMB 3 and disabling signing (I only mount SMB on shares I own in my own network so I am relatively confident in the authenticity). I absolutely HATE the idea of globally disabling such a security feature as packet signing, but alas, Apple has foisted this on us with poor implements of SMB...but I digress.


nsmb.conf


#Try and use NTFS stream if able
streams=yes

#Soft mount so the system don't flip itself off in a fail
soft=yes

#Remove packet signing because Apple does Apple things with established protocols
signing_required=no

#Disable directory cache
dir_cache_max_cnt=0
dir_cache_max=0
dir_cache_off=yes

#SMB3 Only, change value to 6 if need to support 2 and 3.
protocol_vers_map=4

#Remove other SMB1 features because we do not use SMB1
port445=no_netbios
validate_neg_off=yes

#Do not notify
notify_off=yes

#Do the multichannel if avail
mc_on=yes
mc_prefer_wired=yes


So, in conclusion:


I tried all the nsmb.conf optimizations I came across in hundreds of forum posts. They definitely improved the overall transfer speed when transfers were running, but the connection drops that killed my whole networking services on client were ultimately fixed by adding a capital letter in my username when authenticating.


No clue as to why, but for those that have tried everything else, what have you to lose?

24 replies

Nov 10, 2024 3:18 PM in response to ELPiPhone

Thanks! I'll ignore the @eaDir directories as well.


I haven't changed my Time Machine setup and when it does a backup I see Connection entries like this in Synology's Log Center:


User [Darrell] from [MAC-STUDIO(192.168.48)] via [CIFS(SMB3)] accessed shared folder [Time Machine Mac Pro].


So it seems like it MAC-STUDIO should work. Oddly enough, I don't see any entries related to the NFS connections. I do see where the NFS service started up in the log's General entries.


No biggie though, at least I have a stable connection again - thanks again for the suggestion!

Dec 11, 2024 7:59 AM in response to Darrell Spice

I've discovered another issue with using NFS, this one is not so minor.


It doesn't like directories or filesnames that contain "special" characters like ö. I discovered this when I wrote an Applescript to copy selected tracks out of Music onto an SSD for playback in my Tesla. Tracks from:


  • Blue Öyster Cult
  • Sinénad O'Connor
  • Tiësto featuring BT
  • Naïve (album by KMFDM)


all failed to copy. Same things happens with TV shows I have in TV (previously iTunes), such as episodes of Kröd Mändoon - playback fails even though I can see they exist on the Synology.


If I switch the connection from NFS back to SMB the files can seen, but then the disconnection problem returns...


The issue doesn't affect all special characters though, I can watch episodes of Æon Flux without problem.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Connection Drops with SMB Servers on macOS Sequoia 15.1

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.