Dear all, First of all, thanks for your suggestions and help, I really appreciate that. Finally the issue was just in the user mapping rule:The original *\* &= * [] The definitive one AD_Domain_Name\* &= * [] It seems that the "general" first rule was causing the annoying "authentication" behavior. Once replaced, the user tokens from both sides looked similar (although I was told that it wasn't necessary) I hope this helps other people. Regards.
Dear community,   We have configured an access zone with Windows AD and NIS authentication providers, both of them were set with "Lookup Normalize" users and groups to Yes.   created a default mapping rule "*\* &= * []" to join users from two "worlds", all of them have same user naming format, and the mapping token looks fine when "isi auth mapping token" is run.   We created a CIFS share with everyone full access and granted an AD group "GroupA" with "Modify" permissions at file system level. Then this folder was exported by NFSv3, and set "map lookup id" to Yes.   When a member of GroupA tries to access the exported NFS for first time, it receives "access denied". The only way to get access for this user is by accessing through CIFS for first time and remounting the export from the linux side.   CIFS access always works as expected.    NFS access works only if the user have accessed through CIFS at least one time.   It feels like the access token is created only when user access by CIFS, and it enables the access on remaining protocols, in this case NFSv3.   Does it has any sense? There is something that we can check or some additional configuration considerations to take into account?    We look forward to hearing from your valuable experience. Kind regards, Ariel.
OneFS 8.2.1 - Multiprotocol User must access by CIFS first to get access in NFS 
export