search for: local_ad02

...I see the following repeated in syslog:- ==> syslog <== Aug 21 15:25:41 hostname01 winbindd[691]: [2017/08/21 15:25:41.438959, 0] ../source3/libsmb/cliconnect.c:1895(cli_session_setup_spnego_send) Aug 21 15:25:41 hostname01 winbindd[691]: Kinit for HOSTNAME01$@DOMAIN.LOCAL to access cifs/LOCAL_AD02.domain.local at DOMAIN.LOCAL failed: Cannot contact any KDC for requested realm When one of the suspect users tries to log in I get:- ==> auth.log <== Aug 21 15:25:14 op-sdes-dsk01 su[690]: No passwd entry for user 'username' Aug 21 15:25:14 op-sdes-dsk01 su[690]: FAILED su for user...

August 21, 2017 5:34 PM, "Rowland Penny via samba" <samba at lists.samba.org> wrote: > On Mon, 21 Aug 2017 15:37:03 +0000 > "A. James Lewis" <james at fsck.co.uk> wrote: > >> OK, obviously I am slightly sanitising the output here, but I'm >> preserving the case, and just replacing local names with generic ones >> as I did for the

...yslog <== >> Aug 21 15:25:41 hostname01 winbindd[691]: [2017/08/21 >> 15:25:41.438959, >> 0] ../source3/libsmb/cliconnect.c:1895(cli_session_setup_spnego_send) >> Aug 21 15:25:41 hostname01 winbindd[691]: Kinit for >> HOSTNAME01$@DOMAIN.LOCAL to access >> cifs/LOCAL_AD02.domain.local at DOMAIN.LOCAL failed: Cannot contact any >> KDC for requested realm >> >> When one of the suspect users tries to log in I get:- >> >> ==> auth.log <== >> Aug 21 15:25:14 op-sdes-dsk01 su[690]: No passwd entry for user >> 'username...

...nd IP of the AD server.... and connect to it. The error from kinit had the hostname of one of the AD servers in it, that name is not in the config, and that address was reachable... so I can't think that it's DNS. What is worrying me is if this is valid, to have the domain in twice:- cifs/LOCAL_AD02.domain.local at DOMAIN.LOCAL in the kinit error from auth.log I'd love to solve this issue too... but I started with one issue, and now I have 2... LOL! James August 21, 2017 6:02 PM, "Rowland Penny via samba" <samba at lists.samba.org> wrote: > On Mon, 21 Aug 2017 16:47...

...init had the hostname of one of the AD >> servers in it, >> that name is not in the config, and that address was >> reachable... so I >> can't think that it's DNS. >> >> What is worrying me is if this is valid, to have the domain in >> twice:- cifs/LOCAL_AD02.domain.local at DOMAIN.LOCAL in the >> kinit error >> from auth.log >> >> I'd love to solve this issue too... but I started with one >> issue, and >> now I have 2... LOL! >> >> That is perfectly normal, so stop worrying >> >> There...

...; The error from kinit had the hostname of one of the AD servers in >> it, that name is not in the config, and that address was >> reachable... so I can't think that it's DNS. >> >> What is worrying me is if this is valid, to have the domain in >> twice:- cifs/LOCAL_AD02.domain.local at DOMAIN.LOCAL in the >> kinit error >> from auth.log >> >> I'd love to solve this issue too... but I started with one issue, >> and now I have 2... LOL! >> >> That is perfectly normal, so stop worrying >> >> There is an eas...

Hi all, I've just been following a series of guides to set up "winbind" authentication on a container build I'm working on, but I'm seeing some strange behaviour.... After the "net ads join -k", some users can log in, but others cannot (pam says their account does not exist)... although they can all authenticate with kinit! If someone has an idea why this might