Announcement

Collapse
No announcement yet.

AD Replication

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • AD Replication

    Hi,
    I have 3 DC's in my organization. 2 of them are synchronizing and 1 of them after i update 2003 SP1 suddenly couldn't synchronize.
    I attached a screen shot.
    I can't demote the server.

    how can i fix the situation ?
    or how can i force demote ?
    Attached Files

  • #2
    Re: AD Replication

    Have you ran dcdiag on the problematic DC ?
    Some of the reasons for the error you are getting would be:
    - you manually disabled the replication on the DC via registry
    - lingering objects on the DC in question
    - the DC has not been replicating longer than the tombstone lifetime period.

    In any case, the output of dcdiag should help to try to diagnoze the issue.
    Guy Teverovsky
    "Smith & Wesson - the original point and click interface"

    Comment


    • #3
      Re: AD Replication

      This are the results fo running DCDIAG:

      Domain Controller Diagnosis

      Performing initial setup:
      ["ServerName"] Directory Binding Error -2146892976:
      Win32 Error -2146892976
      This may limit some of the tests that can be performed.
      Done gathering initial info.

      Doing initial required tests

      Testing server: Default-First-Site-Name\"ServerName"
      Starting test: Connectivity
      ["ServerName"] DsBindWithSpnEx() failed with error -2146892976,
      Win32 Error -2146892976.
      ......................... "ServerName" failed test Connectivity

      Doing primary tests

      Testing server: Default-First-Site-Name\"ServerName"
      Skipping all tests, because server "ServerName" is
      not responding to directory service requests

      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 : DomainName
      Starting test: CrossRefValidation
      ......................... DomainName passed test CrossRefValidation
      Starting test: CheckSDRefDom
      ......................... DomainName passed test CheckSDRefDom

      Running enterprise tests on : DomainName.loc
      Starting test: Intersite
      ......................... DomainName.loc passed test Intersite
      Starting test: FsmoCheck
      ......................... DomainName.loc passed test FsmoCheck



      someone can help me ?

      Comment


      • #4
        Re: AD Replication

        These errors indicate network problems. DNS is very common, but since you had it working before this seems unlikely. Is the firewall perhaps enabled? Did you block port 135 anywhere?

        Comment

        Working...
        X