How to modify samba config with raidiator 4.2.31

Yes, the added lines were in the global section. I didn't notice the warning that the file is auto-generated at first. When I rebooted, I got a popup in the web interface about an error, but the system rebooted ok. However, the additions were gone. I am guessing that the file takes /etc/default/config/etc/samba/smb.conf as its base, and adds whatever it needs before writing to /etc/samba/smb.conf. I would hesitant to modify the file you mentioned, I don't see how I would modify it, and it seems like it could screw up the whole system. But thanks for the suggestion.

You modify it in exactly the same way you would the smb.conf. (or create it if it's not already there). By declaration, it's an extension of smb.conf.  As best I can tell, it's a place where add-ons can put things that need to go in smb.conf without worrying about them disappearing.  You still need the [global} header for your entry.

Since addons.conf is included toward the bottom of smb.conf, anything in it generally overrides what's in smb.conf.

While it's on an OS6 system, here is an example from my NAS:

[global]
allow insecure wide links = yes
unix extensions = no
[ddclient]
  follow symlinks = yes
  wide links = yes
[hdsentinel]
  follow symlinks = yes
  wide links = yes

As you can see, I've made two changes to the global configuration and two to each of two shares.  I forget which SAMBA update changed the defaults and made me have to do this so I could link files in the apps folder to standard shares.

I checked on my RAIDiator 4.2.x virtual machine and this procedure is also applicable there.

Great, thanks, that is clear, I will try this the next chance I get. Hopefully I will make the upgrade to OS6 on this machine at some point in the not-too-distant future.

I'm somewhat confused. I tried your suggestion to add the min/max protocol lines to addons.conf, then removed the additions to addons.conf after I had initial troubles. After that I noticed that

[global]

min protocol = SMB2

max protocol = SMB2

are in the [global] section of /etc/samba/smb.conf. They are buried in the middle somewhere, not where I added them originally. And above where addons.conf is added.

I guess the bottom line is that I can now connect from my windows 10 clients that could not  connect before. I'm not 100% sure exactly why.

thanks

Great for you.  But not so great for the next person who asks.  I may play with it a bit on my VM.

Yeah, sorry I don't have better feedback. I can say for sure that raidiator 4.2.31 will run w/ SMB2 enabled. I think your suggestion to edit the samba addons.conf is the best way to accomplish the change, given that the user is explicitly warned not to edit /etc/samba/smb.conf.

Long story short my main issue getting things working came from the fact that, as I understand it, windows 10 does not allow to connect to shares w/ guest credentials using SMB2.