search for: wbclookupsid

...amba files. Which in turn kept the old permission settings. I think (could be wrong) that keeping the old SID are now different from the new SID's created while rebuilding to v4.12.6. To answer your DC question: root at dc1:~# wbinfo -s S-1-5-21-589789-1426474111-2143966843-500 failed to call wbcLookupSid: WBC_ERR_DOMAIN_NOT_FOUND Could not lookup sid S-1-5-21-589789-1426474111-2143966843-500 root at dc1:~# wbinfo -s S-1-5-21-589789-1426474111-2143966843-512 failed to call wbcLookupSid: WBC_ERR_DOMAIN_NOT_FOUND Could not lookup sid S-1-5-21-589789-1426474111-2143966843-512 root at dc1:~# wbinfo -s...

...26474111-2143966843-500 S-1-5-21-589789-1426474111-2143966843-512 S-1-5-21-589789-1426474111-2143966843-513 Any member of "Domain Users" should be able to access this folder. The mbr04 server shows this: root at mbr04:~# wbinfo -s S-1-5-21-589789-1426474111-2143966843-500 failed to call wbcLookupSid: WBC_ERR_DOMAIN_NOT_FOUND Could not lookup sid S-1-5-21-589789-1426474111-2143966843-500 root at mbr04:~# wbinfo -s S-1-5-21-589789-1426474111-2143966843-512 failed to call wbcLookupSid: WBC_ERR_DOMAIN_NOT_FOUND Could not lookup sid S-1-5-21-589789-1426474111-2143966843-512 root at mbr04:~# wbinfo...

Sometimes a group sid does not get resolved to its name. Is this a settings problem? Looks like winbind deamon went dormant for a while and then woke up? I am using interface wbcLookupSid provided by the library libwbclient.so for resolving sids to names. These are the winbind related parameters in /etc/samba/smb.conf [global] # separate domain and username with '\', like DOMAIN\username winbind separator = \ # # use uids from 10000 to 20000 for domain users idmap uid = 10...

...I think (could be wrong) that > > keeping the old SID are now different from the new SID's created while > > rebuilding to v4.12.6. > > > > To answer your DC question: > > root at dc1:~# wbinfo -s S-1-5-21-589789-1426474111-2143966843-500 > > failed to call wbcLookupSid: WBC_ERR_DOMAIN_NOT_FOUND > > Could not lookup sid S-1-5-21-589789-1426474111-2143966843-500 > > root at dc1:~# wbinfo -s S-1-5-21-589789-1426474111-2143966843-512 > > failed to call wbcLookupSid: WBC_ERR_DOMAIN_NOT_FOUND > > Could not lookup sid S-1-5-21-589789-1426474111-...

....11).aspx And see here, Security options : Computer Configuration , by default the task is run in the security context of the SYSTEM account. And in case of a samba AD DC, this wil never work since systems isnt correctly mapped. On both DCs: wbinfo -G 3000002 wbinfo -s S-1-5-18 failed to call wbcLookupSid: WBC_ERR_DOMAIN_NOT_FOUND Could not lookup sid S-1-5-18 Im open for any suggestion EXCEPT changing the user in the schedules task. This is my complete smb.conf of my samba 4.5.3 ( on debian Jessie ) Maybe i missed something here. [global] workgroup = NTDOM realm = INTERNAL.DOMA...

...wbinfo -U 3000000 S-1-5-32-544 root at dc2 /# wbinfo -s S-1-5-32-544 BUILTIN\Administrators 4 root at dc2 /# wbinfo -G 3000000 S-1-5-32-544 root at dc2 /# wbinfo -s S-1-5-32-544 BUILTIN\Administrators 4 root at dc3 /# wbinfo -U 3000008 S-1-5-64-10 root at dc3 /# wbinfo -s S-1-5-64-10 failed to call wbcLookupSid: WBC_ERR_DOMAIN_NOT_FOUND Could not lookup sid S-1-5-64-10 root at dc3 /# wbinfo -G 3000008 S-1-5-64-10 root at dc3 /# wbinfo -s S-1-5-64-10 failed to call wbcLookupSid: WBC_ERR_DOMAIN_NOT_FOUND Could not lookup sid S-1-5-64-10 Any help/insight you can provide would be greatly appreciated! Thank...

