SMB File Sharing not working in Ventura

I have tried this suggested fix multiple times, with no luck

What, exactly, did you try? Did you find the extended attribute or custom icon and remove it?

Or, did you not have any of those?

There are some that have problems caused by the FinderInfo extended attribute. There is some other problem. (or problems) that nobody has figured out. It appears you have that problem, along with many others.

Thanks for the response. I might not have done this correctly. I simply Pasted the code you shared in Terminal, followed by dragging the icon for the shared folder/volume into Terminal. I did this for several volumes that I need to share. Sometimes I can access & share the boot drive on the host Mac, and sometimes even open the Desktop on same. But I never can access the various other internal hard drives & external drives on the host Mac. I am pretty Mac literate, but not at the level of this forum. I don't know exactly what the extended attribute or custom icon might be (?).

If you didn’t find the extended attribute, then it isn’t your problem. It is a deeper, underlying problem.

The act of looking for it doesn’t fix the problem. If it was there, you would try removing it.

I had and still have the same problem. Turning off file sharing and rebooting might work one time, but then I have to do it again. The person at Apple I spoke to did not have any other solution. Apple need to fix this.

This is the conclusion I reached as well that I could not wait any longer for Apple to figure this out. Initially I built NAS devices as test cases using some older computers using TrueNas and UnRaid - they worked perfectly - so I purchased a Synology box to have a more modern platform than my test case NASes, also the off the shelf NAS devices use less electricity than the big old servers I used for test cases.

I dunno how Apple managed to break network file sharing but they should be ashamed of themselves, this is kindergarten level stuff that any operating system has to be able to do. How Ventura ever got out of testing with this flaw is shameful.

I wholeheartedly agree with you. Some people would say that all we had to do is revert back to the previous OS. In some cases it is not that easy. I'm now happy again as I can access my NAS and USB drives.

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. For us it has been accumulative issues, such as abandonment of email and LDAP servers. Then inability to reconfigure Mac Mini hardware in the 2018 onward gave us pause, but we were still loyal then this issue put us and our content at risk.

It has been rather difficult decision after 17 years to make a major back office reform. Our front office will still remain mostly MacBook and MacBookPro.

Hope this is not interpreted as Apple bashing, we needed a realistic and immediate business solution.

Yes, we have setup a SAMBA server controlling a QNAP multi-drive system with some mirroring built in. The SAMBA server setup was rather easy. We set up user folders and drive access controls and passwords duplicating what we had on the Mac OS.

The Samba server could also be set up to function as a Domain Controller (DC) as well as OpenLDAP backend.

In terms of the hardware, you are absolutely right, we could have used any other hardware, but we had some Mac Mini 2012 (i5) and 2014 (i7) that were available. Impressive speed running Ubuntu on them.

We are also retiring our old Apple email server, replacing with a brand name running on Ubuntu.

Sad to say the back-end will be transitioned completely to Linux.

I would love to downgrade back to Monterey since there seems to be no fix for this issue any time soon. Apple Support told me I needed a Time Machine backup to downgrade. I don't use Time Machine for backups, but rather Chronosync, which I love. Is there any way to downgrade back to Monterey without a Time Machine backup? Thanks.

Just a thought for Apple to consider: Perhaps Apple's update supply chain got hacked like the Colonial Pipeline attack almost two years ago. If so, the Ventura 13.2.1 we're all having trouble with might be subtly different from the one that Apple has in Cupertino. I don't want to sound like a conspiracy theorist, but the Colonial Pipeline attack was real, and it would certainly cause Apple fits trying to track down the problems users are having if such a thing had happened.

I personally am disabling file sharing until this issue gets resolved.

Disabling the File Sharing is not an option for me as I need to share files across our network of Macs. Right now I am using a small portable hard drive to physically move digital image files (large) from one Mac to another. How frustrating!

The restarting suggestion did not help. Many other comments are good and relevant, but obviously, they do not solve my issue of accessing files on my Ventura 13.2.1 mac-mini from other macs (which have a variety of OS software).

Just an update - I have had several calls from Eng asking for more info and seeming to be converging on the issue. They are asking intelligent questions, referring to our workarounds, trying to understand exactly what is happening.

While I wish I could say a fix is eminent, these are good signs.

We can only hope .... we have had Macs in our business since 1986 and thought there have been some issues I can never recall such a serious problem that lasted so long. If I was PC-literate I might be considering a switch.

swixo and all,

Before doing what you said, I had on and off again connections. A restart sometimes would work.

Did your suggestions and I have had 5 different Apple laptops and Mac minis connect without any hiccups. I did have remote Login already enable but none of the boxes under it checked. I have not unchecked either Remote Login or Management. It would be interesting to see if unchecking all boxes and restarting cause problems again....I think your on to something swixo

This further refines what the problem is.....hopefully we can get this to engineering.