Hi, on my windows 2003 I have lots of this warning messages please help me to resolve this issue details are as follow: Source: NtFrs, Event ID: 13508, Description: The File Replication Service is having trouble enabling replication from WINSRVDC03 to WINSRVDC01 for c:\windows\sysvol\domain using the DNS name winsrvdc03.chaseevans.ad. FRS will keep retrying. Following are some of the reasons you would see this warning. [1] FRS can not correctly resolve the DNS name winsrvdc03.chaseevans.ad from this computer. [2] FRS is not running on winsrvdc03.chaseevans.ad. [3] The topology information in the Active Directory for this replica has not yet replicated to all the Domain Controllers. This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that

Hello,sounds that you have a domain with at least 2 Domain controllers and that on this machine replciation is not working correct. For starting see here:http://technet.microsoft.com/en-us/library/bb727056.aspxIf it doesn't help, please describe more detailed your network, amount of DCs,domains, sitesand how they are located/connected. Also give some information about SP/patch level and if the DCs are installed from images(sysprepped or not) or fresh from installation media.Did something happen before this starts, crash, restore from backup etc.?Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.

In addition to Meinolf suggestion. are these DC located locally or they do exists on different places ?? Is there any WAN link ot the Firewall between them ? According to the description WINSRVDC03 to WINSRVDC01 its very clear the these both DC's are not replicating to each other.Can you please post the dcdiag /v report on the forum for both the servers ? as it might be bit easy for troubleshooting the issue.Lingering objects and incorrect configuration of the dns might also be a problem.http://support.microsoft.com/default.aspx/kb/317097.Thankshttp://technetfaqs.wordpress.com

