DFS - Domain System Volume problem

ast-cm 21 Reputation points
2021-09-24T09:02:22.41+00:00

Hi all,

At the moment we have 5 domain controllers. In the past someone deleted a domain controller (Web-ARR) the wrong way. Now we have a problem wit DFS for the sysvol replication.
When I run "Create Diagnostic Report" in DFS management. I see the following error:
DFS Replication cannot replicate with partner Web-ARR due to a communication error.

Communication errors are preventing replication with Web-ARR.

Affected replicated folders: All replicated folders on this server.
Description: DFS Replication cannot replicate with partner Web-ARR due to a communication error. The DFS Replication service used partner DNS name Web-ARR.asterisque.nl, IP address 10.73.2.18, and WINS address Web-ARR but failed with error ID: 1753 (There are no more endpoints available from the endpoint mapper.). Event ID: 5002
Last occurred: vrijdag 24 september 2021 at 02:31:34 (GMT1:00)
Suggested action: Check for network connectivity problems, for troubleshooting RPC issues see RPC KB 839880 and for additional troubleshooting information, see The Microsoft Web Site.

The Web-ARR is no longer member of the domain. When I ran dsquery server -o rdn it was still listed. I tried to cleanup the server metadata with ntdsutil

metadata cleanup: remove selected server
Transferring / Seizing FSMO roles off the selected server.
Removing FRS metadata for the selected server.
Searching for FRS members under "CN=WEB-ARR,OU=Domain Controllers,DC=asterisque,DC=nl".
Deleting subtree under "CN=WEB-ARR,OU=Domain Controllers,DC=asterisque,DC=nl".
The attempt to remove the FRS settings on CN=WEB-ARR,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=asterisque,DC=nl failed because "Element not found.";
metadata cleanup is continuing.
"CN=WEB-ARR,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=asterisque,DC=nl" removed from server "DC-WIJCHEN"

select operation target: list servers in site
Found 5 server(s)
0 - CN=BDC-EINDHOVEN,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=asterisque,DC=nl
1 - CN=DC-WIJCHEN,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=asterisque,DC=nl
2 - CN=DC-LANDGRAAF,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=asterisque,DC=nl
3 - CN=DC-BOERHAAVE,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=asterisque,DC=nl
4 - CN=WHPDC02,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=asterisque,DC=nl

From then on i don't see any reference to Web-ARR but FDS is still complaining about Web-ARR. This server is not listed in DFS management. The other members have all state 2 : Initial sync

Regards,
Carlo

Windows for business Windows Client for IT Pros Directory services Active Directory
Windows for business Windows Server User experience Other
Windows for business Windows Server Storage high availability Other
0 comments No comments
{count} votes

Accepted answer
  1. Anonymous
    2021-09-28T12:41:11.243+00:00

    How can we fix the web-arr issue ? (this DC no longer exists)

    May be able to find something here.
    https://learn.microsoft.com/en-us/sysinternals/downloads/adexplorer

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


11 additional answers

Sort by: Most helpful
  1. Marco Schiavon 76 Reputation points
    2021-09-24T12:19:57.473+00:00

    from Users and Computer delete Web-arr (Domain > Domain Controllers )
    now do the same in Active Directory Sites and Services
    finally, open a cmd with admin right and do :

    ntdsutil
    metadata cleanup
    remove selected server web-arr
    yes
    quit
    quit

    0 comments No comments

  2. Thameur-BOURBITA 36,261 Reputation points Moderator
    2021-09-24T13:05:11.727+00:00

    Hi,

    You should remove all offline domain controllers via metadata cleanup method , once completed you can perform also the sizing of all FSMO hosted on offline DC if needed.

    Once the cleanup is completed , check if the DFS replication is restored. If it's not the case, you can perform a non-authoritative restore on impacted domain controllers, if you still have the same issue you can perform a authoritative restore to reset the sysvol replication:

    Please don't forget to mark helpful reply as answer


  3. Anonymous
    2021-09-25T00:34:19.17+00:00

    This member is waiting for initial replication for replicated folder SYSVOL

    You can try a non-authoritative restore but sounds more like an authoritative restore may be necessary.

    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--


  4. Anonymous
    2021-09-25T17:36:54.01+00:00

    Did what, and what was the result? Also 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
    ipconfig /all > C:\dc4.txt
    ipconfig /all > C:\dc5.txt

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

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.