search for: low_range_idb

Displaying 3 results from an estimated 3 matches for "low_range_idb".

Did you mean: low_range_id
2024 Jan 24
1
Share access permission errors after upgrade from 4.12.14
.... This is normally 1000. The highest ID should be set to 2147483647. Any range smaller than 0 - 2147483647 will filter some SIDs. As we can normally only start with 1000, we are not able to map 1000 SIDs. This already can lead to issues. The smaller the range the less SIDs can ID = RID - BASE_RID + LOW_RANGE_IDbe mapped. So, it looks like any users or groups that have a RID less than 10000 are ignored and the '4000000000' high number is pointless. This is on top of the fact that the idmap_hash backend should not be used. A better method would be to use the idmap_rid backend: idmap config * :...
2024 Jan 24
1
Share access permission errors after upgrade from 4.12.14
On Wednesday, 24 January 2024 at 10:51, Rowland Penny via samba <samba at lists.samba.org> wrote: > I rearranged the smb.conf above and added comments: > > [global] > netbios name = Tower > server string = Media server > security = USER > workgroup = WORKGROUP > bind interfaces only = yes > interfaces = 192.168.66.10/24 127.0.0.1 > > # we don't do
2024 Jan 25
1
Share access permission errors after upgrade from 4.12.14
...000. The highest ID should be set to 2147483647. > Any range smaller than 0 - 2147483647 will filter some SIDs. As we can > normally only start with 1000, we are not able to map 1000 SIDs. This > already can lead to issues. The smaller the range the less SIDs can ID > = RID - BASE_RID + LOW_RANGE_IDbe mapped. > > So, it looks like any users or groups that have a RID less than 10000 are ignored and the '4000000000' high number is pointless. This is on top of the fact that the idmap_hash backend should not be used. > > A better method would be to use the idmap_rid backend: &gt...