File Sharing Problem

[MikeDr206]

FWIW, I had this problem starting with Sonoma… the workaround is a pain, but at least there is one and it’s reliable. I’m not holding my breath that this will be fixed.

 

[Sciuriware]

I'm happy this thread exists - I noticed the problem after rebooting for an update and couldn't figure out why I could no longer connect. I was using a Linux box as a fileserver - but decided to move the drives to my Mac, so this didn't bite me until now.

I eventually realized that when shutting off the Firewall connections from clients could be made. I ended up finding an article on 6 colors about adding smbd to the firewall and making sure that it was not blocked using

/usr/libexec/ApplicationFirewall/socketfilterfw --listapps

But nothing helped. The tip on shutting off file sharing before rebooting is the only thing that really works(?) so far.

I'm wondering if it would be worth it to try something like Murus (murus) to workaround this? I've been meaning to try it out since the built-in Firewall app is not very good.

Seems crazy something like this gets by QA - and does not get fixed right away by one of the wealthiest companies in the world. I wonder when this bug started - I feel like I found some search results about this issue going back to last year...

I still wonder why this thread reads "RESOLVED".
;JOOP!

 

[CoastalOR]

I still wonder why this thread reads "RESOLVED".
;JOOP!

Good point. There has been additional posts of more people having the same File Sharing issues. I turned off the "RESOLVED" title prefix.

My posts 11 & 12 indicated the File Sharing started working for me on the silicon MBP when FileVault was off for me. There were also some additional problems I found that were mentioned in post 21 that might have contributed to the File Sharing problem, but I was not sure.

Both silicon MBPs have been fine Feb. 18, 2024. We have some trips planned for the Summer, so I decided to turn on FileVault for both silicon MBPs. I enabled FV for 1st MBP on Monday (4-15) and the File Sharing quit working properly with the same symptoms as mentioned in my post 1.

I enabled FV on the 2nd MBP on Tuesday (4-16) the File Sharing problem started on MBP 2.

Today I turned FV off for MBP 1, shut down, started the MBP, and File Sharing was still working correctly.

My conclusion, the File Sharing problem occurs with Sonoma macOS and FV On.

 

[ckeilah]

The actual SOLUTION is to dump Apple's POS samba implementation and install a working one. homebrew is the answer. If you haven't already, just look up how to install homebrew then install smbd then edit /etc/smb.conf, and enjoy rock solid filesharing. Then write nasty letters to Apple. ;-p

 

[MikeDr206]

The actual SOLUTION is to dump Apple's POS samba implementation and install a working one. homebrew is the answer. If you haven't already, just look up how to install homebrew then install smbd then edit /etc/smb.conf, and enjoy rock solid filesharing. Then write nasty letters to Apple. ;-p

I'm intrigued by this ... someone really should make this into an easy-to-install (i.e., download and double-click) package file and request donations. I'd give some cash.

Although, I don't want to have to turn off SIP or anything like that. And would want an option to uninstall later (e.g., when/if Apple ever gets it working).

 

[Sciuriware]

The actual SOLUTION is to dump Apple's POS samba implementation and install a working one. homebrew is the answer. If you haven't already, just look up how to install homebrew then install smbd then edit /etc/smb.conf, and enjoy rock solid filesharing. Then write nasty letters to Apple. ;-p

As I am a bit afraid of interim solutions like these, I would like to suggest NOT to delay a (nasty) letter to APPLE.
Besides, the problem, as far as I can see, concerns the loss of sharing rights when you reboot/restart only.
I made it a routine for all my machines to switch off sharing before reboot; at a crash (not happened yet),
you got to reboot twice to switch twice.

There seem to be more reboot effects than sharing loss alone:
sometimes rebooting switches on WIFI, which is unwanted in our place.
;JOOP!

 

[msephton]

The actual SOLUTION is to dump Apple's POS samba implementation and install a working one. homebrew is the answer. If you haven't already, just look up how to install homebrew then install smbd then edit /etc/smb.conf, and enjoy rock solid filesharing. Then write nasty letters to Apple. ;-p

Problems with this info:
1. there is no smbd formula in homebrew
2. there is no /etc/smb.conf

I've tried many ways to install an alternative samba but so far have not been successful.

If anybody has succeeded, please tell all.

 

[jmverreault]

I used to be able to smb connect to an old WD TV Live Hub before upgrading to Sonoma.

Now I get that error:
"There was a problem connecting to the server “WDTVLiveHub”.
"The server may not exist or it is unavailable at this time. Check the server name or IP address, check your network connection, and then try again."

I also tried using the WDTVLiveHub IP address with no luck.

Below are the results for dns-sd on the WD TV Live Hub
I assume TXTVersion=1.0.0 means that is support only Samba version 1 , correct ?

Q : Does anyone have a clue as to what I could do to make the Samba connection work ?

Thanks
JM

dns-sd -L WDTVLiveHub _smb._tcp


Lookup WDTVLiveHub._smb._tcp.local


DATE: ---Fri 30 Aug 2024---


23:19:16.691 ...STARTING...


23:19:16.788 WDTVLiveHub._smb._tcp.local. can be reached at WDTVLiveHub.local.:445 (interface 15)


TXTVersion=1.0.0 UDN=c4f5677b-0090-a9a3-64dd-7914283a537c Vendor=Western\ Digital\ Corporation manufacturer=Western\ Digital\ Corporation manufacturerURL=http://www.wdc.com modelDescription=Media\ Center modelName=WD\ TV\ Live\ Hub modelNumber=WDBABZ0010BBK modelURL=http://wdtvlivehub serialNumber=WXP1E51CNJP8

 

