[Samba] Member can't join DC2 (The specified network name is no longer available)

[Rowland Penny]

On Wed, 23 Apr 2025 14:53:37 +0200
"Adnan R. via samba" <samba at lists.samba.org> wrote:

> Le 23/04/2025 à 14:07, Luis Peromarta via samba a écrit :
> > I understand DC2 has been powered off but not demoted from AD ?
> 
> Yes, I reinstalled multiple times DC2 without demoting it. At first
> as a member (named DC2), then as a full DC once or twice. THEN before 
> installing DC4, I demoted DC2, removed the references, checked the 
> GUIDs, etc… And cleaned manually the left overs in the DNS.
> 
> Currently, DC2 is a clean install after being demoted. DC4 is an
> attempt to create a new DC without previous reference (I wondered if
> the errors with DC2 could come from the mistakes with it). DC4 is a
> first install and first join with a new hostname.
> 
> > Also, have you used RSAT sites and services to create your 2 sites ?
> 
> Yes, the sites were already created when I created DC1. 10.190.0.0/16
> is on site 1, 10.133.0.0/16 on site 2. I don't use the "sites" for
> anything else nor I configured anything related to sites except their
> network.

If all you have done is to setup a subnet at each place, then you are
not using sites, you are just using different ip's at each place.
 
Best practice would be to run two DC's at each place, set up 'sites and
services' at each place, you could call the place where your first DC
is 'siteA' and the other place could be 'siteB'

As you are running your DCs in VM's, you must ensured that they are
privileged VM's, that is 'root' really is 'root', it will not work
otherwise.

Rowland