Ventura 13.2 File Sharing broken

Sorry to hear @sofalounge,

I can tell you it is still up an running sharing in ave. 2 TB of data per day.

Also via VPN and screensharing = no problem.

I have two shares:

• 1 x external 2TB NVMe (whole disk shared)
• 1 x Folder on a second external disk 2TB NVMe

I only removed one icon (the one of the disk) + off-on-restart file sharing + Cifs on client site.

That's all. The mac mini runs standard Ventura 13.2 no extras, tweaks etc. Good for me

Br

-T

Found another "Fix"

at reddit I found another link for a "Fix" or "Two".

FIX 1: Let OS Auto Switch between SMB 2 & 3

FIX 2: Force Switch to SMB 3

Check it out... didn't try it cause my system is already "stable"

https://www.droidwin.com/smb-file-share-not-working-in-macos-ventura-fix/

Br

-T

@cactusgoeswest

your are absolutely right and we all should be aware to do so.

But meanwhile we need feasible solutions, workarounds etc.

Specially small business companies who use standard file sharing for daily business cannot wait.

First two weeks we shared files via mail and sticks it was horrible ...

Finally I set up an old mac with Monterey ... beside the workaround that works for me. Mentioned it above.

Cross your 🫰🏼to get a fix of Apple very soon

Br

-T

This is interesting. I have always gone through Finder to connect to a server. Going through Safari opens an authentification dialogue box and offers a choice of which folder to access. I would be interested to know if it also permits TM (Time Machine) backup shares. I have already downgraded our server to Ventura 13.1, so I am not in a position to test it. I presume that a reboot on a server running Ventura 13.2 would require another set of authentifications.

If this is the case, then the problem may lie with authentifications being lost by the server for known clients which, bizarrely, was not a problem under Ventura 13.1. So it is not so much a permissions issues, as an authentification issue.

I confirm the bad news. I upgraded one iMac to 13.2.1 and defined on it a test folder in sharing. I gave the folder a custom icon. It was impossible to connect. Behaviour seems unchanged, although this is not a thorough test. Nonetheless, it is probable that nothing has been resolved regarding broken SMB networking. As they say, "if you break it, you own it". Apple engineers own this.

Suggestion: For those trying to add the custom icon, can you not do that and see if it still does not work. This will take one factor out of the issue to simplify the testing procedure.

I do not use a custom icon and continue to have the issue.

Funny, made a post about a possible solution (try the next release .3) and asked if this helps. The post was deleted a short time after. Would be great if support, replays and solutions would be with the same speed...

Seems to me you need to turn on "remote session" ‒ I am not certain what the exact macOS term is in English. The session share opens SSH on port 22. If I understand correctly, SFTP is a derivative of SSH. Usually, one connects by invoking ssh://123.123.123.123 in Terminal. Terminal may also be launched by attempting an SSH connection in Finder. However, if you use "screen sharing", i.e. VNC protocol, the screen sharing option will be déactivated if the remote session option is checked.

For me, it broke on the 13.2.1 security update. I called apple a couple of days ago to report the problem. After doing exhaustive testing, the technical rep. said she'd report it to the developers. I agree we need to stop talking about custom icons. I have none. It also appears this is occurring on Mac Mini M1's? Mine was one of the very first off the line and had bluetooth problems out of the box that one of the early updates corrected. Oddly enough, on this mini, I have never been able to share its screen from another computer. I think there's something up with these M1 mini's. I get the failure to connect error when before, through the finder, the shared volumes would appear after about a second of loading.

Mac Mini M1 16GB/500GB

Sorry to hear about your troubles, but I am glad you conversed with Apple techies. I did the same about a month ago, but left it there. I am certain that Apple is more than aware of the situation. They need to deal with it on 2 levels : internally with their engineers to try to find a solution; externally with users like us who are very experienced regarding technology. As time passes, Apple multiplies the layers of security on macOS. That this needs to be done is not Apple's fault, but it is a consequence of the Far West environment that now dominates the internet. The unexpected problems with SMB are certainly the result of an added layer of security. It will take some time to sort it out.

Small update:

On the two MBPs 13" and 14" I got some kind of sharing back by really copying the files to a new folder by the same name and share that. Very strange workaround that failed in the office but worked with the Notebooks, don't ask me why. SMB3 is the protocol it seems to use according to terminal – and incredibly slow, in the 200-kb/s-range on a WLAN that can easily handle > 50MB/s. I've yet to get above 7MB/s here.

Frankly, stuff like networking and the core filesystem should not break down in a .X-update. Not even in a jump in major versions once a year but sure as heck not with small-ish updates. I would like to be able to trust those to work.

[Edited by Moderator]

To be honest, I did have a hiccough at one point. But shutting down and restarting everything corrected the issue. Sometimes, I have noticed, it takes a few restarts for the system to become stable.

https://www.reddit.com/r/MacOS/comments/10k7070/ventura_132_cannot_connect_with_smb/?utm_source=share&utm_medium=web2x&context=3

I should say that my previous router was starting to run a bit flakey, although it was a wifi-6. Nonetheless, I decided to replace it with a wifi-6E.

The sharing was broken (stopped) after a short time, like the other ideas.

Our solution is still running an old Mac with an older version on it. Everything else have we tried, without success.