Are you sure that was the only change? :-/ Tried it out, but wbinfo --lookup-sids=S-1-5-18 wbcLookupSids failed: WBC_ERR_INVALID_SID Could not lookup SIDs S-1-5-18 Does this possible has anything todo with AD/RID setups? Im on a AD setup. Selecting the users SYSTEM though search still resolve back to NTDOM\System :-) Well.. lunch first. Greetz, > > -----Oorspronkelijk bericht-----...

...2164 >> are there some workarounds ? >> > Yes, do not use the DC as a fileserver;-) > If you must, don't run a backup system that relies on IDs > > A DC has no concept of 'NT AUTHORITY': > > root at dc1:~# wbinfo --sid-to-name S-1-5-18 > failed to call wbcLookupSid: WBC_ERR_DOMAIN_NOT_FOUND > Could not lookup sid S-1-5-18 > root at dc1:~# wbinfo --name-to-sid='NT Authority\SYSTEM' > failed to call wbcLookupName: WBC_ERR_DOMAIN_NOT_FOUND > Could not lookup name NT Authority\SYSTEM > my DC works different [root at apamfs2 ~]# wbinfo --...

...wbinfo -s S-1-5-32-544 > BUILTIN\Administrators 4 > root at dc2 /# wbinfo -G 3000000 > S-1-5-32-544 > root at dc2 /# wbinfo -s S-1-5-32-544 > BUILTIN\Administrators 4 > root at dc3 /# wbinfo -U 3000008 > S-1-5-64-10 > root at dc3 /# wbinfo -s S-1-5-64-10 > failed to call wbcLookupSid: WBC_ERR_DOMAIN_NOT_FOUND > Could not lookup sid S-1-5-64-10 > root at dc3 /# wbinfo -G 3000008 > S-1-5-64-10 > root at dc3 /# wbinfo -s S-1-5-64-10 > failed to call wbcLookupSid: WBC_ERR_DOMAIN_NOT_FOUND > Could not lookup sid S-1-5-64-10 > > > Any help/insight you can...

> Hello, > > I'm trying to resolve SID from a linux using a program written in c# > running under mono. > > I already know the Windows API LookupSID ( > https://docs.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-lookupaccountsida) > and its underlying raw RPC call ( >