We have 3 domain controller for 3 diffrent offices and here is the requested dcdiag /v output as you requested. --------------------- An Warning Event occured. EventID: 0x80000749 Time Generated: 07/02/2009 14:37:41 Event String: 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=PanPen,CN=Sites,CN=Configuration,DC=abccompany,DC=ad An Warning Event occured. EventID: 0x8000061E Time Generated: 07/02/2009 14:37:41 Event String: All domain controllers in the following site that can replicate the directory partition over this transport are currently unavailable. Site: CN=PanPen,CN=Sites,CN=Configuration,DC=abccompany,DC=ad Directory partition: DC=DomainDnsZones,DC=abccompany,DC=ad Transport: CN=IP,CN=Inter-Site Transports,CN=Sites,CN=Configuration,DC=abccompany,DC=ad An Error Event occured. EventID: 0xC000051F Time Generated: 07/02/2009 14:37:41 Event String: The Knowledge Consistency Checker (KCC) has detected problems with the following directory partition. Directory partition: DC=DomainDnsZones,DC=abccompany,DC=ad There is insufficient site connectivity information in Active Directory Sites and Services for the KCC to create a spanning tree replication topology. Or, one or more domain controllers with this directory partition are unable to replicate the directory partition information. This is probably due to inaccessible domain controllers. User Action Use Active Directory Sites and Services to perform one of the following actions: - Publish sufficient site connectivity information so that the KCC can determine a route by which this directory partition can reach this site. This is the preferred option. - Add a Connection object to a domain controller that contains the directory partition in this site from a domain controller that contains the same directory partition in another site. If neither of the Active Directory Sites and Services tasks correct this condition, see previous events logged by the KCC that identify the inaccessible domain controllers. An Warning Event occured. EventID: 0x80000749 Time Generated: 07/02/2009 14:37:41 Event String: 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=PanPen,CN=Sites,CN=Configuration,DC=abccompany,DC=ad An Warning Event occured. EventID: 0x8000061E Time Generated: 07/02/2009 14:37:41 Event String: All domain controllers in the following site that can replicate the directory partition over this transport are currently unavailable. Site: CN=PanPen,CN=Sites,CN=Configuration,DC=abccompany,DC=ad Directory partition: DC=ForestDnsZones,DC=abccompany,DC=ad Transport: CN=IP,CN=Inter-Site Transports,CN=Sites,CN=Configuration,DC=abccompany,DC=ad An Error Event occured. EventID: 0xC000051F Time Generated: 07/02/2009 14:37:41 Event String: The Knowledge Consistency Checker (KCC) has detected problems with the following directory partition. Directory partition: DC=ForestDnsZones,DC=abccompany,DC=ad There is insufficient site connectivity information in Active Directory Sites and Services for the KCC to create a spanning tree replication topology. Or, one or more domain controllers with this directory partition are unable to replicate the directory partition information. This is probably due to inaccessible domain controllers. User Action Use Active Directory Sites and Services to perform one of the following actions: - Publish sufficient site connectivity information so that the KCC can determine a route by which this directory partition can reach this site. This is the preferred option. - Add a Connection object to a domain controller that contains the directory partition in this site from a domain controller that contains the same directory partition in another site. If neither of the Active Directory Sites and Services tasks correct this condition, see previous events logged by the KCC that identify the inaccessible domain controllers. An Warning Event occured. EventID: 0x80000749 Time Generated: 07/02/2009 14:37:41 Event String: 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=PanPen,CN=Sites,CN=Configuration,DC=abccompany,DC=ad An Warning Event occured. EventID: 0x8000061E Time Generated: 07/02/2009 14:37:41 Event String: All domain controllers in the following site that can replicate the directory partition over this transport are currently unavailable. Site: CN=PanPen,CN=Sites,CN=Configuration,DC=abccompany,DC=ad Directory partition: CN=Configuration,DC=abccompany,DC=ad Transport: CN=IP,CN=Inter-Site Transports,CN=Sites,CN=Configuration,DC=abccompany,DC=ad An Error Event occured. EventID: 0xC000051F Time Generated: 07/02/2009 14:37:41 Event String: The Knowledge Consistency Checker (KCC) has detected problems with the following directory partition. Directory partition: CN=Configuration,DC=abccompany,DC=ad There is insufficient site connectivity information in Active Directory Sites and Services for the KCC to create a spanning tree replication topology. Or, one or more domain controllers with this directory partition are unable to replicate the directory partition information. This is probably due to inaccessible domain controllers. User Action Use Active Directory Sites and Services to perform one of the following actions: - Publish sufficient site connectivity information so that the KCC can determine a route by which this directory partition can reach this site. This is the preferred option. - Add a Connection object to a domain controller that contains the directory partition in this site from a domain controller that contains the same directory partition in another site. If neither of the Active Directory Sites and Services tasks correct this condition, see previous events logged by the KCC that identify the inaccessible domain controllers. An Warning Event occured. EventID: 0x80000749 Time Generated: 07/02/2009 14:37:41 Event String: 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=PanPen,CN=Sites,CN=Configuration,DC=abccompany,DC=ad ......................... WINSRVDC02 failed test kccevent Starting test: systemlog * The System Event log test Found no errors in System Event log in the last 60 minutes. ......................... WINSRVDC02 passed test systemlog Test omitted by user request: VerifyReplicas Starting test: VerifyReferences The system object reference (serverReference) CN=WINSRVDC02,OU=Domain Controllers,DC=abccompany,DC=ad and backlink on CN=WINSRVDC02,CN=Servers,CN=CanaryWharf,CN=Sites,CN=Configuration,DC=ch aseevans,DC=ad are correct. The system object reference (frsComputerReferenceBL) CN=WINSRVDC02,CN=Domain System Volume (SYSVOL share),CN=File Replicatio n Service,CN=System,DC=abccompany,DC=ad and backlink on CN=WINSRVDC02,OU=Domain Controllers,DC=abccompany,DC=ad are correct. The system object reference (serverReferenceBL) CN=WINSRVDC02,CN=Domain System Volume (SYSVOL share),CN=File Replicatio n Service,CN=System,DC=abccompany,DC=ad and backlink on CN=NTDS Settings,CN=WINSRVDC02,CN=Servers,CN=CanaryWharf,CN=Sites,CN=Co nfiguration,DC=abccompany,DC=ad are correct. ......................... WINSRVDC02 passed test VerifyReferences Test omitted by user request: VerifyEnterpriseReferences Test omitted by user request: CheckSecurityError Running partition tests on : DomainDnsZones Starting test: CrossRefValidation ......................... DomainDnsZones passed test CrossRefValidation Starting test: CheckSDRefDom ......................... DomainDnsZones passed test CheckSDRefDom Running partition tests on : ForestDnsZones Starting test: CrossRefValidation ......................... ForestDnsZones passed test CrossRefValidation Starting test: CheckSDRefDom ......................... ForestDnsZones passed test CheckSDRefDom Running partition tests on : Schema Starting test: CrossRefValidation ......................... Schema passed test CrossRefValidation Starting test: CheckSDRefDom ......................... Schema passed test CheckSDRefDom Running partition tests on : Configuration Starting test: CrossRefValidation ......................... Configuration passed test CrossRefValidation Starting test: CheckSDRefDom ......................... Configuration passed test CheckSDRefDom Running partition tests on : abccompany Starting test: CrossRefValidation ......................... abccompany passed test CrossRefValidation Starting test: CheckSDRefDom ......................... abccompany passed test CheckSDRefDom Running enterprise tests on : abccompany.ad Starting test: Intersite Skipping site Default-First-Site-Name, this site is outside the scope provided by the command line arguments provided. Skipping site CanaryWharf, this site is outside the scope provided by the command line arguments provided. Skipping site Docklands, this site is outside the scope provided by the command line arguments provided. Skipping site PanPen, this site is outside the scope provided by the command line arguments provided. ......................... abccompany.ad passed test Intersite Starting test: FsmoCheck GC Name: \\winsrvdc02.abccompany.ad Locator Flags: 0xe00001fc PDC Name: \\winsrvdc01.abccompany.ad Locator Flags: 0xe000037d Time Server Name: \\winsrvdc02.abccompany.ad Locator Flags: 0xe00001fc Preferred Time Server Name: \\winsrvdc01.abccompany.ad Locator Flags: 0xe000037d KDC Name: \\winsrvdc02.abccompany.ad Locator Flags: 0xe00001fc ......................... abccompany.ad passed test FsmoCheck Test omitted by user request: DNS Test omitted by user request: DNS C:\Program Files\Support Tools>

