Re: PDC Is not replicating !!

I'm Sorry, Im just getting a lil confuse.
Currently I have 29 DC and 2 dc is the main DC for the rest of the DC to
connect as trusted domain. Basically the 27 DC is trusted the 2 main DC which
having some problem.

I really have no idea how and what is the safe way to tackle the problem.
I really need step by step advice. I cant afford to screw up either one
server on the replication DC. I have ACE server installed.



"Jorge_de_Almeida_Pinto" wrote:

> "" wrote:
> > Hi there,
> > I have been trying to sort out this issue since last week.
> >
> > Here is my scenerio. After I have ghosted my PDC and BDC
> > server and load it
> > in to my new server. After rebooted my new server the
> > replication is not
> > running at all.
> >
> > I wil not able to browse the server host name but Im able to
> > browse the PDC
> > Via IPaddress
> > Error: \server01 is not accessible
> > Logon Failure: The targer account name is incorrect
> >
> >
> > I have issue command repadmin / showrep
> >
> > Error:
> >
> > C:WINNTProfilesAdministrator>repadmin /showreps
> > RedbusSERVER01
> > DSA Options : IS_GC DISABLE_INBOUND_REPL DISABLE_OUTBOUND_REPL
> > objectGuid : b8897f54-1bf0-479e-97e0-a6cb7ec1e107
> > invocationID: b8897f54-1bf0-479e-97e0-a6cb7ec1e107
> >
> > ==== INBOUND NEIGHBORS ======================================
> >
> > CN=Schema,CN=Configuration,DC=server,DC=dr
> > RedbusSERVER02 via RPC
> > objectGuid: d5d0d348-64d0-4789-890d-3a77e8bd5624
> > Last attempt @ 2005-09-07 13:48.44 failed, result
> > 8457:
> > Can't retrieve message string 8457 (0x2109), error
> > 1815.
> > Last success @ 2005-08-30 07:49.17.
> > 86 consecutive failure(s).
> >
> > CN=Configuration,DC=server,DC=dr
> > RedbusSERVER02 via RPC
> > objectGuid: d5d0d348-64d0-4789-890d-3a77e8bd5624
> > Last attempt @ 2005-09-07 13:48.44 failed, result
> > 8457:
> > Can't retrieve message string 8457 (0x2109), error
> > 1815.
> > Last success @ 2005-08-30 08:02.15.
> > 189 consecutive failure(s).
> >
> > DC=server,DC=dr
> > RedbusSERVER02 via RPC
> > objectGuid: d5d0d348-64d0-4789-890d-3a77e8bd5624
> > Last attempt @ 2005-09-07 13:48.44 failed, result
> > 8457:
> > Can't retrieve message string 8457 (0x2109), error
> > 1815.
> > Last success @ 2005-08-30 07:58.02.
> > 123 consecutive failure(s).
> >
> > ==== OUTBOUND NEIGHBORS FOR CHANGE NOTIFICATIONS ============
> >
> > CN=Schema,CN=Configuration,DC=server,DC=dr
> > RedbusSERVER02 via RPC
> > objectGuid: d5d0d348-64d0-4789-890d-3a77e8bd5624
> >
> > CN=Configuration,DC=server,DC=dr
> > RedbusSERVER02 via RPC
> > objectGuid: d5d0d348-64d0-4789-890d-3a77e8bd5624
> >
> > DC=server,DC=dr
> > RedbusSERVER02 via RPC
> > objectGuid: d5d0d348-64d0-4789-890d-3a77e8bd5624
> > --------------------------------------------------------------
> > ------------------------
> > Event Log on SERVER01:
> >
> > ---------------------
> > Event Type: Warning
> > Event Source: NtFrs
> > Event Category: None
> > Event ID: 13508
> > Date: 07/09/2005
> > Time: 11:52:09
> > User: N/A
> > Computer:SERVER01
> > Description:
> > The File Replication Service is having trouble enabling
> > replication from
> > SERVER02 to SERVER01 for c:winntsysvoldomain using the DNS
> > name
> > server02.server.dr. FRS will keep retrying.
> > Following are some of the reasons you would see this warning.
> >
> >
> > [1] FRS can not correctly resolve the DNS name
> > server02.server.dr from this
> > computer.
> > [2] FRS is not running on server02.server.dr.
> > [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 the
> > connection has been established.
> >
> > --------------------------------------------------------------
> > -------------------------
> > Was this post helpful to you?
> >
> > Why should I rate a post?
>
> you have been caught by the USN rollback problem!
>
> Read more at:
> MS-KBQ875495_How to detect and recover from a USN rollback in Windows
> Server 2003
>
> MS-KBQ885875_How to detect and recover from a USN rollback in Windows
> 2000 Server
>
> Windows 2000/2003 DCs should NEVER, NEVER, NEVER be imaged for
> backup/restore purposes! Imaging is NOT AD aware backup/restore
> solution and thus not MS approoved!
> A W2K3 pre-SP1 hotfix, a W2K post-SP4 hotfix and W2K3 SP1 will stop
> DCs replicating by disabling replication when USN rollback is
> detected. As I know the detection is not guaranteed, but when it
> detects it does that to prevent further damage.
>
> I assume you first shutdown one DC, images that one, brought it up
> again, shutdown the other DC, imaged that one and brought it up again.
> And afterwards you restored the images. Is that correct?
>
> The kb articles contain the solution and in your case (if you have 2
> DCs) it means demoting one of the DCs, cleaning up metadata and
> promoting it again to a DC. At least if this is your production
> environment!
>
> If you used imaging to copy your production environment into a lab
> environment follow the following procedure. Be aware to use this at
> your own risk, do not use it in a production environment as a
> backup/restore procedure:
> * Shutdown ALL the DCs at the same time in the production environment
> * Image ALL the DCs
> * Start ALL the DCs after all imaging has been done
> * Copy the images of the DCs to the lab network
> * Restore the images of the DCs on the lab network to its
> corresponding hardware
> * Do NOT connect the lab network with the production network
> * Be aware that SID issues might occur is old images are used for the
> DCs (meaning that a certain does not yet exist in the domain while it
> has already been used in some ACL on another server)
>
> AGAIN:
> * be carefull with what you do and use this at your own risk!!!
> * DO NOT USE THIS FOR YOUR PRODUCTION ENVIRONMENT AS A BACKUP AND
> RESTORE PROCEDURE!!!
>
> --
> Posted using the http://www.windowsforumz.com interface, at author's request
> Articles individually checked for conformance to usenet standards
> Topic URL: http://www.windowsforumz.com/Active-Directory-PDC-replicating-ftopict418400.html
> Visit Topic URL to contact author (reg. req'd). Report abuse: http://www.windowsforumz.com/eform.php?p=1398237
>
.

Relevant Pages

  • Different Directory Information Trees
    ... The DCs were not able to apply group policy to themselves. ... I noticed some NTDS Replication 1955 and 1083 errors that come together. ... Weird side-effect I also noticed was that I can no longer launch the Active Directory related Management tools from my workstation unless I use the Active Directory Management MMC. ... I noticed a lot if DNS 4015 errors on the server it appears that the DNS or Active Directory is "busy". ...
    (microsoft.public.windows.server.active_directory)
  • Replication errors -BuiltinAdministrators doesnt have access ri
    ... * Connecting to directory service on server agfvads1. ... Replication Service,CN=System,DC=andrew,DC=com ... clean up this DCs ... Running partition tests on: Configuration ...
    (microsoft.public.windows.server.active_directory)
  • Re: Missing NTDS Settings object
    ... the AD database on ALL the DCs within that domain ... That's when the replication broke and the ISTG settings in the NTDS Site ... NO server for that domain appears in ANY site, ... and services on one of the domain controllers in that domain - then they show ...
    (microsoft.public.windows.server.active_directory)
  • Re: Replication Problem
    ... You could try resetting the secure channel with the DCs in the other site. ... We have setup the iner-site replication topology in Sites and Services snap-in and everything works fine. ... About two mounth ago on of the servers has been shout-down, that server was the bridge-head server in it site. ... I hope this will resync the computer account passwords and the replication will restart to work * Demote the bridge-head server in the problematic site, remove any leftover objects in the domain and promote the DC again. ...
    (microsoft.public.win2000.active_directory)
  • Re: 2003 AD R2 schema upgrade from Win 2000 Server?
    ... R2 is only available for W2k3 with SP1, you can apply on a mixed environment where you have 2000 and 2003 but R2 features can only be installed in a server with w2k3SP1, and the R2 features are only available to the server. ... DCs located in three sites. ... production environment which must remain up and running 24/7. ...
    (microsoft.public.windows.server.active_directory)