search for: local_ad03

...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 LOCAL_AD03.domain.local 88 Trying 10.x.x.x... Connected to LOCAL_AD03.domain.local. Escape character is '^]'. Connection closed by foreign host. # getent...

...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 LOCAL_AD03.domain.local 88 >> Trying 10.x.x.x... >> Connected to LOCAL_AD03.dom...

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