search for: resolveconf

...Failed to start Samba AD Daemon. --- If I manually start it: $ systemctl start samba-ad-dc then it loads ok. Is the systemd unit file missing a dependency? I compared the version between an AD running 4.10.14 and 4.11.12(this current problem machine) and the one difference between the two is that resolveconf.service is listed as a dependency in 4.11.12 and not in the older version. $ systemctl list-dependencies samba-ad-dc ? ??system.slice ? ??network-online.target ? ? ??systemd-networkd-wait-online.service ? ??sysinit.target ? ??apparmor.service ? ??blk-availability.service ? ??dev-hugepages.mo...

...manually start it: > $ systemctl start samba-ad-dc > then it loads ok. > > Is the systemd unit file missing a dependency? I compared the version > between an AD running 4.10.14 and 4.11.12(this current > problem machine) and > the one difference between the two is that > resolveconf.service is listed as > a dependency in 4.11.12 and not in the older version. > > $ systemctl list-dependencies samba-ad-dc > ??? ??????system.slice > ??? ??????network-online.target > ??? ??? ??????systemd-networkd-wait-online.service > ??? ??????sysinit.target > ???? ?????...

...manually start it: > $ systemctl start samba-ad-dc > then it loads ok. > > Is the systemd unit file missing a dependency? I compared the version > between an AD running 4.10.14 and 4.11.12(this current > problem machine) and > the one difference between the two is that > resolveconf.service is listed as > a dependency in 4.11.12 and not in the older version. > > $ systemctl list-dependencies samba-ad-dc > ??? ??????system.slice > ??? ??????network-online.target > ??? ??? ??????systemd-networkd-wait-online.service > ??? ??????sysinit.target > ??? ????...

...conf. > <ip for hostname01> hostname01.domain.local hostname01 > >> # more /etc/resolv.conf >> search domain.local >> nameserver 10.0.3.1 > > Is '10.0.3.1' the ipaddress of the AD DC (or something that will get > you to the AD DC ? > It's the resolveconf DNS server on the machine hosting LXC, but yes, it is definitely able to resolve the AD server. Everything seems to work as expected:- # nslookup LOCAL_AD03.domain.local Server: 10.0.3.1 Address: 10.0.3.1#53 Non-authoritative answer: Name: LOCAL_AD03.domain.local Address: 10.x.x.x # telnet LOC...

...mctl start samba-ad-dc > > then it loads ok. > > > > Is the systemd unit file missing a dependency? I compared the version > > between an AD running 4.10.14 and 4.11.12(this current > > problem machine) and > > the one difference between the two is that > > resolveconf.service is listed as > > a dependency in 4.11.12 and not in the older version. > > > > $ systemctl list-dependencies samba-ad-dc > > ??? ??????system.slice > > ??? ??????network-online.target > > ??? ??? ??????systemd-networkd-wait-online.service > > ??? ??...

I'm inclined to agree with you regarding resolveconf, but I don't think that's the issue here, clearly it was able to get the name and 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&...

...; Aan: samba at lists.samba.org >> Onderwerp: Re: [Samba] Windows pre-requisites for login with winbind? >> >> On Mon, 21 Aug 2017 17:13:12 +0000 >> "A. James Lewis" <james at fsck.co.uk> wrote: >> >> I'm inclined to agree with you regarding resolveconf, but I don't >> think that's the issue here, clearly it was able to get the >> name and >> 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,...

...mba at lists.samba.org >> Onderwerp: Re: [Samba] Windows pre-requisites for login >> with winbind? >> >> On Mon, 21 Aug 2017 17:13:12 +0000 >> "A. James Lewis" <james at fsck.co.uk> wrote: >> >> I'm inclined to agree with you regarding resolveconf, but I don't >> think that's the issue here, clearly it was able to get >> the name and >> 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...

Also, 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