SMB File Sharing not working in Ventura

Same problem here. M1Ultra Studio and all the different iMacs/iMacPros/Studios in the office can't access a 48 TB archive we work with that is DAS to my Studio via TB anymore. Way to go. Turning off Filesharing, rebooting and turning it back on works for a couple of hours and then we're back to computers crashing as soon as they try to access folders in the Archive. SMB and directly going to folders via network do not work. No custom icons that I know of (maybe the green/red etc flags also are metadata...? But we actively use them for the status of files and have quite a lot of these flags...), no firewall. Backblaze installed (newest version), but their support does not seem to be aware of any problem. Same problem with two M1 MacBooks, even in SafeMode. Definitely seems to be a massive SNAFU in 13.2. Really getting Windows-Vista-vibes here, where you were afraid to update (and thus changed a whole system to Apple in the end). Let's hope for a superquick patch, as this is not an annoyance, this is really keeping us from doing our work.

More information and more anguish.

A few pages back I reported that despite macOS clients not having a connection for more than a few seconds, that my Apple TV the Infuse app, which plays content using a standard SMB connection with a host mac, was playing without issue for more than a week since no mac could connect.

I thought the bug could be in the client, and that for some reason the Apple TV as a client was fine.

Well today when I was looking at Sharing permissions, I noticed that the volume that the Apple TV connects to has some how unchecked "Shared" and didnt even appear in the shared items list. Yet it maintained a connection and was streaming to the shared volume all week.

Stupidly I check the 'Shared' checkbox on, it appeared in the shared list as it should....

But now the Apple TV will not maintain a file sharing connection to the mac server and I cannot play any of my movie or music files. It is broken now as well.

But why did it connect and play perfectly as it did before the upgrade, until I checked the shared checkbox on??? Its almost like it kept working settings from before I upgraded the macOS and used those for the last week flawlessly, but now that I have made a change, the stored settings have been updated/corrupted to the new broken configuration that the macs have suffered from all week.

I felt a sense of deja vu, as I remembered that the serving and client Macs I updated a week ago did actually work fine for a couple of hours before I went to bed, then the next day stopped working. But I haven't been able to connect for more than a few seconds since. Were the Macs actually working off remembered settings from before the upgrade, like the Apple TV? until something forced them to retrieve new corrupt settings installed by the OS update?

And for the record, no custom items anywhere and no Firewall ever as I used a router and don't directly connect to the internet.

Doubly upset.

I have 8 Macs on my network including a M1 Mini as the server and a M1 MBA. This bug only affects my M1 MBA and it was previously working. It stopped working and it acts as if a preference file got corrupted or something. When I try to browse files on the M1 MBA from another Mac, I get the "loading" sign in Finder for a second, then it disappears and nothing happens.

I reinstalled Ventura on top of what was already there but that did not fix the problem. I will likely have to wipe the drive and start over.

In addition to this issue, I have been having an issue writing files to the server since Ventura. I will copy files over to the server and it will randomly throw a beach ball. When that happens, the only way to move forward is to reboot the server because it seems to keep a hold of the files it was trying to copy even though I initiated the copy from another machine. It's weird, but it seems related to the file sharing issue because they both showed up with Ventura.

I have the identical problem attempting to use File Sharing in Ventura between my Mac Pro and Mac Book Pro. Turning off FS, rebooting, then turning FS ON sort of fixes the problem, but, it is spotty. I spent an hour on the phone with Apple tech support last week. I sent them logs from my Macs for their engineers to review and was told I should hear back within 24-48 hours. That was six days ago. I am always slow to upgrade the OSX but apparently this time I was not slow enough. None of the three Apple techs with whom I spoke mentioned this as an existing problem.

Agreed totally the Apple needs to fix this....I updated my last post......I can walk you through this if youre willing to give it a shot.....Yes, I know Apple should fix it, but nothing is coming forth at the moment, so if you need to share files right now, give it a try

Just to clarify, using Batchmod isn't the same thing as simply giving users full access on server settings. There's something that happens to the enclosed items when using Batchmod that solves the permissions issue.

