search for: sid_dom_group

...ocal/samba/bin/samba-tool group add SambaTool-GG-Sec --group-scope=Global --group-type=Security Added group SambaTool-GG-Sec root at dc1:~# getent group EXAMPLE+SambaTool-GG-Sec:*:3000056: root at dc1:~# /usr/local/samba/bin/wbinfo -n SambaTool-GG-Sec S-1-5-21-3390367671-3527586854-3401016232-1129 SID_DOM_GROUP (2) root at dc1:~# /usr/local/samba/bin/ldbedit -e vi -H /usr/local/samba/private/idmap.ldb objectsid=S-1-5-21-3390367671-3527586854-3401016232-1129 # editing 1 records # record 1 dn: CN=S-1-5-21-3390367671-3527586854-3401016232-1129 cn: S-1-5-21-3390367671-3527586854-3401016232-1129 objectClass:...

Arg.. wbinfo --gid-info=100 DC: Confirmed, DOMAIN\Domain Users Member: Fail. failed to call wbcGetgrgid: WBC_ERR_DOMAIN_NOT_FOUND Could not get info for gid 100 But both server show the same with : wbinfo -n "NTDOM\domain users" So imho, report bug if Rowland can confirm this with a samba from source. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba

...t; Epoch?????? : 2 > Version???? : 4.10.7 > Release???? : 0.fc30 > Architecture: x86_64 > > > I have some strange problems with AD: > > at domain member: > > oceanic:~# wbinfo -n "WSISIZ.EDU.PL\\laboratoria" > S-1-5-21-3156691614-3416019035-1284015310-3077 SID_DOM_GROUP (2) > oceanic:~# wbinfo -Y S-1-5-21-3156691614-3416019035-1284015310-3077 > failed to call wbcSidToGid: WBC_ERR_DOMAIN_NOT_FOUND > Could not convert sid S-1-5-21-3156691614-3416019035-1284015310-3077 > to gid > > oceanic:~# wbinfo? --online-status > BUILTIN : active connection...

Yes: # getent group GROUP group:x:17573: # getent group group2 group2:x:11010: # getent group GROUP3 group3:x:21178: # wbinfo --group-info GROUP group:x:17573: # wbinfo -n GROUP S-1-5-21-948789634-15155995-928725530-7573 SID_DOM_GROUP (2)

...02-513 (Domain Group: 2) >> > > Looks correct, try these: > > wbinfo -n Domain\ Users > > wbinfo --group-info=Domain\ Users > > wbinfo --gid-info=10513 > > Rowland root at main:/etc/samba# wbinfo -n Domain\ Users S-1-5-21-2777655458-4002997014-749295002-513 SID_DOM_GROUP (2) root at main:/etc/samba# wbinfo --group-info=Domain\ Users domain users:x:10513: root at main:/etc/samba# wbinfo --gid-info=10513 domain users:x:10513: looks good as well to me?

...cumented?) Samba is at version: Name??????? : samba Epoch?????? : 2 Version???? : 4.10.7 Release???? : 0.fc30 Architecture: x86_64 I have some strange problems with AD: at domain member: oceanic:~# wbinfo -n "WSISIZ.EDU.PL\\laboratoria" S-1-5-21-3156691614-3416019035-1284015310-3077 SID_DOM_GROUP (2) oceanic:~# wbinfo -Y S-1-5-21-3156691614-3416019035-1284015310-3077 failed to call wbcSidToGid: WBC_ERR_DOMAIN_NOT_FOUND Could not convert sid S-1-5-21-3156691614-3416019035-1284015310-3077 to gid oceanic:~# wbinfo? --online-status BUILTIN : active connection OCEANIC : active connection WSISIZ...

