This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(252.8, 51%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EIK%3C/text%3E%3C/svg%3E)
i have multiple additional domain controller which replicate through sites link all work fine but active directory check site topology not auto generated .
even though all the network ports allowed.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
You could check things out via PowerShell.
--please don't forget to upvote and Accept as answer if the reply is helpful--
My issue is topology is not generating automatically.
Not much to go on but you could confirm the ports are open and flowing between networks.
--please don't forget to upvote and Accept as answer if the reply is helpful--
all the ports are open between those sites , what if i add the site connections mannuly? what is the consequence?
Ok gotcha now. You could run
repadmin /kcc *
and see if it can generate the topology based on the AD sites and services configuration.
after running the cmd still site not generated .
What errors are present in the System and DFS Replication event logs?
there is no error for that.
If the Active Directory check site topology is not generating automatically despite having multiple additional domain controllers replicating through site links, here are some potential solutions:
1) Verify replication settings: Check the configurations of site links, replication schedules, and intervals to ensure they are set up correctly.
2) Check network connectivity: Ensure uninterrupted network connectivity between domain controllers by testing and resolving any network or firewall issues.
3) DNS configuration: Confirm that DNS settings on all domain controllers are accurate and functioning properly.
4) Force replication: Attempt to trigger the Active Directory check site topology by forcing replication between domain controllers using the command "repadmin /syncall /AdeP".
5) Monitor event logs: Check the event logs on domain controllers for relevant error messages or warnings related to replication or Active Directory.
6) Verify site topology settings: Double-check the accuracy of site topology settings in Active Directory Sites and Services, including sites, subnets, and site link configurations.
If the issue persists, consider seeking assistance from a system administrator or Active Directory specialist for further analysis and targeted troubleshooting.
The 5014 error may provide some clues.
that is one of site which not able to replicate but my issue for other 10 sites site topology is not generating automatically , even though cmd repadmin /kcc * runs successfully for all sites
Yes, we know. We're still looking for clues as to why but so far you have not provided anything helpful to work with. Another option for you is to start a case here with product support.
https://support.serviceshub.microsoft.com/supportforbusiness
--please don't forget to upvote and Accept as answer if the reply is helpful--
even though dcdiag also shows no error , what if i add site topology manually?
Something here could help.
https://theitbros.com/active-directory-sites-and-subnets/
--please don't forget to upvote and Accept as answer if the reply is helpful--
in directory service event its showing this warning "This directory server has not received replication information from a number of directory servers in other sites within the configured latency interval.
"
We can only guess at this point but most likely cause is the required ports are blocked at some point in the site-to-site connections.
--please don't forget to upvote and Accept as answer if the reply is helpful--