We have three remote sites each with a domain controller. Two sites have Server 2008 R2, one new and one a few months old, and the other has Server 2003. We also have two Server 2008 R2 domain controllers at the main site. All servers are in the same domain. Every thing was working well until I promoted the newest Server 2008 R2 at one of the remote sites to a domain controller. After promoting the server I started getting two errors every 15 minutes on the three remote sites. I get no errors at the main site. The error IDs are 1311 and 1865. I have confirmed that all servers are still replicating, but I am still getting these errors. I did this by creating a user account and then checking to insure that it was replicated to the other servers. I have done what has been suggested in attempting to fix these errors, but does not seem to work. I am to the point of possibly demoting the new server and re-promoting it again. Is there anything else I could try other than the demoting/promoting of the server? Thank you

We have three remote sites each with a domain controller. Two sites have Server 2008 R2, one new and one a few months old, and the other has Server 2003. We also have two Server 2008 R2 domain controllers at the main site. All servers are in the same domain. Every thing was working well until I promoted the newest Server 2008 R2 at one of the remote sites to a domain controller. After promoting the server I started getting two errors every 15 minutes on the three remote sites. I get no errors at the main site. The error IDs are 1311 and 1865. I have confirmed that all servers are still replicating, but I am still getting these errors. I did this by creating a user account and then checking to insure that it was replicated to the other servers. I have done what has been suggested in attempting to fix these errors, but does not seem to work. I am to the point of possibly demoting the new server and re-promoting it again. Is there anything else I could try other than the demoting/promoting of the server? Thank you Have you configured AD Sites and Services properly for those sites before promtly after promoting the DC? Here are a few troubleshooting articles from the TechNet Library that correlate to resolving these issues. KCC Replication Path Computation Event IDs (1311, 1312, 1473, 1664, 1865) http://technet.microsoft.com/en-us/library/cc756582(WS.10).aspx EVENT ID 1865 - KCC Replication Path Computation http://technet.microsoft.com/en-us/library/cc756648(WS.10).aspx The Event ID 1311 states that it can be flagged as a result from impacts of the original issue pertaining to KCC errors (1865)... so resolving the 1865 issue with the mentioned troubleshooting steps mentioned in the Event ID article may help resolve this issue. Steve Kline Microsoft Certified IT Professional: Server Administrator Microsoft Certified Technology Specialist: Active Directory, Network Infrastructure, Application Platform, Windows 7 Microsoft Certified Product Specialist & Network Product Specialist Red Hat Certified System Administrator This posting is "as is" without warranties and confers no rights.

Thank you Mr. Kline for taking the time to look at this issue. I have looked at both of those articles previously. They had a lot of good information but I was unable to resolve the issue with it. I am fairly sure that I was able to get that server set up correctly in Sites and Services. When I did the other 2008 server I had a similar problem, but was able to get it figured out. This one seems to be giving me more problems though. I want the all of the remote servers to replicate to and from the server at the main site. Since I have introduced this last server it seems to want to connect with all of the domain controllers.

Hello, if this problem still exist please upload the following files: ipconfig /all >c:\ipconfig.txt [from each DC/DNS Server] dcdiag /v /c /d /e /s:dcname >c:\dcdiag.txt repadmin /showrepl dc* /verbose /all /intersite >c:\repl.txt ["dc* is a place holder for the starting name of the DCs if they all begin the same (if more then one DC exists)] dnslint /ad /s "DCipaddress" (http://support.microsoft.com/kb/321045) As the output will become large, DON'T post them into the thread, please use Windows Sky Drive (skydrive.live.com) [with open access!] and add the link from it here. Also the /e in dcdiag scans the complete forest, so better run it on COB.Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

Thank you for responding Mr. Weber. My boss will not allow that I post the logs. I have run them and I do see some errors. I know this is not very helpful, but my hands are tied on this. I have demoted and re-promoted the server. Now this server is not replicating at all.

Thank you for responding Mr. Weber. My boss will not allow that I post the logs. I have run them and I do see some errors. I know this is not very helpful, but my hands are tied on this. I have demoted and re-promoted the server. Now this server is not replicating at all. Hello, without having a look into the errors helping you is not really possible. Keep in mind that the private ip ranges 10.x.x.x, 192.168.x.x and 172.16.x.x are NOT accessible from the internet so this isn't a real problem for your security. WAN ip addresses you can replace with x.x.x.x and used machine names if you care about can be renamed, also domain names, just keep the format. Maybe this your boss will agree on. Demoting and promoting a DC is not really a solution if you don't know what's going on and result in additional problems as you see now. Please open a support call with Microsoft, they can go remote into your system and check the problems, of course this calls are NOT for free like the forums.Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

I want to thank the both of you for your assistance on this. I did talk to my boss and he would not allow me to post the log files. I realize that this really hampered how much assistance you could offer. I think I figured it now, though with my limited knowledge of this I am not sure why it worked. I had this happen one other time and did the opposite of what I did this time and it went away. Last time I had removed the site with primary domain controller from the Inter-site Transports connection properties in the Sites in this site link section. This time I put it back in and the errors stopped. Thank you again

possible to execute MPSreport.exe You can download the tool from microsoft.com Kindly post the results via sky drive. for diagnostics troubleshooting purposes :)Guowen Su | CCNA, CCIP, MCP, MCSA, MCSE, MCTS, MCITP, CEH | http://www.microsoft.com/en/sg/default.aspx Our Goal? VERY SATISFIED Customers. If you're not...let's talk!!