search for: testing_dns_name_resolut

...s. This one was > easy to fix by adding the domain to /etc/krb5.conf. I am putting this in as I > changed configuration at this point.. > Working. In essence, the windows member is unable to use any information from Samba. The lookup described in https://wiki.samba.org/index.php/Testing_DNS_Name_Resolution does work and reports both dcs as expected. I checked the Windows system log. There is some noise about group policies and missing updates of the host address. The most relevant record shows: "This computer was not able to set up a secure session with a domain controller in domain SAMBA due...

I'm following the instructions here -- https://wiki.samba.org/index.php/Setup_a_Samba_Active_Directory_Domain_Controller I've successfully "tested" my domain controller -- adam at eagle:~$ smbclient -L localhost -U% Domain=[SMBDOMAIN] OS=[Unix] Server=[Samba 4.1.18-Debian] Sharename Type Comment --------- ---- ------- netlogon

To regenerate dns.keytab I expect you only need to relaunch samba_upgradedns --dns-backend=BIND9_DLZ. If I'm wrong (it happens quiet often) you would have to first launch: samba_upgradedns --dns-backend=SAMBA_INTERNAL and then samba_upgradedns --dns-backend=BIND9_DLZ Here you should have a dns.keytab. Now, right issues: dns related files in samba/private must be accessible to the UNIX user