If the server is an AD-member you can setup a NFS-server and give
permissions to all the AD-users (as long as you have configured winbind
on the server) to your NFs-share. So when a user logs in to a
Linux-client with his AD-account and then mount the NFS-share he should
have the permissions you gave to him on the NFS-share. The Linux-client
must also be a AD-member. The user will get a kerberos-ticket during the
login process and so you can configure NFS using Kerberos, but this is a
different story ;-)
Am 16.01.24 um 17:00 schrieb Peter Carlson via samba:> Stefan,
>
> That's an excellent point, thanks for the reminder and the
> confirmation.? I had thought the same thing.? I dont think that will be
> a requirement, (at least not that I have been told).? Just multi
> protocol access to the same server.
>
> Peter
>
> On 1/16/24 07:24, Stefan Kania via samba wrote:
>> I don't know what you would like to do, but it is not a good idea
to
>> let SMB and NFS share the same directory, because of the file-locking.
>> NFS and SMB uses different file-locking. So if a user opens a file for
>> writing via SMB in that directory and another user open the same file
>> via NFS both could write. That's not what you want ;-)
>>
>> Am 15.01.24 um 17:51 schrieb Peter Carlson via samba:
>>> This is an off topic question
>>>
>>> I am trying to set up NFS4.2 server.? I already have samba fs,
samba
>>> ad, and windows, mac, linux clients working (all linux machines are
>>> running ubuntu 22.04).? Now I want to add a NFS server that also
uses
>>> AD for auth and for extended ACLs.? Can anyone recommend a good
guide
>>> on this?
>>>
>>> Peter
>>
>>