similar to: failed to call wbcGetpwnam/wbcGetgrnam/wbcGetpwsid WBC_ERR_DOMAIN_NOT_FOUND

Displaying 20 results from an estimated 3000 matches similar to: "failed to call wbcGetpwnam/wbcGetgrnam/wbcGetpwsid WBC_ERR_DOMAIN_NOT_FOUND"

2017 Jun 07
0
failed to call wbcGetpwnam/wbcGetgrnam/wbcGetpwsid WBC_ERR_DOMAIN_NOT_FOUND
He did not test : getent passwd username result ? He did test : getent passwd result ok He could test with : wbinfo --own-domain Results: NTDOM And this should show: wbinfo --all-domains Results: BUILDIN HOSTNAME NTDOM Im guessing, the last one wil fail. Things to check. samba idmap setup. nsswitch.conf idmap.conf pam setup. So best option lookt to me upgrade to 4.6.5 and run
2017 Jun 03
3
failed to call wbcGetpwnam/wbcGetgrnam/wbcGetpwsid WBC_ERR_DOMAIN_NOT_FOUND
> Op 3 jun. 2017 om 23:07 heeft Rowland Penny via samba <samba at lists.samba.org> het volgende geschreven: > > On Sat, 3 Jun 2017 21:49:15 +0100 > Alex Matthews via samba <samba at lists.samba.org> wrote: > >> 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
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 08
0
failed to call wbcGetpwnam/wbcGetgrnam/wbcGetpwsid WBC_ERR_DOMAIN_NOT_FOUND
( copy the parts from Rowlands mail ) > I do not have an idmap.conf? it is part of smb.conf A small mixup here, See below. There are 2 idmap definitions ( smb.conf and idmap.conf ) idmap.conf is/should normaly not be needed, this all depends on the setup. More comment below. > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens Alex >
2017 Jun 08
1
failed to call wbcGetpwnam/wbcGetgrnam/wbcGetpwsid WBC_ERR_DOMAIN_NOT_FOUND
> That would be idmapd.conf, not idmap.conf Oeps, you correct. Typo there.. And you only might need this when you use nfs. But i dont know if he uses that. # wbinfo --all-domains Yes, the COMPUTERNAME only shows on the member servers. Thanks for the corrections. ;-) Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens
2017 May 25
0
failed to call wbcGetpwnam/wbcGetgrnam/wbcGetpwsid WBC_ERR_DOMAIN_NOT_FOUND
On Thu, 25 May 2017 13:25:15 +0100 Alex Matthews via samba <samba at lists.samba.org> wrote: > 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
2017 Jun 08
3
failed to call wbcGetpwnam/wbcGetgrnam/wbcGetpwsid WBC_ERR_DOMAIN_NOT_FOUND
On Thu, 8 Jun 2017 10:41:39 +0100 Alex Matthews via samba <samba at lists.samba.org> wrote: > Rowland - please, don't get in the way of others being constructive to > solving this issue. I do not need to know your opinions. I was being constructive. I will also reply to this and try to be constructive. > > Louis - thanks for your responses. I have just updated to 4.6.4
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
2017 May 26
0
failed to call wbcGetpwnam/wbcGetgrnam/wbcGetpwsid WBC_ERR_DOMAIN_NOT_FOUND
On Fri, 26 May 2017 13:31:09 +0100 Alex Matthews via samba <samba at lists.samba.org> wrote: > > > From what I know about arch, it is based on ubuntu, which is based > > on d > ebian > Arch is not based on any other distro. Shows you how much I know about Arch Linux ;-) > > # pacman -Qo /usr/lib/libnss_winbind.so.2 > /usr/lib/libnss_winbind.so.2 is owned by
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 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 May 26
0
failed to call wbcGetpwnam/wbcGetgrnam/wbcGetpwsid WBC_ERR_DOMAIN_NOT_FOUND
On Fri, 26 May 2017 12:21:35 +0100 Alex Matthews via samba <samba at lists.samba.org> wrote: > >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
2017 Jun 03
0
failed to call wbcGetpwnam/wbcGetgrnam/wbcGetpwsid WBC_ERR_DOMAIN_NOT_FOUND
On Fri, 2 Jun 2017 12:39:49 +0100 Alex Matthews via samba <samba at lists.samba.org> wrote: > 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
2017 Jun 03
0
failed to call wbcGetpwnam/wbcGetgrnam/wbcGetpwsid WBC_ERR_DOMAIN_NOT_FOUND
On Sat, 3 Jun 2017 20:16:25 +0100 Alex Matthews via samba <samba at lists.samba.org> wrote: > 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
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 07
5
failed to call wbcGetpwnam/wbcGetgrnam/wbcGetpwsid WBC_ERR_DOMAIN_NOT_FOUND
On Wed, 7 Jun 2017 17:01:03 +0200 "L.P.H. van Belle via samba" <samba at lists.samba.org> wrote: > He did not test : > getent passwd username > result ? > > He did test : > getent passwd > result ok > > He could test with : > wbinfo --own-domain > Results: > NTDOM > > And this should show: > wbinfo --all-domains > Results:
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 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
2016 Aug 24
1
Winbind occasionally forgets some users (failed to call wbcGetpwnam: WBC_ERR_DOMAIN_NOT_FOUND)
I've been googling, but can't seem to find an answer to this one. We have a Windows network with ~25 sites. Each site has a local Windows DC. Each site has a Debian 8.5 box running Samba 4.2.10-Debian. We decided to test moving shares from the Windows Server to the local Debian machine. (zfs snapshot is *really* handy when someone decides to open cryptolocker). File sharing has been