SMB broke in 13.2
After upgrading to 13.2 I can no longer share disks/file via SMB between my Macs. They can see windoze shares but no macOS. Way to go apple!
Mac Studio, macOS 13.1
After upgrading to 13.2 I can no longer share disks/file via SMB between my Macs. They can see windoze shares but no macOS. Way to go apple!
Mac Studio, macOS 13.1
the plot thickness, I created an external boot drive for the Mac Studio, with a 'scratch' volume. If I put an icon on the volume smb fails. If I remove it, and stop and restart file serving it works fine.
In my previous tests, I removed the icon from a drive I was trying to mount via SMB, but left the others as shared with their icons. After I am done with setting up the external boot drive and back on to the internal drive, I will remove all drives from sharing except one that will not have an icon and see if that works.
If that does "work" it will make things a bit harder for me as I have lots of external drives with icons representing what they are for. It has made my life easier, but I suppose I should be able to get along without the icons.
My tests of Mac client (Ventura 13.2.1) to Mac server (Ventura 13.2.1) shows that nothing has changed in the dysfunctional behaviour of SMB connections, regardless of the number of reboots. However, my tests of Mac client (Ventura any version) to Mac server (Ventura 13.1) show that SMB connections function without fault.
My workaround has been connecting the external thunderbolt drive to an old iMac running an old OS. Then others can connect to it but it is only running at TB2 speeds and not TB4 speeds which I get when connected to my Mac Studio.
Give them a call. Also, I just had them call me from their support app. Called in one minute and had a person on the phone within 2.
Why I fell back and reverted. Just too much of a pain. 13.1 just works. Haven’t had an issue since I put it back.
I also downgraded to 13.1 and now network shares are working great.
well that was a bust. The guy I spoke to was nice and he saw the problem. He then suggested I use TimeMachine to go back to 13.1. I told him, that I didn't think one can anymore but he assured me.
I booted recovery and selected a backup from Sunday that was 13.1. It then has me selected Install MacOS, but then goes right back to select which backup with a message to install MacOS again, then use Migration Assistant to get your files.
I started that, but it was obvious it was going to install 13.2.
It is true, even with a backup in TimeMachine we can no longer go backwards in a release.
I hope people are reporting this to Apple. I spoke to 2 support agents. The first one was very helpful and could see there was a problem and agreed with all my trouble shooting methods to try and resolve it. The second call which I got was most unhelpful as the guy just said it was probably a network (hardware) problem and there was nothing he could do about it.
I should mention that my network had not changed when then problem started and I even created a 2 station network using a different switch to replicate it.
Needless to say I think we should all report it formally to get some traction with Apple on this one.
Dave
select a folder to share on the server, and reboot the server to make sure it isn't wedged. Then select the share when pressing Control-k.
On my system between two Macs if I try and mount a volume the server freezes immediately. It does not freeze when sharing a folder.
My server was running 13.2.1
I have had the 13.2.x server work with windows for several hours, then it would stop. Between the Macs it never worked enough to mount the shared volume.
I will keep testing it to see if it does fail with time.
I have a machine still on 13.1, and it can’t access files off the 13.2 mac. This is most likely a bug on the machine hosting files, not the accessing mac.
more investigating shows that both Macs can mount shared volumes from windoze systems. No system either
Mac or windoze can mount the Mac volumes.
the problem still exists. have been in contact with apple support and have not gotten anywhere.
what I have done so far is:
I have tried turning off all sharing rebooting and turning it back on, no change.
Apple says, yeah it is a problem, too bad live with it, we have no method of elevating the problem to someone who can look at the logs and see what is going on.
So I have a $5K Mac Studio that is really not all that useful as the drives with my videos are on the iMac. Any ideas of what to investigate next?
I understand this problem is not entirely widespread and there are several alleged "fixes;" such as turning on/off filesharing with a reboot between each operation. Another such fix claims that the issue is caused by custom icons being used on the shared resource; however, none of these so-called solutions have proved helpful.
At this point, I can use CMD+K to direct to the sharing system and get a list of available shares - but am unable to map them, or even open them for viewing. I'm not sure what was changed between 13.1 and 13.2 but can we roll this thing back? puh-lease!
Still more testing and more questions with no answers yet. If I leave the icons on the drives, the SMB server on both Macs (iMac and Mac Studio) work fine from anywhere from 5 minutes to 12 hours. Then it just stops responding to requests.
After a reboot, I can mount both directions to the Macs, and the PCs. Then it just stops. If I reboot again, it might work, might be wedged. If it works it will eventually stop.
Still looking for a way to keep it going...
Someone in another thread suggested forcing the Firewall off on the server. Is that what this terminal command does? I am afraid to try it.
sudo /usr/libexec/ApplicationFirewall/socketfilterfw --unblockapp /usr/sbin/smbd
I purchased a 1 TB OWC Envoy Pro Elektron USB-C Portable NVMe SSD for $99 to boot 13.1 from and it is working okay. It does not have the blazing speed of the internal drive, but it is good enough until the smb server issues gets fixed.
It's a royal pain the in *** for sure. I just think we all need to fire off Feedback and make support calls about it. I did have a call with someone in Apple about 3 weeks ago and that went along the lines of "it works ok for me, so it must be your network and I can't help you with that".
Of course that was an exceptional response - I am normally very happy with the help from Apple. But it does highlight that there are probably some variables involved in the problem which are not obvious and we need to send as much data back to apple as possible.
SMB broke in 13.2