SMB File Sharing not working in Ventura

Hello,

With the firewall off, did you try below steps. If so what was result.

COMMAND

---------

a. sudo -s

b. Put in the password

c. Navigate to below path

PATH = /etc/

d. nano pf.conf

e. copy and paste the below information

# My Custom Firewall Rule

pass in proto tcp from any to any port 445

pass in proto udp from any to any port 445

pass in proto tcp from any to any port 139

pass in proto udp from any to any port 139

pass in proto tcp from any to any port 138

pass in proto udp from any to any port 138

pass in proto tcp from any to any port 137

pass in proto udp from any to any port 137

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

f. nano NSMB.CONF

g.copy and paste the below

[default]

protocol_vers_map=6

port445=both

or use below port

Port445=normal

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

I. give full disk access smb

• 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

J. let reboot and check and let me know if solve the problem

I am so glad I found this discussion thread, I have been going insane for two weeks now trying to figure out why I can't maintain connectivity to shared folders on one of my Mac minis that I am using like a file server and storage. Stopping and starting file sharing, or rebooting the Mini brings back operation some times for a few hours sometimes for a few minutes. Clearly there is a huge problem with SMB in Ventura!!!! I will open another support case because so far I've been instructed to reinstall the OS which I did to no effect, and the next instruction from Apple support was to completely wipe the mini and start over which seems like an extreme piece of advise for a network file sharing issue where it just seems like smb stops responding.

This issue needs attention, Apple!

This is a great summary, and yes I agree if you're looking for something to prevent users from accessing your network, download something like Little Snitch or Lulu. But I have even disabled my Lulu firewall for now just in case that's what's causing the SMB issue.

I'm not sure why people on this thread are so hesitant of using BatchMod. It's more commonly used than people on this thread are making it out to be. So far the temporary workaround I've posted above has been working. It's been roughly 10 hours of use, and the server hasn't timed out even once.

However the steps I've posted on this thread don't work for alias folders that are connected to a cloud service like OneDrive. For some reason I can't find a way to reset permissions on my OneDrive folder and therefore I can't access it through SMB. So in all honesty this isn't a long term solution. Apple needs to fix this asap. And I can completely understand why people are hesitant.

I've also noticed major issues with WindowServer. Ever since the 13.2 update, the SMB connection causes WindowServer to crash relentlessly. You can verify this by opening up Activity Monitor. People on other forums have mentioned that this too might be one of the root causes. But when I spoke to the Sr. Rep at Apple this morning, she stated that the engineers are saying it's surely the Network Firewall that's causing the hang up.

If anyone else gets news, please update this thread. I've escalated this to the highest point at Apple, and I'm expecting someone from the OS engineering team to call me within 3-4 business days.

Yes everything is reversible. Just move your files to a newly created and fresh folder and turn your firewall back on. This will automatically reset the permissions at the folder level. As for the enclosed items, yes it is fully reversible there too. But I suggest you learn how to use Batchmod first. There are tons of threads in this community you can look up that go into a lot of detail. Once the SMB file share is fixed, you'll also be able to set your permissions on there as well.

Here is a thread that talks about Batchmod in detail:

All sharing settings (users and folders a… - Apple Community

I don't want to persuade anyone into doing something that will cause bigger issues, which is why I only recommend this workaround if you know how to use Batchmod. So far it's worked great for me, but again I really hope Apple fixes the issue the correct way.

I can verify that @somuchforlaunch BatChmod solution works flawlessly.........I placed all files in the Shared User area and created multiple groups (folders) based on what access level I wanted users to share (Groups 1, 2, 3, 4)....then used the BatChmod program to assign access rights to those files....been working for 2 or more weeks now with only an occasional hiccup where I made the error in placing a file in the wrong folder and a user could see it because of their access level......no more hiccups

See @somuchforlaunch prior posts on how to use Batchmod.......thank you Sir for pointing me in the correct direction

We are into a second week of official migration to Linux from Ventura on our fileservers. Things are going well with the SMB server on that platform. We chose Ubuntu for now. We had some Intel Core i7 Mac Minis setup with the migrated Ubuntu OS and external USB storage devices that are doing great. All user access controls and permissions work like it used to on the old Mac servers. The speed is amazing. This may not be our final solution, but has got us going. Our learning curve was a week and a week of user migration, transplanting over a million files and 4 TB of mirrored data. The front end user Ventura systems works great with the backend Ubuntu servers (so far).

We also had significant issues using MS Office 365 on Ventura, as client Word and Excel apps were creating cache folders that weren't removed by the application. We had to do a daily clean up of hundreds of cache folders. These have resolved for most users , but not all.

We are planning to test Linux on the M1 and M2 platforms as it offers far more flexibility for the back end.

Just updated to 13.1.2 and can confirm that SMB file share is NOT fixed, along with a number of other issues such as WindowServer crashing and caching issues.

Back to using Batchmod with no firewall on

I thought I should mention this in case someone else has this issue. The only Mac this is happening to me on is a M1 MBA that I changed the local hostname on in Settings - General - Sharing - Local hostname. This name matches what is in Settings - General - About, but I tried to change the Local hostname and since I did that File Sharing no longer works. I have several other Macs with Ventura and it works fine. Screen Sharing works for me, but not File Sharing no matter what I do.

I suspect I will have to wipe this drive and start over to fix it.

I have the same problem. Can not connect anymore between MacBook Pro 2020 , MacBook Pro 2022 (M1), MacStudio 2022 (M1) and a MacStudio 2023 (M1). I can see them, but not access them anymore. Also connecting with my apple ID is not possible anymore. all running OS 13.2.1. The problem started with OS 13.2, before that everything worked very well. Tried several workarounds (toglle on/off shared folders, recreated shared folders + I don't have custom folder icons). Nothing worked. Very annoying. Hope for a fix really soon, because now we can't work together anymore on shared videoprojects.

All -

Before you give up and go back to Monterey (a disruptive process) - Letting you know I have been engaged with support and feeding logs, videos and reports to Engineering on several occasions. When we have gotten to this step in the past it usually means they are tracking down the problem and working the issue.

So you might want to sit tight before wasting a lot of time reinstalling.

No guarantees tho - it's up to them.

I tried all the supposed "fixes" from deleting VolumeIcon files to turning off file sharing then rebooting and turning on file sharing and rebooting.

I finally went back to Monterey 12.6.3 and file sharing worked again but then other features stopped working like Apple Photos, Apple Music and Apple TV.

So then I updated from Monterey 12.6.3 back to Ventura and files sharing went wonky again.

I will say that it appears to be the "server" side that broke, because I kept my "client" Macs on Ventura throughout the process. They worked and saw all shared files when the server was running Monterey and then did not work when the server was running Ventura.

I actually think that the problem started with the update from 13.1.x to 13.2.1 but have no proof of this.

With all the problems that most of you are experiencing it seems that I should consider myself lucky as I have found work arounds while I impatiently wait for the the next update which hopefully will fix this thing.

I am using an Intel 2018 MacBook Pro as a file server on which multiple drives are mounted and a 2022 M1 MacBook Air to access the file server. Everything worked fine until Ventura.

Both are running the latest version of Ventura and have found the following to be true.

Screen Sharing works in both ways, MBPro > MBA and MBA > MBPro.

I can only file share from the MBPro > MBA so to transfer files I just connect MBA > MBPro via Screen Sharing and I can transfer files either direction.

The only thing I can't do is backup my MBA to the SparseBundle I have mounted on the MBPro. So I am temporarily backing up to a local drive until a solution is found.

So my problem is File Sharing M1 > Intel so I cannot backup over the network.

I am no genius but one of the issues seems related to what processors you are using.

Somehow I got distracted and upgraded to 13.2.1 and everything broke again! what a huge mistake.....thought I was upgrading something els.e....YIKES!

It did not work at all yesterday but this AM it started to work, but a few hours later, file sharing quit.....A hard restart of the server made it work, but for how long.....

Everyone, please submit your bug reports to Apple as mentioned by this poster below...squeaky wheel gets the grease.

There is a 13.3 Beta release out there but it does not appear to address this issue.....so bombard them folks!

tresinnoctem

I would strongly recommend that everyone who still has issues after installing 13.2.1 should make an official bug submission through Bug Reporting - Apple Developer They seem to be able to fix the problems if they get enough information to understand what is causing them.

I tried removing and restoring my home directory. The "Unknown user" did not appear for the shared folder. I think tried it for a folder in my home directory and "Unknown user" did appear with "Custom" permissions. I then found that I could successfully connect to and access "Macintosh HD" from a remote machine (running 13.2). Starting from there, I could go to Users and then my home directory, and from there everything works. Then I dismounted the remote "Macintosh HD" drive and tried again to connect directly to my home directory. As before, the directory appears, but clicking on any of the entries in the directory hangs the Finder and requires a reboot of the remote machine in order to continue.

I also found that removing extended attributes has solved (cross fingers) my sharing problems as well. I came about this the long way by trying all the other solutions which at best never worked or worked temporarily. My symptoms sounded like yours where only certain shares were causing problems.

Since my extended attribute removal all shares have behave consistently from all client devices that attached to the server.