SMB File Sharing not working in Ventura

Good to hear this worked for you. I am pretty Mac literate, but do not know what "removing extended attributes" means. If you or someone else could outline the precise steps to "remove extended attributes" I would greatly appreciate it. Thanks!

ChatGPT says

"

Extended attributes are additional metadata that can be associated with files on a Mac filesystem, such as the creation date, author, and permissions. These attributes can be useful for organizing and managing files, but they can also take up additional storage space.

If extended attributes are removed from a file or a set of files on a Mac filesystem, it means that the additional metadata associated with those files is deleted. This can be done using the xattr command in the Terminal or by using a third-party utility.

Removing extended attributes can help to free up storage space on a Mac filesystem, particularly if the attributes are associated with large files. However, it can also have unintended consequences, such as affecting the functionality of certain applications that rely on those attributes. Therefore, it is generally recommended to proceed with caution when removing extended attributes and to back up important files beforehand."

ksaro1 wrote:

ChatGPT says

"

Extended attributes are additional metadata that can be associated with files on a Mac filesystem, such as the creation date, author, and permissions. These attributes can be useful for organizing and managing files, but they can also take up additional storage space.

ChatGPT is confused.

Creation date, while not Unix standard, is macOS file system standard metadata, and is not an extended attribute.

Author, is the owner, and has been standard part of Unix since creation of Unix over 50 years ago.

Permissions, as in User, Group, Other, has been part of Unix since its inception. Access Control Lists (ACLs) are a bit newer, but are still considered part of the standard Unix permissions and are not extended.

There are other attributes that are extended, and are manulipated with the xattr command. Just not the ones listed by ChatGPT.

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......

I did try user of the attribute command detailed either earlier in this thread or one of the parallel ones. I got either command not recognised errors using the first commands or no extended attribute found error when using a global attr -c . The OP referred to custom icons which I have never knowingly created.

just wish I could downgrade using Time Machine but even that has been blocked in Ventura. As has the ability to access and delete old backups, so Time Machine is now broken for me as backup disc is full and I can only reuse it by wiping all backups from current and older iMac. Not great!

Now that you mention this... the ability to easily restore and downgrade in an emergency... ought to be high on a list of required features to justify use in a commercial setting. Well... for anyone who values network uptime. For me it's been a serious problem.

We recently reverted to a sneakernet moving files around the studio on external drives :-( Instead of collaborating via file sharing. Now there are assets all over the place that need to be reconciled with the server WHEN this debacle is finally over. I know that day will come for sure because either Apple will fix it... or I'll get around to commissioning a server on another OS.

Indeed. When it arrived TM was the simplest and easiest backup solution with access and manipulability both within and independently of the app. Having just discovered the new locks, I don’t even know if the backups of my old parked iMac are even restorable. And 18TB drive is full and I can’t remove unneeded extra backups. I am not buying another drive at that cost - it’s just a home setup. I am having to airdrop or email files to myself or resort to USB sticks and a lot of stairway steps. Agree with you - it’s solved or I return to a PC network.

Thank you, this worked for me as well. I had tried everything in your post *except* removing the previously shared folders from the list in Settings as part of the process. I went to the list of shared folders in "File Sharing" (click the little info circle to open a dialogue that shows the list.) I removed all folders from the list, turned off file sharing, unchecked "shared folder" in all Finder Get Info boxes, and rebooted. After the reboot, the folders are shared normally. Time Machine backups now work normally. Sharing has survived multiple reboots over two days to be sure, so I am happy. 

abromber

Thank you, this worked for me as well. I had tried everything in your post *except* removing the previously shared folders from the list in Settings as part of the process. I went to the list of shared folders in "File Sharing" (click the little info circle to open a dialogue that shows the list.) I removed all folders from the list, turned off file sharing, unchecked "shared folder" in all Finder Get Info boxes, and rebooted. After the reboot, the folders are shared normally. Time Machine backups now work normally. Sharing has survived multiple reboots over two days to be sure, so I am happy. 

abromber

I also received the notification from Apple as follows: As a result of your feedback, there are changes in the latest update, build 22E5236f, that have resolved this issue.

You can see the software build your device is running and check for the latest update by clicking on the Apple logo in the upper left hand corner > About This Mac. If the build is not visible, click on the macOS version, e.g. 10.15.x, to reveal it.

If this issue is not resolved for you in the 22E5236f build, please file a new feedback report. 

Feedback ID FB11992033, File Sharing issue

Hopefully the update will be released soon.

Apple just notified me too that the issue related to my ticket (FB11991908 - extended attributes with SMB sharing) is expected to be fixed in last macOS beta (22E5236f).

I can't test it on my Mac Mini, but I will try to reproduce on a VM.

If someone can test more easily in the mean time, feel free to comment here.

Alas, as ctphoto1 predicted, it stopped working again for me after only a few hours :-(. I may try upgrading my client mac to Ventura as that was already on my "to do" list - even though, all evidence suggests it's a server-side issue.

Accuracy of terms is important. There are no differences between the OS used on the clients or the machines we choose to be the server with the exception of the sharing mounts. The same SMB protocol is present on both (Ventura OS) machines and provides sharing and access control.

Second, based on our observation the Microsoft Office ".SB" temp files are also caused by the same protocol (SMB) issue on the client machines with Ventura, even using a non-Mac OS server platform. This has been reported to Apple as well.

Hence, SMB protocol implementation on Ventura is the issue based on our limited experimentation.

Thanks. Yes, in my case I meant "the Mac that is acting as the server and sharing folders" is Ventura, and "the Mac that is acting as a client and trying to access the folders over the LAN" is not (it's still Big Sur). From what you are saying, upgrading that machine won't help (as I suspected).

Without generalizing and based only on our limited experience and experiments in our own network environment, the Mac units used as a client on the network without Ventura (mostly Monterey) do not exhibit any SMB related anomalies. The units (M1 and Intel) upgraded to Ventura have this issue even when connected to a non Mac-OS fileserver. We even downgraded one M1 mac from Ventura to Monterey as the user was tired of deleting the extra ".SB" directories generated as a result of saving Office files on the fileserver.