Forum Discussion

Apprentice

May 25, 2017

Solved

Change Samba idmap with AD

I have a nas that was installed long ago with a firmware pre 6.5 and then upgraded to the last, with this nas the idmap with ad is different that one started with a recent firmware.

It's possible change the way idmap work to the same automatic behaviour like in the new firmware, having in smb.conf from idmap config * : backend = tdb to idmap config * : backend = rid?

smb.conf is autogenerated so it cannon be modifiied

Thanks

File Sharing

cs_giuseppe
Jun 01, 2017
Hi,

SOLVED !!!

here the step

Switch from AD to Local users.
NEW - Disabled samba in each share
Wipe the permissions under File access tab / reset of each shares settings section.
Edit /etc/samba/smb.conf to replace tdb by: rid
Execute: net cache flush
NEW - Reboot
Join AD with "trusted domain" unchecked.
After these steps now idmap use rid.

Thank for all suggestions

9 Replies

Replies have been turned off for this discussion

jak0lantash
Mentor
May 25, 2017
I would:
Switch from AD to Local users.
Wipe the permissions under File access tab / reset of each shares settings section.
Join AD with "trusted domain" unchecked.
Check smb.conf that it's using rid instead of tdb.
Reapply the permissions: https://kb.netgear.com/7066/ReadyNAS-OS-6-Setting-Active-Directory-folder-permissions

If smb.conf still uses tdb, I can try to confirm how to manually change it.
- cs_giuseppe
  Apprentice
  May 27, 2017
  Hi jak0lantash,
  
  thank for the suggestion
  
  made:
  
  Switch from AD to Local users - done
  Set file owner to guest and group owner to guest - done
  Wipe the permissions under File access tab / reset of each shares settings section. - done
  Deleted the nas account on domain - done
  Join AD with "trusted domain" unchecked. - done
  Check smb.conf that it's using rid instead of tdb. - NO, still idmap config * : backend = tdb
  
  I
  - jak0lantash
    Mentor
    May 27, 2017
    cs_giuseppe wrote:
    Check smb.conf that it's using rid instead of tdb. - NO, still idmap config * : backend = tdb
    I wish this would behave differently...
    
    Try to edit smb.conf to replace tdb by: rid
    Then: net cache flush
    Then start the steps again. If you get to rid, the mapping table should be calculated consistently across both devices.