SMB File Sharing not working in Ventura

I tried the "turn file sharing off, then reboot, then turn it back on trick and it didn't solve it for me. Other users on the network can access the files but whenever they save any changes, a temp folder is created in this format "filename.xlsx.sb-***" where *** is about 10 random characters. Those temp folder don't disappear automatically. The only accumulate. I spent 90 mins with Apple Support on the phone and it still wasn't resolved. :-(

This is my problem as well. I formatted the drive, installed a fresh copy of Ventura, setup file sharing. Any edit on a shared file results in several visible .sb folders that cannot be deleted by the user accessing the files. I have spent two days getting a pristine environment, but it just does not work. I am going back to Monterey as I have an entire office down.

In macOS previous to Ventura, I would lose SMB sharing a couple of times a year. To the same machine, I could SSH (remote logon), but SMB sharing would stop working. I wasn't successful in creating a script to fix this, so I would have to VNC or get to the computer, go to the system preferences, and toggle file serving off and then on. I never rebooted for this operation, and it generally fixed things.

I just got my Mac Stadium up and running and my VLC apps running over SMB would either time out or take 3-8 minutes to get connected to the first directory. The new System Settings makes finding the "sharing" harder. I've found that the old "toggle off, breathe, toggle on" has fixed my SMB issues for now. I haven't had to reboot for this to work. Also had to re-setup the directories to be shared.

I finally borrowed a Ventura MacBook to see if it also had the same issue as my non-Ventura Macs. Sadly, the answer is yes. Accessing my M1 iMac Ventura file-share still creates the same temp folders every time you edit a shared file. I'll try the "hassle but workaround" 👆🏼 suggestion next.

hi, your have to do these things pretty much on off, has your tho actually fixed the issue or does this come up from time to time cause in Ventura it has issues when rebooting with user home folders on ext drives.

Hi!

Just now I have updated my Mac mini 2018 from Monterey to Ventura 13.1 – which bricked file sharing. Your solution "turning off – reboot – turning on again" didn't do the trick for me.

In addition, your user MUST HAVE ADMINISTRATIVE RIGHTS!

I had to grant my account admin rights, THEN I did the turn off-reboot-turn on.

After that I could remove admin authorizations from my account and file shaing still works.

THANK YOU ALL VERY MUCH!!

Later today it turned out, I had to deactivate the builtin firewall, too. When I tried to reactivate it, file sharing didn't work anymore. In fact, I had to do the full thing again (grant admin privileges, turn off, reboot, turn on, revoke admin privileges (which needs another reboot).

I had issues with the builtin firewall multiple times in the last years. Last time it was screen sharing, now its file sharing. Well, I gave up. I FINALLY deactivated it. I'm running Little Snitch, which also works as a firewall for incoming traffic, so I still "feel save". :-)

RESOLUTIONS: Note below fix the problem for OSX13.0.1 and OSX13.1 for me. So please try below phase 01 to 04 resolutions and need to use a terminal with the below command.

COMMAND

---------

a. sudo -s

b. Put in the password

c. nano [TYPE BELOW PHASES PATH WITH BRACKET]

d. copy and paste the below phase text starting DEFAULT or MY CUSTOM FIREWALL...

e. Press control+O (^O WriteOut) O as Orange to save and control+X (^X Exit) to exit.

Phase 01:

PATH = /etc/nsmb.conf

SMB PROTOCOL UNDERSTANDING

7 SMB 1/2/3 enabled (default)

6 SMB 2/3 enabled

4 only SMB 3 enabled

2 only SMB 2 enabled

1 only SMB 1 enabled

FOR OSX 13.0.1 = NSMB.CONF INFO

----------------------------

[default]

signing_required=no

streams=yes

protocol_vers_map=7

minauth=ntlmv2

port445=both

FOR OSX 13.1 = NSMB.CONF INFO

----------------------------

[default]

protocol_vers_map=6

port445=both

Phase 02:

PATH = /etc/pf.conf

FIREWALL ALLOW CONNECTION = PF.CONF add in end of the file content.

-------------------------------------------------------------------

PART1:

# My Custom Firewall Rule

pass in proto tcp from any to any port 445

pass in proto udp from any to any port 445

PART2:

NOTE: macOS Ventura or later Steps to unblock all incoming connetions:

a. Open System Settings.

b. Click Network from the sidebar.

c. Click Firewall. If it says “Inactive,” it is turned off. When Firewall is disabled, your Mac does not monitor network traffic, and all incoming and outgoing traffic is allowed.

d. Click on it, and toggle the switch to on so that Firewall is enabled.

e. Then click Options.

f. Then turn off the “Block all incoming connections” switch.

g. You may need to click the lock icon or it will ask you to enter your password to take effect.

PART3:

NOTE: ONLY USE FOLLOW BELOW STEP IF WANT FIREWALL or JUST LEAVE IT OFF.

a. Open System Settings.

b. Click Network from the sidebar.

c. Click Firewall. If it says “Inactive,” it is turned off. When Firewall is disabled, your Mac does not monitor network traffic, and all incoming and outgoing traffic is allowed.

d. Click on it, and toggle the switch to on so that Firewall is enabled.

e. Then click Options.

f. Under list app click on the plus (+) button to add more apps or services and add below services.

Name: SMDB SERVICE

Path: /usr/sbin/smdb

Name: NETBIOS

Path: /usr/sbin/netbiosd

Name: LAUNCH DEMONEDS

Path: /sbin/launchd

g. Then use the drop down connections to “Allow incoming connections” for above app.

