I have two domain controllers, DC1 and DC2. DC2 is a new DC and is having problems becoming a full DC because it cannot replicate through the File Replication Service. DC1 is a MS server 2008 + DNS and DC2 is a virtual MS server 2003 + DNS. Using net share on DC2 shows that SYSVOL and NETLOGON shares are missing.
The Event Viewer, File Replication Service, on DC2, indicates a 13508 error every hour.
I have tried the following on both DCs:
netdiag /fix -no errors except domain controller failure on DC2
dcdiag /test:frsevent -error is, DC2 failed test frsevent
ntfrsutl version DC1 ntfrsutl sets -this test indicates LastSndStatus: RPC_S_SERVER UNAVAILABLE
If I try to force replication from AD Sites and Services of DC2, I get an error, The naming context is in the process of being removed or is not replicated from the specified server.
This server, DC2, has been operating for several weeks, and nobody noticed it had not finished the DCPROMO cycle. I was going to demote it and try again, but it wont demote gracefully because it is not yet a full DC. So rather than the hassle of a forced demotion I thought I would try and fix it.
We have checked all the obvious things, like firewall, routers, anything that might block RPC. Using Event Viewer and connecting to another computer works both ways from DC2, but not from any other computer to DC2. The error reported is : The RPC server is unavailable. It has been my experience that almost all of these kinds of errors are traceable to a faulty DNS installation but I cant find anything wrong with the DNS.
I was hoping that maybe someone at Experts Exchange might have an answer we have overlooked. We are willing to try anything to resolve this problem.
Thank you
Brian
|
