Displaying 7 results from an estimated 7 matches for "wbcstringtosid".
2017 Nov 18
3
The group name could not be found
...: *
type : SID_NAME_USE_NONE (0)
sid : *
sid : S-0-0
result : NT_STATUS_NONE_MAPPED
However from one of the dc's:
$ wbinfo -s S-0-0
failed to call wbcStringToSid: WBC_ERR_INVALID_SID
Could not lookup sid S-0-0
$ wbinfo -n ianc
S-1-5-21-2093009959-3443338361-3281248646-1407 SID_USER (1)
$ wbinfo --user-domgroups=S-1-5-21-2093009959-3443338361-3281248646-1407
S-1-5-21-2093009959-3443338361-3281248646-1407
S-1-5-21-2093009959-3443338361-3281248646-513
S-1-5-...
2015 Dec 01
2
Problems with authentication in Samba4
...n I put ^ as
separator, how in Domain^Users, the error message appeared:
root at proxy:~# *echo "bacci Domain^Users" | /usr/lib/squid3/wbinfo_group.pl
<http://wbinfo_group.pl>*
failed to call wbcLookupName: WBC_ERR_DOMAIN_NOT_FOUND
Could not lookup name Domain^Users
failed to call wbcStringToSid: WBC_ERR_INVALID_PARAM
Could not convert sid to gid
ERR
But, when I put %20 as separator, how in Domain%20Users, the authentication
is OK.
root at proxy:~# *echo "bacci Domain%20Users" |
/usr/lib/squid3/wbinfo_group.pl <http://wbinfo_group.pl>*
OK
My environment is: Samba 4.2.1...
2010 Nov 08
7
winbind sometimes does not resolve sid to a name
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
2017 Nov 18
0
The group name could not be found
...: SID_NAME_USE_NONE (0)
> sid : *
> sid : S-0-0
> result : NT_STATUS_NONE_MAPPED
>
> However from one of the dc's:
> $ wbinfo -s S-0-0
> failed to call wbcStringToSid: WBC_ERR_INVALID_SID
> Could not lookup sid S-0-0
>
> $ wbinfo -n ianc
> S-1-5-21-2093009959-3443338361-3281248646-1407 SID_USER (1)
>
> $ wbinfo --user-domgroups=S-1-5-21-2093009959-3443338361-3281248646-1407
> S-1-5-21-2093009959-3443338361-3281248646-1407
> S-1-5-21-20930...
2018 Nov 18
0
getenv does not return any AD DOMAIN users or groups - ?nsswitch is not setup for Samba?
...If the SID does not correspond to a UNIX user mapped
by winbindd(8) then the operation will fail.
I used the wbinfo command with a SID from a domain user. It fails which seems to confirm that there is some missing link with winbindd as mentioned on the man page.
result:
failed to call wbcStringToSid: WBC_ERR_INVALID_SID
could not convert sid S-1-5-21-346857055-4299993622516-4263914971-1113 to uid
Barry
2019 Mar 14
1
Samba 4.8 Config SMB.Conf File
I am having similar issues going form 4.7.12 to 4.8.9
Previous smb.conf on a member server just no longer IDs users.
wbinfo -u and wbinfo -g return proper information; however, id does not.
The error appears to be in mapping SIDs.
# wbinfo -n user
<sid>
# wbinfo -S <sid>
ailed to call wbcSidToUid: WBC_ERR_DOMAIN_NOT_FOUND
Could not convert sid <sid> to uid
Notably, I do use
2018 Nov 16
7
getenv does not return any AD DOMAIN users or groups - ?nsswitch is not setup for Samba?
The problem is that getenv does not return any AD domain users or groups. From much research this seems to be because nsswitch is not setup for Samba.
I would really appreciate some assistance as I think this is my last hurdle for actually being able to use this test file server.
Ubuntu server 18.04 - Samba installed and configured (almost)
Kerberos functioning. wbinfo --ping-dc successfully