h. You may need to click the lock icon or it will ask you to enter your password to take effect.

Phase 03:

FULL DISK ACCESS

----------------------

• Using Finder, go to /usr/sbin

• Locate "smbd"

• Launch Settings

• Go to "Security & Privacy"

• Click the tab "Privacy"

• Click on "Full Disk Access"

• Drag and drop "smbd"

Phase 04:

REBOOT & VERIFY

----------------

Restart the computer and test.

===========================================

ADDITIONAL TROUBLESHOOT

1. Restart the Samba (SMB) IN TERMINAL

sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.smbd.plist

2. Reset the LOCALKERBEROSREALM encrypted key.

Delete com.apple.smb.server.plist (you'll need to authenticate), then restart, com.apple.smb.server.plist gets created & properly populated without a Kerberos Realm. At following path = /Library/Preferences/SystemConfiguration/com.apple.smb.server.plist

===========================================

Resources URL

- NSMB.CONF : https://www.manpagez.com/man/5/nsmb.conf/

- NSMB.CONF more INFO : https://www.truenas.com/community/threads/what-are-the-optimal-macos-settings.93986/

- RESOLUTIONS 3RD PARTY : https://apple.stackexchange.com/questions/362739/what-causes-some-network-drives-using-smb-no-longer-connect-to-macos-catalina

- FIREWALL 1 = https://macreports.com/what-does-block-all-incoming-connections-do/

- FIREWALL 2 = https://www.lifewire.com/open-a-port-on-a-routers-or-computers-firewall-5072435

- FIREWALL 3 = https://stackoverflow.com/questions/42752245/mac-osx-open-a-port

- TROUBLESHOOT SMB Restart = https://www.geekbitzone.com/posts/macos/smb/macos-restart-smb/

- SMB PROTOCOL UNDERSTANDING 1 = https://forums.macrumors.com/threads/smb-broken-with-monterey.2324371/

- SMB PROTOCOL UNDERSTANDING 2 = https://www.droidwin.com/smb-samba-not-working-in-macos-monterey-fix/

- RESET LOCALKERBEROSREALM encrypted = https://mjtsai.com/blog/2022/12/30/fixing-smb-file-sharing-in-ventura/

SMB and support for MS Office Applications:

There is an additional issue that may be related to SMB sharing while using Microsoft office (Word, Excel, PowerPoint) on a network. Office applications create temporary cache directories with an ".SB" extension that are not removed by the application.

We have designated a Mac-Mini as our file server and since the Ventura upgrade MS Office is unable to delete any of the temporary ".SB" files. The file server is accessed by several users and the amount of garbage left behind by the MS Office as the result of SMB malfunction is significant.

Interestingly, even as a registered user on the file server you can't delete these ".SB" folders from the remote computer. The error message "The operation can’t be completed because you don’t have permission to access some of the items." occurs when trying to delete as a remote registered user with read/write permissions. You have to physically access the platform as an administrator and delete these ".SB" folders from the file server.

Also, turning the file sharing ON and OFF does not fix the problem.

We are certainly considering switching to Ubuntu Linux after 20 years of using Apple for our back-office. It is a shame.

I seemed to have resolve the file sharing issue... at least for the moment.

I turned off File Sharing and Media Sharing on both iMacs, shut down both, restarted both and turned file and Media Sharing back on. I don't know if that even mattered.

Now, this happened exactly the same on both iMacs... In Media Sharing under the (i) there is the option to turn Home Sharing on. It was on so I turned it off and turned it back on again. This required my AppleID & Password which I entered. This gave me an endless spinning wheel by the ID I had to Option-Command-Escape out of System Settings. I went back and tried again and this time it said Home Sharing has been turned on and the appropriate Family Icon Drive appeared.

I have tried everything except the Terminal Commands since I dont quite understand them......This has totally broken our office file sharing and sorry I upgraded to Ventura....BIG mistake!

My laptop connects just fine but 4 other users cannot and I have wasted 2 days of my time trying to replicate what this sees and theirs does not......I am frustrated beyond all belief at Apple

I'm struggling through this myself. If you read my post a bit earlier; I describe how I turned everything off and on again... with some difficulty... and that seemed to help but Media Sharing still didn't work and I lost it on restart but...

Now I'm logged in with the same ID and Password on each machine in General > Sharing > Media Sharing > Home Sharing & Share media with guests.

There is also (Your Name) > Family Sharing to select Family who can access.

Privacy & Security > Full Disk Access > SMBD is on.

On desktop Menu > Go > Connect To Server, I've saved the working path to the other device. Like smb://(other-mac-name)._smb._tcp.local

I have Energy Saver > Wake up for Network Access Off so I think that's why the other computer has to be awake to access... but I haven't tested that.

Good luck.

This happens to me, but I detected it only happens when Screen Sharing is-was connected, apparently VNC service has conflicts with SMB service. So To allow the data to work, I need to not have been connected with Screen Share. (thats why it works)

but then, If I connected to read files, I cannot connect to VNC server on my MacMini with M1 and Ventura updated.

I am having sharing issue to in osx Ventura. I try every possible thing, but only thing works is the turning off the firewall.

It seem like it blocking smbd, netbios, launchd, 445 port and many other services. I have turn off the firewall deleted "com.apple.alf.plist" at "/library/preferences/", restart the osx, turn on the firewall and restart the osx. It works after that but than restarting 3rd time it goes back to problem. So I turn it off completely as no solution found internet and waiting for next update. Hopefully apple will solve the issue.