Hello everyone. Im need of some help trying to resolve an issue Im currently experiencing. I have a parent site with one child domain. The child domain was created a while back ago and all seem well for some time. Now there are really no issues arising due to this, Users are able to login to the child domain without any issues, Intrasite replication within the child domain is functioning fine. Intersite replication is currently failing. DNS configuration for the child domain is a stub zone pointing to the parent domain. On the parent domain, I configured a delegation pointing to one of the servers within child domain. Now there are no clear errors due to this but Im afraid that all these event logs could result in bigger problems. I keep getting tons of event log errors in the parent domain that it cannt replicate shema, configuration and domain information from the child domain. Active directory within the child domain only replicates to active directory domain controllers within the child domain and not across the forest. I keep getting event log errors within the parent domain that state that replication issues exist when replication the schema, configuration and domain information from the child domain. I am aware that global catalog in fact replicates some data to the parent domain controllers in regards to it shema and configuration which is replicated acrross the forest. What could be causing this issues. Please advise how to go about this. Thanks in advance. The Knowledge Consistency Checker (KCC) was unable to form a complete spanning tree network topology. As a result, the following list of sites cannot be reached from the local site. Sites: CN, CHilddomain,CN=Sites,CN=Configuration,DC=test,DC=com

Hello, Create a scondary zone for your parent domain on the child domain and remove the stub zone. Make them active directory integrated dns as well.Isaac Oben MCITP:EA, MCSE

Isaac, I would like to keep the stub on the child domain since it doesnt replicate the all of dns. The reason for using the stub zone is because of bandwitdht issues with that sight. I dont want to overload the site link with DNS transfers.