Unable to access NETLOGON

Question

New server 2019 DC. Forest/domain level 2012r2.

New 2019 DC. NTDS and SYSVOL were set to a separate partition as I was lead to believe that this was better than having it on the system partition. This was done during dcpromo.

This is the first time I have set them on a separate partition.

When going to This PC - map network drive - \new2019dcservername\netlogon, I get an error.

Unable to connect 0x80070043.

Is this a result of the above being on a different partition or something else wrong?

How do I resolve this error while keeping the above on a separate partition?

I am able to do this with existing DC's where the above was set to the default locations.

If I have to move them back to the default c:\windows folders, please provide the cmd, cmdlets needed to do so.

Thanks

Answer 1

You can try a non authoritative sync
https://support.microsoft.com/en-us/help/2218556/how-to-force-an-authoritative-and-non-authoritative-synchronization-fo

--please don't forget to upvote and Accept as answer if the reply is helpful--

Answer 2

Do the shares show up? Please run;

Dcdiag /v /c /d /e /s:%computername% >C:\dcdiag.log
repadmin /showrepl >C:\repl.txt
ipconfig /all > C:\dc1.txt
ipconfig /all > C:\dc2.txt
ipconfig /all > C:\dc3.txt

then put unzipped text files up on [OneDrive][1] and share a link.

Answer 3

It was a single DC environment and the new DC was meant to replace it.

Current DC A. New 2019 DC B.

Trying to change operations master. It says the new server B is the current manager and can't change it when it shows the original DC A.

SYSVOL replication was previously upgraded to DFSR while DC A was the only DC.

Based on my environment, is the below fix recommended for DC A? The 1015 days is the day that the DC before A was demoted, leaving A.

The DFS Replication Event Log.
There are warning or error events within the last 24 hours after the

     SYSVOL has been shared.  Failing SYSVOL replication problems may cause

     Group Policy problems. 
     An error event occurred.  EventID: 0xC0000FAC

        Time Generated: 01/26/2022   22:56:13

        Event String:

        The DFS Replication service stopped replication on the folder with the following local path: C:\Windows\SYSVOL\domain. This server has been disconnected from other partners for 1015 days, which is longer than the time allowed by the MaxOfflineTimeInDays parameter (60). DFS Replication considers the data in this folder to be stale, and this server will not replicate the folder until this error is corrected. 



        To resume replication of this folder, use the DFS Management snap-in to remove this server from the replication group, and then add it back to the group. This causes the server to perform an initial synchronization task, which replaces the stale data with fresh data from other members of the replication group. 

Answer 4

Well beyond the tombstone. You can cleanup the remnants by following along here.
https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/deploy/ad-ds-metadata-cleanup
https://techcommunity.microsoft.com/t5/itops-talk-blog/step-by-step-manually-removing-a-domain-controller-server/ba-p/280564

I would not try adding new ones or making any changes until domain health is 100%

--please don't forget to upvote and Accept as answer if the reply is helpful--

Answer 5

There's no ghost DC's still listed.

Are there any known complications for doing the following?

To resume replication of this folder, use the DFS Management snap-in to remove this server from the replication group, and then add it back to the group. This causes the server to perform an initial synchronization task, which replaces the stale data with fresh data from other members of the replication group.