...samba from > > source. > > Same here on DM: > > # wbinfo --gid-info=100 > failed to call wbcGetgrgid: WBC_ERR_DOMAIN_NOT_FOUND > Could not get info for gid 100 > > # wbinfo -n "ARBEITSGRUPPE\Domain Users" > S-1-5-21-2777655458-4002997014-749295002-513 SID_DOM_GROUP (2) > > DC: > > # wbinfo --gid-info=100 > ARBEITSGRUPPE\domain users:x:100: > > # wbinfo -n "ARBEITSGRUPPE\Domain Users" > S-1-5-21-2777655458-4002997014-749295002-513 SID_DOM_GROUP (2) > > How many times do I have to say this, 'wbinfo' connects...

...h id mapping configuration: wbinfo -u works. wbinfo -g works. getent group does not list domain users and groups. I logged into PDC and checked gidNumber for "Domain Users": [root at site-ad ~]# wbinfo --name-to-sid "Domain Users" S-1-5-21-4155694911-3186826046-1573605777-513 SID_DOM_GROUP (2) [root at site-ad ~]# wbinfo --sid-to-gid S-1-5-21-4155694911-3186826046-1573605777-513 985 (same as 'users' unix gid on host) And the same check for "Domain Admins": [root at site-ad ~]# wbinfo --sid-to-gid S-1-5-21-4155694911-3186826046-1573605777-512 3000004 My file serve...

...10.7 >> Release???? : 0.fc30 >> Architecture: x86_64 >> >> >> I have some strange problems with AD: >> >> at domain member: >> >> oceanic:~# wbinfo -n "WSISIZ.EDU.PL\\laboratoria" >> S-1-5-21-3156691614-3416019035-1284015310-3077 SID_DOM_GROUP (2) >> oceanic:~# wbinfo -Y S-1-5-21-3156691614-3416019035-1284015310-3077 >> failed to call wbcSidToGid: WBC_ERR_DOMAIN_NOT_FOUND >> Could not convert sid S-1-5-21-3156691614-3416019035-1284015310-3077 >> to gid >> >> oceanic:~# wbinfo? --online-status >>...

On 16/09/2019 15:04, L.P.H. van Belle via samba wrote: > Well it was worth checking.. We just dont know what you already checked.. > > Then all i can say now is, or a different OS, or try Vincent's his packages. > I see that is should support AD-DC, but I really dont know. I only do debian/ubuntu. > At least it looks like it. > > (from :

...gid numbers for chown if you don't have winbind, sssd, nslcd, or something like it installed to do a mapping on that machine? I know how to get to the appropriate numbers if winbind is installed on the server. # wbinfo -n "Domain Users" S-1-5-21-1358803832-2400073699-459451966-513 SID_DOM_GROUP (2) # wbinfo -Y S-1-5-21-1358803832-2400073699-459451966-513 10001 # chown :10001 I also know how to get those numbers from ADUC *IF* the groups/users involved have their posix attributes set up by ADUC (or at least have their NIS domain set). But what is the canonical way to get that informat...

...OM\domain guests SAMDOM\domain computers SAMDOM\domain controllers SAMDOM\schema admins SAMDOM\enterprise admins SAMDOM\group policy creator owners SAMDOM\read-only domain controllers SAMDOM\dnsupdateproxy root at dc01:~# wbinfo -n "Domain Users" S-1-5-21-589789-1426474111-2143966843-513 SID_DOM_GROUP (2) I have been troubleshooting to confirm a properly setup AD? DC and member server. All previous tests are passing. Could I have some other issue? -- Bob Wooden

I've got this on the backup DC root at bdc:~# wbinfo --sid-to-gid S-1-5-21-1166961617-3197558402-3341820450-516 3000000 while root at bdc:~# ldbedit -H /usr/local/samba/private/idmap.ldb objectsid=S-1-5-21-1166961617-3197558402-3341820450-516 shows correct xid 3000019 and on the primary DC I've got itk at dc:/$ wbinfo --sid-to-gid S-1-5-21-1166961617-3197558402-3341820450-516 3000019

