[Samba] Problems joining station in domain

[L.P.H. van Belle]

Good day Andrew, 

Thank you for your quick responce on this. 

> -----Oorspronkelijk bericht-----
> Van: Andrew Bartlett [mailto:abartlet at samba.org] 
> Verzonden: woensdag 28 augustus 2019 10:15
> Aan: L.P.H. van Belle; samba at lists.samba.org
> Onderwerp: Re: [Samba] Problems joining station in domain
> 
> On Wed, 2019-08-28 at 10:08 +0200, L.P.H. van Belle via samba wrote:
> > Hai, 
> > 
> > I re-checked your config that looks all good, few minor things. 
> > 
> > Now, i noticed this in Andrews comment. 
> > Quote: 
> > The problem here is that Samba's python libraries are trying to find
> > the DNS record they just added over RPC, but can't using 
> LDAP.  They do
> > this to fix the ownership of the records, as otherwise they will be
> > owed by the administrator, not the DC.
> 
> The relevance is that, as mentioned, the domain started with Windows. 
> We have a problem there, which is why the extreme measure of joining
> with a really old version was needed.

Yes, i know. I hoped, that the join part with DLZ works out differently. 
So if i understand it right and i found a few older threads on this. 

Then we are left with the 2 possible workarounds as mentions in the list before. 
See: https://www.spinics.net/lists/samba/msg158588.html
Adjust the code of samba a bit. 

Dennis pointed out, and option to upgrade/create partitions on w2k3 before the joins. 
Found here: https://lists.samba.org/archive/samba/2019-July/224515.html
But as far i know that server is gone. 

The last option is this bug to be fixed.

Why i posted the last parts, so you understand my thoughts. 
Before i want to try these, i want to be sure the other parts are all checked. 
I was hoping to find that a join with bind9_dlz would help out. I dont know that. 

But if you really sure it is not, please tell, then im left without options, 
and then is up too you guys. Do you want a bug report on it? 

Looks like this one is releated: 
https://bugzilla.samba.org/show_bug.cgi?id=14045 


> 
> Sadly that now means that the domain is in a slightly different
> arrangement to what we expect, and no amount of fiddling settings will
> fix it, it is 'just' a code bug/db layout issue.
> 
> Sorry!
Well, nothing to be sorry about, but maybe its time to start a bughunt on this one, 
because this should get a higher. 

You guys to that fast, i can follow all changes, i try to but that hard todo.

Thank you (again) so far. 

Greetz,

Louis