SMB File Sharing not working in Ventura

"My case is not resolved with 13.3. The workaround (sharing off - reboot - sharing on) still does work."

Tip: Before you reboot, Go to Settings/General/Sharing and click the little circle with the "i" next to the toggle. It will bring up a list of shares. REMOVE ANY SHARES THAT ARE LISTED. Then turn file sharing off and reboot. Then turn file sharing back on. That is what finally worked for me.

P.S. You can turn off SMB from that same nested dialogue (click "Options") if you want to experiment.

abromber

This solved the problem for me too. Just to be clear, I tried rebooting, toggling it off and on again, rebooting again. I even tried waiting a bit in between toggling it off and on again. I still couldn't connect. The only thing that got it working was turning it off, restarting while File Sharing was off, then turning it back on afterward.

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". :-)

It seem everything reloved around firewall at least for me. I just turn off the Sharing and confirm my firewall is turnoff. Then I update the the OSX 13.1 to OSX 13.2. After that I turn on the Sharing and confirm its working fine, but as soon as firewall turn on after 1 min, the problem comes back. So I waited for 6 min and try again with firewall on, but the problem still exist. So i turn off the firewall and restart the machine with Sharing on. It solve my problme.

Final result is = Firewall blocking stuff and problem exsist since launch of the OSX 13

If I'm not mistaken, the smbd full disk access is turned on automatically when SMB file sharing is turned on.

It's not, as noted by many people here. I think it was put into Full Disk Access on my Mac, but it wasn't enabled. When users here noted they could no longer access their Desktop, Documents, and Downloads over SMB, I looked for smbd in Full Disk Access and enabled it to check. I have had to explain to others where to find smbd in order to add it to Full Disk Access. It is completely unnecessary for normal file sharing. It is only under Ventura that the privacy settings prevent seeing folders in the Desktop, Documents, and Downloads folders without user permission. The SMB daemon does not ask for access (at least as far as I could tell).

The way we had implemented SMB on the file-server was through user R/W access to select folders and drives specific to each user. Our file sharing is activated only on the server side and not the client sides. On the client side there is no smbd daemon running.

ll clients were Mac OS Ventura (Intel based) and the server was Ventura (M1 based) as well.

If you use Sharing Only users, you can configure specific permissions for everything within the File Sharing Settings. If you create real users on the Mac, when they log in via File Sharing, they will have whatever permissions they would have if logged in directly. The File Sharing permissions do not override those.

There are times when File Sharing creates ACLs for the folders, and those could possibly override the normal user POSIX permissions.

All - During my testing I all of a sudden made this issue go away, accidently.

I turned on "Remote Login" and "Remote Management". (Under Sharing)

Made sure I had permissions for each (click the "i" by each). File Sharing off.

Reboot.

After restart - Turn the remote options off (or leave them on) and enable file sharing.

My mac now will share files across reboots. I do not know why this is working and would rather it didn't, so we can get it fixed. '

Please try this and report what happens.

If you follow the thread, it is pretty clear that this fix is currently in beta test. It will presumably appear in your software update when testing is complete.

I put on the comprehensive fix (remove all shares, turn sharing off, reboot, reinstate shared folders) - this has worked and I await whether or how long it will stick. Previous suggestions have all reverted after my laptop has gone on standby and restarted. None of the Get Info boxes had 'Shared Folder' ticked, so I didn't had to make changes there.

@swixo - yes -- it fixed it completely on 13.2.1. Everything works normally and has survived multiple reboots, etc. Eventually the shares repopulated in the list, but that hasn't affected anything so far. It's been almost three weeks and I have declared victory. I have not tried 13.3 yet and I am in no hurry. Good luck!

abromber

Thank you, thank you, thank you so much Radek & Garry! I have 3 of 5 mac's where the smbd was broken for many months. I tried everything in this community/support and nothing worked, the iOS updates didn't help (except for 1/5). Today I found this post. Having a look at the firewall settings and setting up the button "allow incoming connections for smbd", worked! Note: I never changed this setting. It must be iOS software update related. I'm so happy, now we can work in the network again after a long period of frustrations!

Barney-15E wrote:

When Apple rearrange the settings, they moved the setting into the Guest user section because it makes more sense there, but it’s not the guest user.

Non sequitur.

It clearly is related because when you select “Allow guest users to access shared folders” for the Guest User on the Mac, the Files App will connect and display shared folders. Unselecting this option removes access to the shares.

Try it yourself - enable share option for the Guest User on the Mac, set up the server in the Files App on iOS or iPadOS, connect, choose Guest and then Next, the connection is made and all shares are displayed. Now disable the “Allow guest users to access shared folders” on the Mac and try to use the connection you just created. An Authentication Error message displays, same as selecting a Registered User.

The Mac GuestUser = Guest in iOS and iPadOS. The real issue is using a Registered User/Username - it will just not Authenticate terminating with an Authentication Error (screen shot above).

MRYFLYGUY wrote:

Barney-15E wrote:

When Apple rearrange the settings, they moved the setting into the Guest user section because it makes more sense there, but it’s not the guest user.

Non sequitur.

It clearly is related because when you select “Allow guest users to access shared folders” for the Guest User on the Mac, the Files App will connect and display shared folders. Unselecting this option removes access to the shares.

Try it yourself - enable share option for the Guest User on the Mac, set up the server in the Files App on iOS or iPadOS, connect, choose Guest and then Next, the connection is made and all shares are displayed. Now disable the “Allow guest users to access shared folders” on the Mac and try to use the connection you just created. An Authentication Error message displays, same as selecting a Registered User.

The Mac GuestUser = Guest in iOS and iPadOS. The real issue is using a Registered User/Username - it will just not Authenticate terminating with an Authentication Error (screen shot above).

You don’t seem to quite grasp the concept that the guest login for filesharing existed well before the guest user account was created in Mac OS. The setting to enable guest access to file shares was moved into the guest user space in the new settings set up since it makes more sense for it to be there. It may be one of the few things that does make sense in the new Settings layout.

When you enable guest remote login, it is listed as a Sharing Only user, not an actual user account which Guest is if you enable it.

I found I could make it work by using IP address instead of computer name. I thought we were past this sort of solution by now, but I guess not.

The issue was fixed in 13.3 for many of us. I have been running it for over a week, issue is gone.

13.3 solved the SMB problem immediately. Not touching 13.3.1 until I’m confident it doesn’t break it again!