samba - Apr 2025 - Member can't join DC2 (The specified network name is no longer available)

Nah, just I have been fighting it longer than you.

I can?t really get anything conclusive from your logs. Are they truncated ?

I just say I feel it?s a bad idea having an unknown state DC in an AD, and even
if it was good I don?t think it?s a good idea to have it permanently off I?m
shire there?ll be sync issues.

I?d demote it. You run a hypervisor. Get a snapshot of everything while turned
off if you want to fever back.



On 23 Apr 2025 at 21:38 +0100, aere_premium.0k at icloud.com, wrote:

> You probably know Samba a lot better than I do, but according to the
> logs in my first message, Windows seems to find and try to connect to
> DC4. Could DC2 still mess with the whole thing ?
>

On Wed, 23 Apr 2025 21:42:39 +0100
Luis Peromarta via samba <samba at lists.samba.org> wrote:
> Nah, just I have been fighting it longer than you.
> 
> I can?t really get anything conclusive from your logs. Are they
> truncated ?
> 
> I just say I feel it?s a bad idea having an unknown state DC in an
> AD, and even if it was good I don?t think it?s a good idea to have it
> permanently off I?m shire there?ll be sync issues.
> 
> I?d demote it. You run a hypervisor. Get a snapshot of everything
> while turned off if you want to fever back.
> 
The problem with turning off a DC and leaving it off for a period of
time is replication. Any other DC's will try to replicate to the DC
that is turned off and there is always the chance of accounts
etc that have been deleted on the running DCs reappearing when the DC
is turned back on again.

If you are going to turn off a DC for any length of time, then, in my
opinion, you should demote it.

Rowland