samba - Jun 2020 - Samba as a domain member:

Sorry, "encrypt passwords" was added by mistake. I see it is
deprecated now.

In any case, even without removing it, I decided to remove the member
from the domain and added it again as I saw other posts with similar
issues. I ran a "net ads leave" followed by a "net ads join"
again,
and after the message that it had joined successfully, now wbinfo -t
and the likes work fine.

The only difference I can see with the failing scenario is that "net
ads info" showed a different AD server (there are 3 in my network).

I am unable to reproduce the problem. I am trying to join specifically
to the PDC that was supposedly failing (with the -S or -I options),
but "net ads join" still shows the "working" PDC.

So, I can't say why it failed the first time, and I can't make it fail
again.
I guess I'll keep in mind that leaving and joining again may help in
case I get into trouble again.

Thanks,

Vieri

On 15/06/2020 10:33, Vieri Di Paola via samba wrote:
> The only difference I can see with the failing scenario is that "net
> ads info" showed a different AD server (there are 3 in my network).
That is how it is supposed to work.
> I am unable to reproduce the problem. I am trying to join specifically
> to the PDC that was supposedly failing (with the -S or -I options),
> but "net ads join" still shows the "working" PDC.
Will you please stop calling it a 'PDC', it isn't a PDC, that is 
something quite different. All AD DC's are equal except for the FSMO 
roles and they can be on any DC. There really isn't a concept of 
primary, secondary or backup AD DC's, they are all just DC's.

Samba will use what it thinks is the best DC and this might not be 
always the same DC.

Rowland