Unfortunately 13.2.1 does not fix anything related to SMB file sharing. Also, nowhere in the patch notes does it say anything about Apple addressing SMB file sharing with this update. I suspect that this will be a high priority for 13.2.2 considering the vast amount of attention this issue is getting online (reddit, apple community, articles, etc). I'm not a computer engineer, but it certainly seems like these guys have gotten to the root of the issue:

https://www.truenas.com/community/threads/smb-permission-issues-on-macos-ventura.104067/

I can confirm that Apple has changed SOMETHING in 13.2.1 regarding file sharing. I tried 2 virtual machines, one as a server, one as a client.

Fresh installation!

Sometimes it can connect, sometimes the Finder hangs. Sometimes the popup with the list of the shared folders stays forever, sometimes it's being closed and a forever-waiting Finder progress bar comes up. Sometimes it shows the mounted folder on the desktop sometimes, it doesn't. But if it connects, it hangs a few seconds later.

In my opinion, it get's worse with every update. And again: I'm talking about a fresh and clean installation.

Let's hope that Apple doesn't choose to "fix" the issue finally by removing file sharing capabilities in the next major macOS release... :-(

Erratic hangs issue on connection for me as well on 13.2.1, but not with all my share points.

None of the suggested workaround work.

I noticed some logs like "smbd socket_look: rdsz 0 ---> EPIPE". Not sure if related in any way.

I opened the feedback ticket FB11991908.

We have switched the file servers to Linux Ubuntu. We examined TrueNas, but we’re far more comfortable with the Linux platform. We even used a couple of our Intel based Mac Minis to install Linux.

As it is merely a server, it doesn't really matter what hardware you use.

I don't know if it is possible to install Samba (which you are likely using on Linux) on macOS and force it to use that instead of Apple's implementation, but it is likely more difficult than just setting up a Linux server. If you don't need to use the server as a Mac, then there is no reason to do so.

Since setting up a NAS all of my file sharing issues are resolved. For whatever reason, Ventura, as it is now, is not up to the task and like many people I needed a solution I could implement immediately because I could not just stop working to wait for Apple.

This issue seems to go back to November of 2022 so hopefully Apple is close to a solution but I see no indication there are anywhere near a fix. It's been over a month since a senior advisor told me he was required to check with engineering three times a day on my case and communicate to me any updates - I never heard from that advisor again.

I tried this (Macbook Air M1 won't connect to iMac upstairs, nor will a Win10 PC next to it) and it worked immediately, as did the Turn off File Sharing, reboot, turn back on. Unfortunately, the effects lasted an hour or two before reverting - I'm assuming the Air going onto standby triggers the problem. I also tried the same on the Air to get the iMac to see it - that also worked for around an hour. Neither the original file share off/on nor your triple switch change was repeatable on a subsequent occasion.

Made a new folder called Groups 5 in the shared file and copied a rather large folder with many files over to it. Ran BatChmod a 3rd party app as mentioned earlier in this discussion and removed all Xattr's, changed ownership to me, gave it administration rights for R/W/D and gave everyone access to R/W/D.

Running an Intel MacBook Pro to a M1 mini (file server) and the MB would not see Groups 5. Ran Clear ACL's and still no luck......

Just to let others know - glad to say this is fixed for our insanely complex setup (Mac Studio with two separate ethernet networks one of which shares RAIDs via Softraid with custom icons and CrushFTP for client cloud access.) We didn’t do incremental updates for obvious reasons so I’m extremely grateful for everyone’s continued updates here. Finally updated all macs on the network this morning and see stable success on ethernet and wifi. Haven’t restarted since again for good reasons so I hope this stays fixed permanently. Thanks again.

Yeah, Logged in as an administrator, I can have access to other users shared files so file sharing works. It’s the link between SMBD and File Sharing that‘s broken. I spoke with a senior advisor and he said Apple does not support the “Connect to server” option in the iOS Files App, which I’m not sure is correct.

I actually did a reinstall of Ventura MacOS through the recovery mode before updating to Sonoma and it do not correct the situation. It sure would be nice to know specifically what corrects this problem before taking the sledgehammer approach, more than most want to try. I have some confidence in Time Machine but have not had to do a complete restore of all data. I might try a re-install of Sonoma first.

And what syntax are you using to set up the server connection in Files - server name or IP address? Or do both connect for you?