[Samba] Protocol restrictions

[Peter Milesson]

On 25.09.2024 11:38, Anders Östling via samba wrote:
> Agreed, I will keep the NT1 share on a separate VM and create a new
> one for the other services. Air-gapping will be difficult though, but
> I will check what can be done.
> Thanks
>
> On Wed, Sep 25, 2024 at 11:20 AM Rowland Penny via samba
> <samba at lists.samba.org> wrote:
>> On Wed, 25 Sep 2024 11:08:24 +0200
>> Anders Östling via samba<samba at lists.samba.org> wrote:
>>
>>> Is it possible to have the "min client protocol" statements per share,
>>> or must they be global?
>> I take you meant 'client min protocol', that is a global setting and
>> cannot be per share.
>>
>>> I am asking since I have the NT1 limit on a specific Samba server with
>>> a share for an industrial robot with an ancient Linux/Samba
>>> implementation , but there are other shares on the same server that
>>> should be better protected with SMB3.
>> If you have to use NT1, then in my opinion it should be a separate
>> server just for that use, 'airgapped' for preference.
>>
>> Rowland
>>
>>
>>
Hi folks,

I have got a similar setup with NC-machines (still using Windows NT4). 
The samba server lives in a small and cheap mini-PC, as the main servers 
are in another location. In case of connection failure to the main 
servers, the local samba server continues to serve the machine group. 
The machine group network is completely isolated with its own router 
with a firewall (MikroTik), and access to the local samba server is 
limited to a couple of IP-addresses in the main production network.

Best regards,

Peter