[Brian33]

I used to be able to smb connect to an old WD TV Live Hub before upgrading to Sonoma.

Now I get that error:
"There was a problem connecting to the server “WDTVLiveHub”.

Below are the results for dns-sd on the WD TV Live Hub
I assume TXTVersion=1.0.0 means that is support only Samba version 1 , correct ?

TXTVersion=1.0.0 UDN=c4f5677b-0090-a9a3-64dd-7914283a537c Vendor=Western\ Digital\ Corporation manufacturer=Western\ Digital\ Corporation manufacturerURL=http://www.wdc.com modelDescription=Media\ Center modelName=WD\ TV\ Live\ Hub modelNumber=WDBABZ0010BBK modelURL=http://wdtvlivehub serialNumber=WXP1E51CNJP8

Hello, & welcome to MacRumors!

I don't really know if that "TXTVersion=1.0.0" means that your WD TV Live Hub only supports SMB 1.0.0. Maybe it does mean that. When I run a dns-sd -L on my other (filesharing) Macs, it doesn't include any TXT info.

On Monterey (macOS 12.7) at least, the SMB client appears to support SMB 1.0 by default. I say that because man nsmb.conf shows the default values for the SMB client (not smbd!), and it says for "protocol_vers_map" the default value is "7" (see below), which is the bitmap value to enable support for SMB 1, and 2, and 3.

However, in my searching, I think I found someone's post that this value has changed for Sonoma, and that the default was now "6", or maybe "4". Frustratingly, I can't seem to find that page again.... But if it's true, "6" would enable only SMB 2 and SMB 3, while "4" would enable only SMB 3.

Anyway, I don't have a Sonoma machine at my disposal -- can you run man nsmb.conf and look at the value for protocol_vers_map in the section that looks like this:

Possible keywords may include: Keyword Section Default Comment A B C Values addr - + - DNS name or IP address of server (SNIP)... protocol_vers_map + - - 7 Bitmap of SMB Versions that are enabled (SNIP)...

I'm curious if it has changed from 7 to some other value in Sonoma. ??

IF it has changed to 6 or 4, that might be the issue! It appears that you can create a nsmb.conf specifying "7", and put that file in either ~/Library/Preferences/nsmb.conf (to affect your user account only) or in /etc/nsmb.conf (to set the value for all users).

I haven't tried this, but it looks like the file could be just the two lines:

[default] protocol_vers_map=7

 

[marstan]

I had this problem under Ventura not only with file sharing but also screen sharing. However, I recently installed Sonoma on both my M2 mini and M2 MBA and the problem has gone away. I can now restart with file/screen sharing on and I can see the files and screen shares upon reboot.

 

[jmverreault]

Hello, & welcome to MacRumors!

I don't really know if that "TXTVersion=1.0.0" means that your WD TV Live Hub only supports SMB 1.0.0. Maybe it does mean that. When I run a dns-sd -L on my other (filesharing) Macs, it doesn't include any TXT info.

On Monterey (macOS 12.7) at least, the SMB client appears to support SMB 1.0 by default. I say that because man nsmb.conf shows the default values for the SMB client (not smbd!), and it says for "protocol_vers_map" the default value is "7" (see below), which is the bitmap value to enable support for SMB 1, and 2, and 3.

However, in my searching, I think I found someone's post that this value has changed for Sonoma, and that the default was now "6", or maybe "4". Frustratingly, I can't seem to find that page again.... But if it's true, "6" would enable only SMB 2 and SMB 3, while "4" would enable only SMB 3.

Anyway, I don't have a Sonoma machine at my disposal -- can you run man nsmb.conf and look at the value for protocol_vers_map in the section that looks like this:

Possible keywords may include: Keyword Section Default Comment A B C Values addr - + - DNS name or IP address of server (SNIP)... protocol_vers_map + - - 7 Bitmap of SMB Versions that are enabled (SNIP)...

I'm curious if it has changed from 7 to some other value in Sonoma. ??

IF it has changed to 6 or 4, that might be the issue! It appears that you can create a nsmb.conf specifying "7", and put that file in either ~/Library/Preferences/nsmb.conf (to affect your user account only) or in /etc/nsmb.conf (to set the value for all users).

I haven't tried this, but it looks like the file could be just the two lines:

[default] protocol_vers_map=7

The man nsmb.conf on Sonoma reports :

I notice that in Sonoma A B C = + + - for protocol_vers_map where as your's was + - -
I am not sure I understand what it means.


JM

 

[Brian33]

I notice that in Sonoma A B C = + + - for protocol_vers_map where as your's was + - -

That part's not too important -- it just specifies which sections of the config file that keyword is allowed to appear in.

The critical part is the default value of 7 -- which we now know is the same for Sonoma and Monterey. The 7 means that, by default, the SMB client does support SMB protocol version 1 (as well as 2 and 3).

So, your issue isn't as simple as the client refusing to use SMB 1 with your "WD TV Live Hub" device. (Of course there might be a bug introduced in Sonoma.)

There may be something unusual about your WD device. In retrospect, it would have been best to post this issue in a separate (new) thread, because it's unrelated to the original poster's issue. A new thread with "WD TV Live Hub" in the subject line might get views from other users of the device.