• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 545
  • Last Modified:

DCDIAG - replication errors

hi experts,

using windows 2003 server (standard w/ Service Pack 1). Two sites (Site A & B) and one DC per site (ie DC01 at Site A and DC02 at Site B)

ive attached the dcdiag test results. please advise on how to proceed with resolving replication errors.

thanks in advance
check.txt
0
kenny_klbn
Asked:
kenny_klbn
1 Solution
 
NarendraGCommented:
seems to be link problem with machine account try this

http://support.microsoft.com/kb/260575/EN-US/
0
 
NarendraGCommented:
0
 
Mike KlineCommented:
Anything happen in early Oct on your network that may have caused this?
In this case you are running up on that 90 day period since the last success so once you go over the tombstone lifetime you really don't have much of a choice.
I'd remove AD from this DC and repromote

1.  Run dcpromo /forceremoval. That will remove AD from the server without replicating (replication is not working anyway).  After the reboot the server will be a standalone box.
2.  Run a metadata cleanup of the DC that was demoted
http://www.petri.co.il/delete_failed_dcs_from_ad.htm & http://msmvps.com/blogs/ad/archive/2008/12/17/how-to-remove-a-failed-or-offline-dc.aspx   
Those are my two favorite metadata links
 In your case DC2 doesn't hold any FSMO roles so you don't need to seize them.
 3.  You can then join the server back to the domain and promote it again.
 Thanks
Mike
0
 
Glen KnightCommented:
What is DC01? Is it still active?

If they are on different sites is there good communication between the sites?

Are they both DNS servers?
0
 
ARK-DSCommented:
HI,
Replication can break due to various reasons like name resolution etc. Now, if two DCs do not replicate with each other for more than 30 days, the chances are there that the two machines are not able to access each other. As, every windows based machine changes its machine account's password every 30 days. If its not replicating with other DCs, this password will not replicate with them and hence will result in this situation.
Resolution:
Just follow this article and run NetDom command as specified in this:
http://support.microsoft.com/kb/260575

IMP: You have to do this on PDC first in its own context. Then do it on the other server with PDC's context. So, run this command on both servers (but first on PDC).
Netdom /resetpwd /server:PDC_NAME /Userd:Domain\user_name /passwordd:"password"

Regards,

Arun.


0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now