...8945(domain users),1278739538(rwuser),1278739551(ur_users),1278739543(ur-lab-privateshare-rw),1278739547(b-rw),1278739545(ur-lab-privateshare-a-rw),1278739556(ubuntu_share_rw) ur-lab-privateshare-rw root at UR-Lab:~# wbinfo -n ur-lab-privateshare-rw S-1-5-21-3759969785-1361971536-1710822149-1111 SID_DOM_GROUP (2) ur-lab-privateshare-ro root at UR-Lab:~# wbinfo -n ur-lab-privateshare-ro S-1-5-21-3759969785-1361971536-1710822149-1110 SID_DOM_GROUP (2) Testparm Output =============== Load smb config files from /etc/samba/smb.conf lpcfg_do_global_parameter: WARNING: The "null passwords" option...

...-H /usr/local/samba/private/sam.ldb '(cn=stduser)' cn primaryGroupID memberOf dn: CN=stduser,CN=Users,DC=my,DC=example,DC=com cn: stduser primaryGroupID: 513 memberOf: CN=stdgroup,CN=Users,DC=my,DC=example,DC=com ~# wbinfo --name-to-sid=stdgroup S-1-5-21-1691533938-518786298-626738373-3385 SID_DOM_GROUP (2) ~# cat /tmp/chggrp.ldif dn: cn=stduser,cn=Users,dc=my,dc=example,dc=com changetype: modify replace: primarygroupid primarygroupid: 3385 ~# ldbmodify --url=/usr/local/samba/private/sam.ldb /tmp/chggrp.ldif Modified 1 records successfully ------------------------------- 3) Now it's impossi...

...> OK, you have problems there, but not what you think. On my first DC > (note I don't have a 'primary' or a 'backup' DC, I just have DC's) if I > run 'wbinfo --name-to-sid=Domain\ Controllers' , I get: > > S-1-5-21-2025076216-3455336656-3842161122-516 SID_DOM_GROUP (2) > > If I then run 'wbinfo > --sid-to-gid=S-1-5-21-2025076216-3455336656-3842161122-516' , I get: > > 3000025 > > But if I run the same command on my other DC, I get: > > 3000021 > > This is because idmap.ldb is not replicated between DC's . This can...

...0450-516 > 3000000 OK, you have problems there, but not what you think. On my first DC (note I don't have a 'primary' or a 'backup' DC, I just have DC's) if I run 'wbinfo --name-to-sid=Domain\ Controllers' , I get: S-1-5-21-2025076216-3455336656-3842161122-516 SID_DOM_GROUP (2) If I then run 'wbinfo --sid-to-gid=S-1-5-21-2025076216-3455336656-3842161122-516' , I get: 3000025 But if I run the same command on my other DC, I get: 3000021 This is because idmap.ldb is not replicated between DC's . This can be checked by running 'ldbedit -e nano -H /v...

Am 22.02.19 um 15:16 schrieb Rowland Penny via samba: > On Fri, 22 Feb 2019 15:03:37 +0100 > "L.P.H. van Belle via samba" <samba at lists.samba.org> wrote: > >> Hai, >> >> That bond0 interface, you might want to change that the interface >> name to bond1 Depending on the bonding settings, you might have hit a >> reserved name. I lots my docu

...; SAMDOM\domain controllers > SAMDOM\schema admins > SAMDOM\enterprise admins > SAMDOM\group policy creator owners > SAMDOM\read-only domain controllers > SAMDOM\dnsupdateproxy > > root at dc01:~# wbinfo -n "Domain Users" > S-1-5-21-589789-1426474111-2143966843-513 SID_DOM_GROUP (2) > > I have been troubleshooting to confirm a properly setup AD? DC and > member server. > > All previous tests are passing. > > Could I have some other issue? > Did you miss this: if Domain Users does not have a gidNumber, you probably do not have any yet, so you can...

On Wed, 29 Nov 2023 17:45:16 +0100 Marco Gaiarin via samba <samba at lists.samba.org> wrote: > Mandi! Rowland Penny via samba > In chel di` si favelave... > > >> acl_xattr:default acl style = windows > >> acl_xattr:ignore system acls = yes > > Why have you added those two last lines ? > > Ahem, really you need an answer?! ;-) > >