Il 06/11/2017 16:17, Rowland Penny via samba ha scritto: > On Mon, 6 Nov 2017 15:27:13 +0100 > Giuseppe Arvati via samba <samba at lists.samba.org> wrote: > >> Hello, >> I recently set up a new software to backup samba share. >> This software ( https://github.com/borgbackup/borg ) run on file >> server as root cron script during the night and save file on

...inistrators 4 > > root at dc2 /# wbinfo -G 3000000 > > S-1-5-32-544 > > root at dc2 /# wbinfo -s S-1-5-32-544 > > BUILTIN\Administrators 4 > > root at dc3 /# wbinfo -U 3000008 > > S-1-5-64-10 > > root at dc3 /# wbinfo -s S-1-5-64-10 > > failed to call wbcLookupSid: WBC_ERR_DOMAIN_NOT_FOUND > > Could not lookup sid S-1-5-64-10 > > root at dc3 /# wbinfo -G 3000008 > > S-1-5-64-10 > > root at dc3 /# wbinfo -s S-1-5-64-10 > > failed to call wbcLookupSid: WBC_ERR_DOMAIN_NOT_FOUND > > Could not lookup sid S-1-5-64-10 > > &...

...37994910-1777336544-1996716333-1009 > > I have no name!@bd21:~$ wbinfo --sid-to-uid=S-1-5-21- >> 3437994910-1777336544-1996716333-1009 > > 12369 > > I have no name!@bd21:~$ wbinfo --sid-to-name=S-1-5-21- >> 3437994910-1777336544-1996716333-1009 > > failed to call wbcLookupSid: WBC_ERR_DOMAIN_NOT_FOUND > > Could not lookup sid S-1-5-21-3437994910-1777336544-1996716333-1009 > > I have no name!@bd21:~$ wbinfo --sid-to-uid=S-1-5-21- >> 2473489792-1370047036-1446391509-2369 > > 12369 > > > The sid of my user differed from that on the AD serve...

...nix User\root 1 getent passwd Administrator returns nothing wbinfo --uid-to-sid=0 S-1-22-1-0 wbinfo -i Administrator failed to call wbcGetpwnam: WBC_ERR_DOMAIN_NOT_FOUND Could not get info for user Administrator On the DC Samba version is 4.6.11 wbinfo --sid-to-name=S-1-22-1-0 failed to call wbcLookupSid: WBC_ERR_DOMAIN_NOT_FOUND Could not lookup sid S-1-22-1-0 getent passwd Administrator returns nothing wbinfo --uid-to-sid=0 S-1-5-21-773202902-494389186-2375354597-500 wbinfo -i Administrator BRAIN-02\administrator:*:0:10000::/home/BRAIN-02/administrator:/bin/false Any ideas? > > Row...

...gt; > > "L.P.H. van Belle via samba" <samba at lists.samba.org> wrote: > > > > > > > Are you sure that was the only change? :-/ > > > > > > > > Tried it out, but > > > > wbinfo --lookup-sids=S-1-5-18 > > > > wbcLookupSids failed: WBC_ERR_INVALID_SID > > > > Could not lookup SIDs S-1-5-18 > > > > > > > > Does this possible has anything todo with AD/RID setups? > > > > Im on a AD setup. > > > > > > > > Selecting the users SYSTEM though search sti...

On Thu, 3 Nov 2016 10:25:00 -0400 lingpanda101 via samba <samba at lists.samba.org> wrote: > On 11/3/2016 9:59 AM, Marcio Demetrio Bacci wrote: > > Thanks Lingpanda101 > > > > Following the result of command: > > > > # file: Policies/{0F1E5B10-3640-4FFE-AA6B-5DE4CFF73625} > > # owner: 10060 > > # group: 30028 > > user::rwx > >

...eleave all your saying and everything your saying works. BUT If you going to set more advanced GPO settings, it wil end up in errors, Not working GPOs etc. Just my saying, said already to much here. Posted problems like this long ago already. Samba DC : ( 4.5.3) wbinfo --lookup-sids=S-1-5-18 wbcLookupSids failed: WBC_ERR_INVALID_SID Could not lookup SIDs S-1-5-18 Samba Member 4.5.3 and 4.5.5 For a correct windows 10 profiles share, you need the following. https://technet.microsoft.com/en-us/library/jj649079(v=ws.11).aspx which clearly shows systems with Full control. Greetz, Louis > -...

...e: > platon:~ # wbinfo -n root > failed to call wbcLookupName: WBC_ERR_DOMAIN_NOT_FOUND > Could not lookup name root > platon:~ # wbinfo -U 0 > S-1-5-21-4224351836-719640785-1152632845-1000 > platon:~ # wbinfo -s S-1-5-21-4224351836-719640785-1152632845-1000 > failed to call wbcLookupSid: WBC_ERR_DOMAIN_NOT_FOUND > Could not lookup sid S-1-5-21-4224351836-719640785-1152632845-1000 I cannot tell whether it is expected that two of the three commands fail. So for now, I'd like to make as few changes as possible to get that user mapping working again. It seems I haven't...

> root at graz-dc-sem.ad.tao.at# wbinfo --sid-to-name=S-1-5-11 > failed to call wbcLookupSid: WBC_ERR_DOMAIN_NOT_FOUND > Could not lookup sid S-1-5-11 So how fucked is my domain? On 2017-08-25 08:09, L.P.H. van Belle via samba wrote: > Ah, yes, oeps sorry, and i did run out of the office yesterday, so didnt see this.. > > 3000002:rwx > 3000003:r-x > > wbinfo --...

...n Wed, 25 Jan 2017 12:25:45 +0100 > > "L.P.H. van Belle via samba" <samba at lists.samba.org> wrote: > > > > > Are you sure that was the only change? :-/ > > > > > > Tried it out, but > > > wbinfo --lookup-sids=S-1-5-18 > > > wbcLookupSids failed: WBC_ERR_INVALID_SID > > > Could not lookup SIDs S-1-5-18 > > > > > > Does this possible has anything todo with AD/RID setups? > > > Im on a AD setup. > > > > > > Selecting the users SYSTEM though search still resolve back to > > &...