Displaying 10 results from an estimated 10 matches for "stmiss".
Did you mean:
stmass
2017 Jun 03
1
failed to call wbcGetpwnam/wbcGetgrnam/wbcGetpwsid WBC_ERR_DOMAIN_NOT_FOUND
I feel you have missed the point of my original post, or maybe I wasn't
clear enough. This is not a freshly provisioned install, this is an install
that has been in use for some 12-18 months.
On 3 June 2017 at 20:41, Rowland Penny via samba <samba at lists.samba.org>
wrote:
> On Sat, 3 Jun 2017 20:16:25 +0100
> Alex Matthews via samba <samba at lists.samba.org> wrote:
>
2017 Jun 02
2
failed to call wbcGetpwnam/wbcGetgrnam/wbcGetpwsid WBC_ERR_DOMAIN_NOT_FOUND
Still no joy on this.
@Rowland - Everything except the tests I mentioned in my first post work as
expected, when compared to what you sent me.
On 26 May 2017 at 14:20, Rowland Penny via samba <samba at lists.samba.org>
wrote:
> On Fri, 26 May 2017 13:31:09 +0100
> Alex Matthews via samba <samba at lists.samba.org> wrote:
>
> >
> > > From what I know about
2017 Jun 08
0
failed to call wbcGetpwnam/wbcGetgrnam/wbcGetpwsid WBC_ERR_DOMAIN_NOT_FOUND
> You don't have any idmap configuration in that smb.conf.
Correct. That is my idmap configuration.
> At last, there is your problem, you need PAM because you need Unix authentication.
If you set up PAM 'getent passwd testuser' will work.
<bangs head against a brick wall HARD> That is NOT my problem because I am
not trying to get unix auth to work... I am trying to get
2017 Jun 08
0
failed to call wbcGetpwnam/wbcGetgrnam/wbcGetpwsid WBC_ERR_DOMAIN_NOT_FOUND
Rowland - please, don't get in the way of others being constructive to
solving this issue. I do not need to know your opinions.
Louis - thanks for your responses. I have just updated to 4.6.4 (4.6.5
isn't in a repo yet) and run samba-tool testparm. Unfortunately, no issues.
It also does not fix the underlying issue.
As for your other questions:
# getent passwd testuser
<nothing>
2017 Jun 16
1
samba-tool ntacl sysvolreset ERROR
Or if you want to maintain the 'log level = 2' you can set just the 'vfs'
log level to 1 eg:
log level = 2 vfs:1
This way you are just silencing the bit that needs to be silenced, not the
whole of samba. If that's what you want, of course.
On 16 June 2017 at 07:06, Rowland Penny via samba <samba at lists.samba.org>
wrote:
> On Thu, 15 Jun 2017 20:00:42 -0300
>
2017 May 26
2
failed to call wbcGetpwnam/wbcGetgrnam/wbcGetpwsid WBC_ERR_DOMAIN_NOT_FOUND
>Sorry if I upset you, but....
Thanks, the apology is much appreciated.
> Do you have the correct libnss_winbind.so in your lib path ?
# locate libnss
/usr/lib/libnss_compat-2.25.so
/usr/lib/libnss_compat.so
/usr/lib/libnss_compat.so.2
<truncated>
/usr/lib/libnss_winbind.so
/usr/lib/libnss_winbind.so.2
> From what I know about arch, it is based on ubuntu, which is based on d
2017 Jun 02
3
failed to call wbcGetpwnam/wbcGetgrnam/wbcGetpwsid WBC_ERR_DOMAIN_NOT_FOUND
Arch doesn't have versions, it's a rolling release.
Also, it's a DC not a Domain Member.
I gave my versions at the beginning of this discussion.
I'm 99% sure it's something screwy with this installation/provision but
I've checked all the usual suspects.
On 2 June 2017 at 11:44, Rowland Penny <rpenny at samba.org> wrote:
> On Fri, 2 Jun 2017 10:02:10 +0100
>
2017 May 25
2
failed to call wbcGetpwnam/wbcGetgrnam/wbcGetpwsid WBC_ERR_DOMAIN_NOT_FOUND
Hiya,
I've run into a problem on a Samba 4.5.8 active directory domain
controller. The domain controller seems to work to authenticate against (I
have a couple of domain members). However wbinfo throws an error when used
locally. My configs are posted at the bottom of the page.
# wbinfo -t
checking the trust secret for domain SMC via RPC calls succeeded
# wbinfo -u
<list of domain
2017 Jun 03
2
failed to call wbcGetpwnam/wbcGetgrnam/wbcGetpwsid WBC_ERR_DOMAIN_NOT_FOUND
That's great. You managed to get a freshly installed Arch linux install to
provision correctly. This doesn't help me solve my issue in the slightest.
I don't need to know that it CAN work correctly, I need to know why my
install is NOT working correctly and so far you, Rowland, have not done
anything to help that situation.
Sorry to be blunt but all you have done is prove what I
2017 May 26
2
failed to call wbcGetpwnam/wbcGetgrnam/wbcGetpwsid WBC_ERR_DOMAIN_NOT_FOUND
>Why do people add stuff to the smb.conf on a DC without really knowing what
they are doing ???
Why do people on mailing-lists always treat people who make mistakes like
children? You patronising..... person....
Maybe you should consider that this smb.conf has been on a server for a
long time and that servers roles have changed.
wins support # From the pre AD days, perhaps?
enumports command