John Lewis
2015-Jan-13 14:06 UTC
[Samba] Is there any problem that can arise from remapping gidNumber?
On 01/13/2015 06:35 AM, Rowland Penny wrote:> On 13/01/15 11:33, John Lewis wrote: >> This morning I remapped gidNumber from primaryGroupID to gidNumber. I >> did that because I could not change the integer in primaryGroupID wit >> ldbedt as root. >> >> I mapped to to a new attribute called gidNumber which has no specific >> meaning in samba. Is there any potential problems that can arise from >> doing that. Is there a better way to fix that problem? >> > > Hmm, definitely going to need more info here, gidNumber has a specific > meaning to samba, depending on how you set up samba. > > Rowland >I took the defaults except for rfc2307 which I enabled. I am running Samba Version 4.1.11-Debian.
Rowland Penny
2015-Jan-13 14:23 UTC
[Samba] Is there any problem that can arise from remapping gidNumber?
On 13/01/15 14:06, John Lewis wrote:> On 01/13/2015 06:35 AM, Rowland Penny wrote: >> On 13/01/15 11:33, John Lewis wrote: >>> This morning I remapped gidNumber from primaryGroupID to gidNumber. I >>> did that because I could not change the integer in primaryGroupID wit >>> ldbedt as root. >>> >>> I mapped to to a new attribute called gidNumber which has no specific >>> meaning in samba. Is there any potential problems that can arise from >>> doing that. Is there a better way to fix that problem? >>> >> Hmm, definitely going to need more info here, gidNumber has a specific >> meaning to samba, depending on how you set up samba. >> >> Rowland >> > I took the defaults except for rfc2307 which I enabled. I am running > Samba Version 4.1.11-Debian.Yes, but what as ?? an AD DC or in classic mode i.e. just like samba3 Might be best if you post your smb.conf (sanitised ) Rowland
John Lewis
2015-Jan-13 15:11 UTC
[Samba] Is there any problem that can arise from remapping gidNumber?
On 01/13/2015 09:23 AM, Rowland Penny wrote:> On 13/01/15 14:06, John Lewis wrote: >> On 01/13/2015 06:35 AM, Rowland Penny wrote: >>> On 13/01/15 11:33, John Lewis wrote: >>>> This morning I remapped gidNumber from primaryGroupID to gidNumber. I >>>> did that because I could not change the integer in primaryGroupID wit >>>> ldbedt as root. >>>> >>>> I mapped to to a new attribute called gidNumber which has no specific >>>> meaning in samba. Is there any potential problems that can arise from >>>> doing that. Is there a better way to fix that problem? >>>> >>> Hmm, definitely going to need more info here, gidNumber has a specific >>> meaning to samba, depending on how you set up samba. >>> Rowland >>> >> I took the defaults except for rfc2307 which I enabled. I am running >> Samba Version 4.1.11-Debian. > > Yes, but what as ?? an AD DC or in classic mode i.e. just like samba3 > Might be best if you post your smb.conf (sanitised ) > > RowlandI attached it to this email. -------------- next part -------------- # Global parameters [global] workgroup = OFLAMEO realm = D.OFLAMEO.COM netbios name = DRAKEBURNER server role = active directory domain controller dns forwarder = 192.168.2.1 idmap_ldb:use rfc2307 = yes [netlogon] path = /var/lib/samba/sysvol/d.oflameo.com/scripts read only = No [sysvol] path = /var/lib/samba/sysvol read only = No
Apparently Analagous Threads
- Is there any problem that can arise from remapping gidNumber?
- Is there any problem that can arise from remapping gidNumber?
- Is there any problem that can arise from remapping gidNumber?
- Is there any problem that can arise from remapping gidNumber?
- Is there any problem that can arise from remapping gidNumber?