similar to: Error joining Samba 4.7.4 DC to existing Win2008R2 domain

Thanks for your help. > On the Windows DC can you check that the A record is actually created? Yes, it is, and it persists after join failure. Another sign of presence of SRVAD-NEW on the old DC is the new computer account, created in "Domain controllers" folder in "Active Directory Users and Computers" at the beginning of join procedure then automatically removed just

On Fri, 2 Mar 2018 11:43:37 +0100 Claudio Nicora via samba <samba at lists.samba.org> wrote: > If I create SRVAD-NEW DNS record manually, under samdom.local zone, > this is what I see with adsiedit: > > distinguishedName: > DC=SRVAD-NEW,DC=samdom.local,CN=MicrosoftDNS,DC=ForestDnsZones,DC=SAMDOM,DC=LOCAL > There is a bit of a problem with that, it should be:

Can you specify the full DN of the DNS record in question? Afterwards, maybe you can also try deleting that DNS record and retry the join? Failed to find machine account is almost certainly an unrelated debug message. I don't think it has any relation to your issue. Cheers, Garming On 26/02/18 00:28, Claudio Nicora via samba wrote: > Tried again to join, now with full cleanup of

It seems I'm talking to myself... anyway another test here: Added the existing DC IP config to /etc/hosts and the join now shows a more explicit LDAP error: --- Wrong username or password: kinit for SRVAD-NEW$@SAMDOM.LOCAL failed (Preauthentication failed) SPNEGO(gssapi_krb5) creating NEG_TOKEN_INIT for ldap/SRVAD-OLD.SAMDOM.LOCAL failed (next[ntlmssp]): NT_STATUS_LOGON_FAILURE Got

Tested again to join, now clearing both Kerberos, Samba config and Samba private folder. The new log now has some more details (resolve_lmhosts: Attempting lmhosts lookup for name SRVAD-OLD.SAMDOM.LOCAL<0x20>), but I'm still not able to join. Wonder why is it trying to do an lmhosts lookup, 4.6 is not. An identical server (with same hostname and IP) with Samba 4.6 joins without

Tested again to join, now clearing both Kerberos, Samba config and Samba private folder. The new log now has some more details (resolve_lmhosts: Attempting lmhosts lookup for name SRVAD-OLD.SAMDOM.LOCAL<0x20>), but I'm still not able to join. Wonder why is it trying to do an lmhosts lookup, 4.6 is not. An identical server (with same hostname and IP) with Samba 4.6 joins without

Tried again to join, now with full cleanup of /var/lib/samba/private folder on new server... same error. Anyone have an idea of what's going wrong? Il 23/02/2018 09:52, Claudio Nicora via samba ha scritto: > Thanks for your help. > >> On the Windows DC can you check that the A record is actually created? > > Yes, it is, and it persists after join failure. > Another

Thanks for the time you're dedicating to solving my issue. > Is your WORKGROUP really the same as your dnsdomain ? > So, the command should be: > samba-tool domain join samdom.local DC -U Administrator --dns-backend=BIND9_DLZ --verbose -d3 I've replaced log sensitive data before posting it (replacing real domain name with SAMDOM), but replace was case-insensitive so