Hello,your dcdiag /v is not complete. Use "dcdiag /v >c:\dcdiag.log" in a command prompt without the quotes to redirect it into a textfile where you can copy the content from. Additional please answer the other questions. Did you check the webpage?Please post also an unedited ipconfig /all from all DCs. Did you configure AD sites and services according to your location setup?Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.

Hello tech558, To troubleshoot the issue, please check the following 1. Check if the DNS of the TCP properties has been pointed to internal DNS server. 2. Verify that FRS service is running on winsrvdc03.chaseevans.ad 3.Please reboot domain controller to run the MPS report to collect the information on both of the PDC and the problematic server that you run. a. Download proper MPS Report tool from the website below. Microsoft Product Support Reports http://www.microsoft.com/downloads/details.aspx?FamilyID=CEBF3C7C-7CA5-408F-88B7-F9C79B7306C0&displaylang=en b. Double-click to run it, if requirement is not met, please follow the wizard to download and install them. After that, click Next, when the "Select the diagnostics you want to run" page appears, select "General", "Internet and Networking" and "Server Components", and then click Next. c. After collecting all log files, choose "Save the results", choose a folder to save <Computername>MPSReports.cab file. You may send the screenshot and the MPSReports to tfwst@microsoft.com Thanks for your co-operation.This posting is provided "AS IS" with no warranties, and confers no rights.

I had the same issue when I added a second domain controller to a single domain controller environment. Simply put, the preferred DNS server entry in the network settings of the original domain controller was set to an external DNS server. To correct the problem, I made sure that the preferred domain controller setting for each domain controller is set to the other server, and that the alternate DNS is set to the localhost 127.0.0.1. So for example, if you have two domain controllers, server1 with IP 10.10.0.5 and server2 with IP 10.10.0.10, server1's preferred DNS should be 10.10.0.10 and the alternate should be 127.0.0.1. Then server2's preferred DNS server should be 10.10.0.5 and the alternate should be 127.0.0.1. I corrected these settings on my domain controller and 5 minutes later the replication started to work normally. Hope this helps.