Displaying 13 results from an estimated 13 matches for "wbcgetgrgid".
2017 Jan 13
1
Duplicate xidNumbers
...18 = Local System
3000003 dn: CN=S-1-5-21-976934076-1976663741-3168181429-514 = Domain
Guests
3000003 dn: CN=S-1-5-11 = Authenticated Users
Empty xidNumbers
3000011
3000012
wbinfo --gid-info shows:
root at CY-DC:~# wbinfo --gid-info 3000002
failed to call wbcGetgrgid: WBC_ERR_DOMAIN_NOT_FOUND
Could not get info for gid 3000002
root at CY-DC:~# wbinfo --gid-info 3000003
failed to call wbcGetgrgid: WBC_ERR_DOMAIN_NOT_FOUND
Could not get info for gid 3000003
root at CY-DC:~# wbinfo --gid-info 3000011
failed to call wbcGetgrgid: WBC_ERR_DOMAIN_NOT_FOUND
Could not...
2017 Sep 25
2
Domain member server: user access
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 [mailto:s...
2014 Apr 25
3
BUILTIN not mapping on DC
Running 4.1.6-SerNet-RedHat-7.el6 on CentOS 6.5.
I've been bumping my head against GPO issues and am now wondering if its
connected to my BUILTIN groups not mapping on my DC.
For instance on DC:
sh-4.1# wbinfo --gid-info=544
failed to call wbcGetgrgid: WBC_ERR_DOMAIN_NOT_FOUND
Could not get info for gid 544
But on a member:
sh-4.1# wbinfo --gid-info=544
BUILTIN\administrators:x:544:
Likewise `getent group BUILTIN\\administrators` fails on the DC.
Any ideas?
Here is my smb.conf:
[global]
workgroup = xxx
realm = xxx
ne...
2017 Sep 25
2
Domain member server: user access
...Weichinger via samba" <samba at lists.samba.org> wrote:
> Am 2017-09-25 um 16:48 schrieb L.P.H. van Belle via samba:
> > 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.
>
> Sa...
2017 Jan 13
3
Duplicate xidNumbers
...,
>>>>
>>>> First stopped Samba, backed up idmap.ldp and ldpedit deleted the
>>>> duplicates. Started Samba and it did recreate the records so I
>>>> did net cache flush but wbinfo --gid-info failed for the new xids:
>>>> failed to call wbcGetgrgid: WBC_ERR_DOMAIN_NOT_FOUND
>>>> No change in sysvolreset also.
>>>>
>>>> Second, I stopped samba, restored backup idmap.ldp and just edited:
>>>> 3000002 dn: CN=S-1-5-21-976934076-1976663741-3168181429-501 to
>>>> 3000011 3000003 dn:
>...
2017 Jan 13
3
Fwd: Re: Duplicate xidNumbers
Rowland,
Thank you for the quick response.
I have just run net cache flush no change in problem. I have dumped the
idmap.ldp using ldbsearch -H /var/lib/samba/private/idmap.ldb >
idmap.txt and did some sorting, that is how I found the duplicates.
On 1/13/2017 11:09 AM, Rowland Penny via samba wrote:
> samba-tool ntacl
> >sysvolreset
2017 Jan 24
4
Security Principals, and SID's mapping bug
Hai,
Does anyone know more if this is adressed or point me to the bug report?
There should be one, but i cant find it.
Im finding the following again, tested with samba 4.4.5, now samba 4.5.3.
These reports go back to the year 2013.
I searched in my mail samba folder for S-1-5-18
The problem.
I create a "computer" Scheduled task.
Now this task MUST run as : SYSTEM (S-1-5-18)
2017 Jan 13
2
Duplicate xidNumbers
...gt;>> First stopped Samba, backed up idmap.ldp and ldpedit deleted the
>>>>>> duplicates. Started Samba and it did recreate the records so I
>>>>>> did net cache flush but wbinfo --gid-info failed for the new
>>>>>> xids: failed to call wbcGetgrgid: WBC_ERR_DOMAIN_NOT_FOUND
>>>>>> No change in sysvolreset also.
>>>>>>
>>>>>> Second, I stopped samba, restored backup idmap.ldp and just
>>>>>> edited: 3000002 dn:
>>>>>> CN=S-1-5-21-976934076-1976663741-316...
2017 Jan 13
0
Duplicate xidNumbers
...two ways but it didn't seem to help,
>>
>> First stopped Samba, backed up idmap.ldp and ldpedit deleted the
>> duplicates. Started Samba and it did recreate the records so I did
>> net cache flush but wbinfo --gid-info failed for the new xids:
>> failed to call wbcGetgrgid: WBC_ERR_DOMAIN_NOT_FOUND
>> No change in sysvolreset also.
>>
>> Second, I stopped samba, restored backup idmap.ldp and just edited:
>> 3000002 dn: CN=S-1-5-21-976934076-1976663741-3168181429-501 to
>> 3000011 3000003 dn: CN=S-1-5-21-976934076-1976663741-3168181429-...
2016 Apr 12
2
failed to find NT AUTHORITY domain log message during backup windows
On Mon, Apr 11, 2016 at 6:10 PM, Jonathan Hunter <jmhunter1 at gmail.com>
wrote:
> It sounds as though there are files on your servers owned by a UID or GID
> (most probably a GID) that is not in /etc/group, and is being looked up and
> "reverse resolved" to 'NT AUTHORITY\Authenticated Users', but this somehow
> doesn't map back the other way, i.e. from a
2017 Jan 13
0
Duplicate xidNumbers
...gt; >>>> First stopped Samba, backed up idmap.ldp and ldpedit deleted the
> >>>> duplicates. Started Samba and it did recreate the records so I
> >>>> did net cache flush but wbinfo --gid-info failed for the new
> >>>> xids: failed to call wbcGetgrgid: WBC_ERR_DOMAIN_NOT_FOUND
> >>>> No change in sysvolreset also.
> >>>>
> >>>> Second, I stopped samba, restored backup idmap.ldp and just
> >>>> edited: 3000002 dn:
> >>>> CN=S-1-5-21-976934076-1976663741-3168181429-501 to...
2017 Jan 13
0
Duplicate xidNumbers
...st stopped Samba, backed up idmap.ldp and ldpedit deleted
> >>>>>> the duplicates. Started Samba and it did recreate the
> >>>>>> records so I did net cache flush but wbinfo --gid-info failed
> >>>>>> for the new xids: failed to call wbcGetgrgid:
> >>>>>> WBC_ERR_DOMAIN_NOT_FOUND No change in sysvolreset also.
> >>>>>>
> >>>>>> Second, I stopped samba, restored backup idmap.ldp and just
> >>>>>> edited: 3000002 dn:
> >>>>>> CN=S-1-5-21...
2017 Sep 25
9
Domain member server: user access
samba-4.6.8 on both DC and DM.
3 users were created as suggested:
DC # samba-tool user create kamleitnerl Le26xxx
--nis-domain=arbeitsgruppe --unix-home=/home/kamleitnerl
--uid-number=10070 --login-shell=/bin/false --gid-number=100
this user can login to a Windows PC, but not access/connect shares.
log for the PC's IP:
[2017/09/25 15:45:10.522051, 1]