This could be the right way... > There is a bit of a problem with that, it should be: > > DC=SRVAD-NEW,DC=samdom.local,CN=MicrosoftDNS,DC=DomainDnsZones,DC=SAMDOM,DC=LOCAL The SAMDOM.LOCAL zone is set to replicate to the whole forest (maybe I've missed that info on DNS config, anyway Domain-only replication is ok for me too). I've changed it to replicate to only Domain DNS and

On Fri, 2 Mar 2018 15:15:49 +0100 Claudio Nicora <claudio.nicora at gmail.com> wrote: > This could be the right way... > > There is a bit of a problem with that, it should be: > > > > DC=SRVAD-NEW,DC=samdom.local,CN=MicrosoftDNS,DC=DomainDnsZones,DC=SAMDOM,DC=LOCAL > The SAMDOM.LOCAL zone is set to replicate to the whole forest (maybe > I've missed that info

On Fri, 2 Mar 2018 16:15:43 +0100 Claudio Nicora <claudio.nicora at gmail.com> wrote: > > > Is bind9 running during the join ? > > How have you set up bind ? > No it's not. > Following the doc here > https://wiki.samba.org/index.php/BIND9_DLZ_DNS_Back_End > I see than the needed files (like /var/lib/samba/private/named.conf > and

On the Windows DC can you check that the A record is actually created? > Adding DNS A record SRVAD-NEW.SAMDOM.LOCAL for IPv4 IP: 10.0.3.100 It appears that the record is added over RPC, but then fails to find it over LDAP. Presumably they are to the same domain controller, so you should be able to see if there is a record in the domain DNS zone. Maybe there is a race here, but that seems a

Thanks for your attention > You are always receiving these: > > Adding DNS A record SRVAD-NEW.SAMDOM.LOCAL for IPv4 IP: 10.0.3.100 > Join failed - cleaning up Yes, but the DNS record is created and it persists after the failure. Another thing I've noticed using RSAT "Active Directory Users and Computers" is that the new DC computer account SRVAD-NEW$@SAMDOM.LOCAL is

On Fri, 2 Mar 2018 16:48:26 +0100 Claudio Nicora <claudio.nicora at gmail.com> wrote: > > > No, I was just checking if you where something you shouldn't, like > > creating the zone files in the Bind configs. > Good, it's better to clear out any doubt. > > > There doesn't seem to be anything wrong in any of your conf files, > > the only other

On Sun, 4 Mar 2018 00:14:48 +0100 Claudio Nicora <claudio.nicora at gmail.com> wrote: > > > And I can now confirm that 4.7.4 on the latest Ubuntu 18.04 snapshot > > joins to a Samba AD domain as a DC. > I'm sure it does, that's why I suspect something is wrong in my > Win2000-->Win2008R2 upgraded domain AD. > > > Another thing that comes to my

Il 05/03/2018 09:55, denis.shigapov via samba ha scritto: > Hi, run please to Windows DC command > dcdiag Already did it, both plain dcdiag and dcdiag /test:DNS. Nothing interesting in the output except for a warning at the end of /test:dns execution (Warning: Failed to delete the test record dcdiag-test-record in zone SAMDOM.LOCAL): ================= PS C:\Users\Administrator.SAMDOM>

> Garming asked you to see if you could locate > where the records got put the records by hand Sorry, I can't understand what you mean with "if you could locate where the records got put"... Are you're asking me to create the DNS record by hand with RSAT on SRVAD_OLD, then run samba-tool join again? If so, yes I've tried to create the record manually and re-run

Hi list, i removed my second DC from the domain, and now the re-join as DC hangs. the join hangs now for ca. 2 hours at the step "Committing SAM database" version: samba 4.5.0 on ubuntu 14.04 with a "strace -p " i see this: strace -p 1793 Process 1793 attached brk(0x35e18000) = 0x35e18000 brk(0x35e39000) = 0x35e39000

You are always receiving these: Adding DNS A record SRVAD-NEW.SAMDOM.LOCAL for IPv4 IP: 10.0.3.100 Join failed - cleaning up Questions: 1) Prior to the join, dos a kinit -V5 ADMINISTRATOR at SAMDOM.LOCAL works? 2) Can you create DNS entries without issues with your administrator account? 3) Can you do a test and join your samba server as a normal computer? Does it work? Regards, Vinicius. Em

If I create SRVAD-NEW DNS record manually, under samdom.local zone, this is what I see with adsiedit: distinguishedName: DC=SRVAD-NEW,DC=samdom.local,CN=MicrosoftDNS,DC=ForestDnsZones,DC=SAMDOM,DC=LOCAL In "Active Directory Users and Computers" under "Domain Controllers" I see this object (that disappears after failure): distinguishedName: CN=SRVAD-NEW,OU=Domain