none
Replicação entre domain controlers RRS feed

  • Pergunta

  • Fala galera...

    Faz um bom tempo que não postava nada só absorvendo conhecimento, me mudei para uma nova empresa, a qual tenho diversos problemas. Um dos principais problemas esta na replicação de domínio.

    Toda vez que tento efetuar a replicação recebo erro de RPC. 

    Executei o comando dcdiag /DnsBasic

    E obtive a seguinte resposta:                        

    ====================================================================================================

    Domain Controller Diagnosis

    Performing initial setup:
       Done gathering initial info.

    Doing initial required tests

       Testing server: POP-DEMOSTENES\G1474-FS
          Starting test: Connectivity
             ......................... G1474-FS passed test Connectivity

    Doing primary tests

       Testing server: POP-DEMOSTENES\G1474-FS
          Starting test: Replications
             [Replications Check,G1474-FS] A recent replication attempt failed:
                From W8VPOPSERVICE to G1474-FS
                Naming Context: DC=ForestDnsZones,DC=pop,DC=corp
                The replication generated an error (1256):
                Win32 Error 1256
                The failure occurred at 2012-08-24 15:49:46.
                The last success occurred at 2012-05-23 08:46:08.
                2244 failures have occurred since the last success.
             [W8VPOPSERVICE] DsBindWithSpnEx() failed with error 1753,
             Win32 Error 1753.
             [Replications Check,G1474-FS] A recent replication attempt failed:
                From R410POPEXCH to G1474-FS
                Naming Context: DC=ForestDnsZones,DC=pop,DC=corp
                The replication generated an error (1256):
                Win32 Error 1256
                The failure occurred at 2012-08-24 15:50:09.
                The last success occurred at 2012-05-25 13:26:58.
                2192 failures have occurred since the last success.
             [R410POPEXCH] DsBindWithSpnEx() failed with error 1722,
             Win32 Error 1722.
             [Replications Check,G1474-FS] A recent replication attempt failed:
                From W8VPOPSERVICE to G1474-FS
                Naming Context: DC=DomainDnsZones,DC=pop,DC=corp
                The replication generated an error (1256):
                Win32 Error 1256
                The failure occurred at 2012-08-24 15:49:46.
                The last success occurred at 2012-05-23 09:15:18.
                2244 failures have occurred since the last success.
             [Replications Check,G1474-FS] A recent replication attempt failed:
                From R410POPEXCH to G1474-FS
                Naming Context: DC=DomainDnsZones,DC=pop,DC=corp
                The replication generated an error (1256):
                Win32 Error 1256
                The failure occurred at 2012-08-24 15:50:09.
                The last success occurred at 2012-05-25 13:30:37.
                2192 failures have occurred since the last success.
             [Replications Check,G1474-FS] A recent replication attempt failed:
                From W8VPOPSERVICE to G1474-FS
                Naming Context: CN=Schema,CN=Configuration,DC=pop,DC=corp
                The replication generated an error (1753):
                Win32 Error 1753
                The failure occurred at 2012-08-24 15:50:09.
                The last success occurred at 2012-05-23 08:45:47.
                2244 failures have occurred since the last success.
                The directory on W8VPOPSERVICE is in the process.
                of starting up or shutting down, and is not available.
                Verify machine is not hung during boot.
             [Replications Check,G1474-FS] A recent replication attempt failed:
                From R410POPEXCH to G1474-FS
                Naming Context: CN=Schema,CN=Configuration,DC=pop,DC=corp
                The replication generated an error (8524):
                Win32 Error 8524
                The failure occurred at 2012-08-24 15:50:11.
                The last success occurred at 2012-05-25 13:26:58.
                2192 failures have occurred since the last success.
                The guid-based DNS name c46390a8-acbe-4ca8-bec7-12e593564404._msdcs.pop.corp
                is not registered on one or more DNS servers.
             [Replications Check,G1474-FS] A recent replication attempt failed:
                From POPSD to G1474-FS
                Naming Context: CN=Schema,CN=Configuration,DC=pop,DC=corp
                The replication generated an error (1722):
                Win32 Error 1722
                The failure occurred at 2012-08-24 15:50:32.
                The last success occurred at 2012-05-15 18:45:05.
                2435 failures have occurred since the last success.
                [POPSD] DsBindWithSpnEx() failed with error 1722,
                Win32 Error 1722.
                The source remains down. Please check the machine.
             [Replications Check,G1474-FS] A recent replication attempt failed:
                From POPSD to G1474-FS
                Naming Context: CN=Configuration,DC=pop,DC=corp
                The replication generated an error (1722):
                Win32 Error 1722
                The failure occurred at 2012-08-24 15:50:07.
                The last success occurred at 2012-05-15 18:45:05.
                2430 failures have occurred since the last success.
                The source remains down. Please check the machine.
             [Replications Check,G1474-FS] A recent replication attempt failed:
                From W8VPOPSERVICE to G1474-FS
                Naming Context: CN=Configuration,DC=pop,DC=corp
                The replication generated an error (1753):
                Win32 Error 1753
                The failure occurred at 2012-08-24 15:50:07.
                The last success occurred at 2012-05-23 08:45:47.
                2244 failures have occurred since the last success.
                The directory on W8VPOPSERVICE is in the process.
                of starting up or shutting down, and is not available.
                Verify machine is not hung during boot.
             [Replications Check,G1474-FS] A recent replication attempt failed:
                From R410POPEXCH to G1474-FS
                Naming Context: CN=Configuration,DC=pop,DC=corp
                The replication generated an error (8524):
                Win32 Error 8524
                The failure occurred at 2012-08-24 15:50:09.
                The last success occurred at 2012-05-25 13:26:58.
                2192 failures have occurred since the last success.
                The guid-based DNS name c46390a8-acbe-4ca8-bec7-12e593564404._msdcs.pop.corp
                is not registered on one or more DNS servers.
             [Replications Check,G1474-FS] A recent replication attempt failed:
                From POPSD to G1474-FS
                Naming Context: DC=pop,DC=corp
                The replication generated an error (1722):
                Win32 Error 1722
                The failure occurred at 2012-08-24 15:50:55.
                The last success occurred at (never).
                2474 failures have occurred since the last success.
                The source remains down. Please check the machine.
             [Replications Check,G1474-FS] A recent replication attempt failed:
                From R410POPEXCH to G1474-FS
                Naming Context: DC=pop,DC=corp
                The replication generated an error (8524):
                Win32 Error 8524
                The failure occurred at 2012-08-24 15:57:00.
                The last success occurred at 2012-05-25 13:35:26.
                2193 failures have occurred since the last success.
                The guid-based DNS name c46390a8-acbe-4ca8-bec7-12e593564404._msdcs.pop.corp
                is not registered on one or more DNS servers.
             [Replications Check,G1474-FS] A recent replication attempt failed:
                From W8VPOPSERVICE to G1474-FS
                Naming Context: DC=pop,DC=corp
                The replication generated an error (1753):
                Win32 Error 1753
                The failure occurred at 2012-08-24 15:57:04.
                The last success occurred at 2012-05-23 09:25:11.
                2246 failures have occurred since the last success.
                The directory on W8VPOPSERVICE is in the process.
                of starting up or shutting down, and is not available.
                Verify machine is not hung during boot.
             REPLICATION-RECEIVED LATENCY WARNING
             G1474-FS:  Current time is 2012-08-24 15:58:27.
                DC=ForestDnsZones,DC=pop,DC=corp
                   Last replication recieved from W8VPOPSERVICE at 2012-05-23 08:59:02.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from R410POPEXCH at 2012-05-25 13:26:58.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from POP0027AD at 2012-05-25 13:26:15.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                DC=DomainDnsZones,DC=pop,DC=corp
                   Last replication recieved from W8VPOPSERVICE at 2012-05-23 09:15:18.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from R410POPEXCH at 2012-05-25 13:30:40.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from POP0027AD at 2012-05-25 13:27:03.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                CN=Schema,CN=Configuration,DC=pop,DC=corp
                   Last replication recieved from W8VPOPSERVICE at 2012-05-23 11:00:50.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from W3KADPOPNHUGUAC at 2011-03-29 12:45:35.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from R410POPEXCH at 2012-05-25 13:26:58.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from POPSD at 2012-05-15 18:53:16.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from POP0027AD at 2012-05-25 13:00:52.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                CN=Configuration,DC=pop,DC=corp
                   Last replication recieved from W8VPOPSERVICE at 2012-05-23 08:59:02.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from W3KADPOPNHUGUAC at 2011-03-29 18:59:27.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from R410POPEXCH at 2012-05-25 13:27:00.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from POPSD at 2012-05-15 18:53:16.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from POP0027AD at 2012-05-25 13:26:42.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                DC=pop,DC=corp
                   Last replication recieved from W8VPOPSERVICE at 2012-05-23 11:00:50.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from W3KADPOPNHUGUAC at 2011-03-29 18:59:33.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from R410POPEXCH at 2012-05-25 13:35:29.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from POP0027AD at 2012-05-25 13:27:48.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
             ......................... G1474-FS passed test Replications
          Starting test: NCSecDesc
             ......................... G1474-FS passed test NCSecDesc
          Starting test: NetLogons
             ......................... G1474-FS passed test NetLogons
          Starting test: Advertising
             ......................... G1474-FS passed test Advertising
          Starting test: KnowsOfRoleHolders
             ......................... G1474-FS passed test KnowsOfRoleHolders
          Starting test: RidManager
             ......................... G1474-FS passed test RidManager
          Starting test: MachineAccount
             ......................... G1474-FS passed test MachineAccount
          Starting test: Services
             ......................... G1474-FS passed test Services
          Starting test: ObjectsReplicated
             ......................... G1474-FS passed test ObjectsReplicated
          Starting test: frssysvol
             ......................... G1474-FS passed test frssysvol
          Starting test: frsevent
             There are warning or error events within the last 24 hours after the

             SYSVOL has been shared.  Failing SYSVOL replication problems may cause

             Group Policy problems. 
             ......................... G1474-FS failed test frsevent
          Starting test: kccevent
             An Warning Event occured.  EventID: 0x8000051B
                Time Generated: 08/24/2012   15:51:41
                Event String: The Knowledge Consistency Checker (KCC) has

             An Warning Event occured.  EventID: 0x8000061E
                Time Generated: 08/24/2012   15:51:41
                Event String: All domain controllers in the following site that

             An Warning Event occured.  EventID: 0x8000051B
                Time Generated: 08/24/2012   15:51:41
                Event String: The Knowledge Consistency Checker (KCC) has

             An Error Event occured.  EventID: 0xC000051F
                Time Generated: 08/24/2012   15:51:41
                Event String: The Knowledge Consistency Checker (KCC) has

             An Warning Event occured.  EventID: 0x80000749
                Time Generated: 08/24/2012   15:51:41
                Event String: The Knowledge Consistency Checker (KCC) was

             An Warning Event occured.  EventID: 0x80000805
                Time Generated: 08/24/2012   15:51:41
                Event String: A new connection has been created to address site

             An Warning Event occured.  EventID: 0x8000061E
                Time Generated: 08/24/2012   15:51:41
                Event String: All domain controllers in the following site that

             An Error Event occured.  EventID: 0xC000051F
                Time Generated: 08/24/2012   15:51:41
                Event String: The Knowledge Consistency Checker (KCC) has

             An Warning Event occured.  EventID: 0x80000749
                Time Generated: 08/24/2012   15:51:41
                Event String: The Knowledge Consistency Checker (KCC) was

             An Warning Event occured.  EventID: 0x8000061E
                Time Generated: 08/24/2012   15:51:41
                Event String: All domain controllers in the following site that

             An Error Event occured.  EventID: 0xC000051F
                Time Generated: 08/24/2012   15:51:41
                Event String: The Knowledge Consistency Checker (KCC) has

             An Warning Event occured.  EventID: 0x80000749
                Time Generated: 08/24/2012   15:51:41
                Event String: The Knowledge Consistency Checker (KCC) was

             An Warning Event occured.  EventID: 0x8000061E
                Time Generated: 08/24/2012   15:51:41
                Event String: All domain controllers in the following site that

             An Error Event occured.  EventID: 0xC000051F
                Time Generated: 08/24/2012   15:51:41
                Event String: The Knowledge Consistency Checker (KCC) has

             An Warning Event occured.  EventID: 0x80000749
                Time Generated: 08/24/2012   15:51:41
                Event String: The Knowledge Consistency Checker (KCC) was

             An Warning Event occured.  EventID: 0x80000785
                Time Generated: 08/24/2012   15:52:13
                Event String: The attempt to establish a replication link for

             An Warning Event occured.  EventID: 0x80000785
                Time Generated: 08/24/2012   15:52:13
                Event String: The attempt to establish a replication link for

             ......................... G1474-FS failed test kccevent
          Starting test: systemlog
             An Error Event occured.  EventID: 0x40000004
                Time Generated: 08/24/2012   15:14:50
                Event String: The kerberos client received a

             ......................... G1474-FS failed test systemlog
          Starting test: VerifyReferences
             ......................... G1474-FS passed test VerifyReferences

       Running partition tests on : ForestDnsZones
          Starting test: CrossRefValidation
             ......................... ForestDnsZones passed test CrossRefValidation
          Starting test: CheckSDRefDom
             ......................... ForestDnsZones passed test CheckSDRefDom

       Running partition tests on : DomainDnsZones
          Starting test: CrossRefValidation
             ......................... DomainDnsZones passed test CrossRefValidation
          Starting test: CheckSDRefDom
             ......................... DomainDnsZones passed test CheckSDRefDom

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

       Running enterprise tests on : pop.corp
          Starting test: Intersite
             ......................... pop.corp passed test Intersite
          Starting test: FsmoCheck
             ......................... pop.corp passed test FsmoCheck

    ====================================================================================================

    Como é possível perceber faz mais de 3 meses que o problema ocorre, o problema é que entrei na empresa tem pouco mais de um mês e não sei exatamente o que foi efetuado. Como o ambiente é de produção não posso ficar arriscando entre tentativa e erro.

    Alguém poderia dar uma luz?

    []´s

    sexta-feira, 24 de agosto de 2012 19:35

Respostas

  • Olá Rafael,

    Não sei se você chegou a ver, mas segue KB com o seu problema: http://support.microsoft.com/kb/2028495

    Tem mais alguns comandos neste KB.

    Sobre o segundo DC ele não está achando o GC nem os FSMOs por causa dos registros DNS do DNS server configurado na placa deste servidor.

    Sugiro comparar os DNS Servers que estão normais com os que estão com problemas de replicação, pois creio que estes que estão faltando registros, como por exemplo, registros SRV.


    Att,

    Elias Shuiti Yasuda
    MCP | MCTS | MCITP | MCSA 2K8 | ITIL v3 | Cobit
    Digisystem - Analista N2 Servidores
    Mestra - Administrador de redes
    "O ser humano evolui ao reconhecer os próprios erros."


    quarta-feira, 29 de agosto de 2012 02:05
    Moderador

Todas as Respostas

  • Olá Rafael Estevan,

    Primeiramente faça o backup System State destes servidores ou faça um ambiente de testes virtualizando os DCs.

    Faça o backup também dos scripts que estão no NETLOGON.

    Provavelmente nos logs de replicação você está com os erros Event ID 2042, 1388 ou 1988, além de outros erros.

    Creio que não conseguiremos resolver somente em um post.

    Você está com objetos remanescentes e você terá que removê-los.

    Primeiramente verifique se o horário e a data entre os DCs estão corretos, a diferença máxima entre eles deverá ser de 5 minutos.

    Para remover os objetos remanescentes siga os passos abaixo:

    1. Dê o comando repadmin /showrepl no servidor que você postou o log.

    2. Observe os campos indicados em vermelho:

    3. Segue a sintaxe do comando a ser realizado:

    repadmin /removelingeringobjects <ServerName> <ServerGUID> <Directory Partition> /advisory_mode

    onde,

    <ServerName> - Nome do servidor em que o log ID 2042 está ocorrendo

    <ServerGUID> - É o campo DC object GUID encontrado no passo 2

    <Directory Partition> - São um dos 3 campos encontrados em vermelho no passo 2

    Temos que remover os objetos remanescentes da partição do domínio, da partição de configuração do domínio e da partição do esquema. Temos que fazer 2 comandos para cada partição, um comando com /advisory_mode e outro comando sem o /advisory_mode.

    Darei um exemplo caso o nome do domínio seja newyork.contoso.org.br com base na GUID da figura que eu postei. O nome do controlador de domínio será NY-DC1.

     

    repadmin /removelingeringobjects NY-DC1 999f6143-f55b-40f0-8840-6eb46a60c05e DC=newyork,DC=contoso,DC=org,DC=br /advisory_mode

    repadmin /removelingeringobjects NY-DC1 999f6143-f55b-40f0-8840-6eb46a60c05e DC=newyork,DC=contoso,DC=org,DC=br

    repadmin /removelingeringobjects NY-DC1 999f6143-f55b-40f0-8840-6eb46a60c05e CN=Configuration,DC=newyork,DC=contoso,DC=org,DC=br /advisory_mode

    repadmin /removelingeringobjects NY-DC1 999f6143-f55b-40f0-8840-6eb46a60c05e CN=Configuration,DC=newyork,DC=contoso,DC=org,DC=br

    repadmin /removelingeringobjects NY-DC1 999f6143-f55b-40f0-8840-6eb46a60c05e CN=Schema,CN=Configuration,DC=newyork,DC=contoso,DC=org,DC=br /advisory_mode

    repadmin /removelingeringobjects NY-DC1 999f6143-f55b-40f0-8840-6eb46a60c05e CN=Schema,CN=Configuration,DC=newyork,DC=contoso,DC=org,DC=br

    4. Caso o outro DC esteja com o event ID 2042, faça novamente os passos 2 e 3 no outro servidor.

    5. Entre no regedit do servidor PDC e mude a chave abaixo (Caso não tenha o registro, crie):

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters
    Registro DWORD:
    Allow Replication With Divergent and Corrupt Partner, Value Data = 1

    Editar este registro reinicia a replicação entre os controladores de domínio.

    6. Verifique se a replicação está funcionando, fazendo testes com a pasta SYSVOL ou forçando a replicação pelo Active Directory Sites and Services.

    7. Caso esteja funcionando normalmente, edite o registro do passo 5 para Value Data = 0.

    Poste o log dcdiag dos servidores. Poste também os logs dcdiag /test:dns.



    Att,

    Elias Shuiti Yasuda
    MCP | MCTS | MCITP | MCSA 2K8 | ITIL v3 | Cobit
    Digisystem - Analista N2 Servidores
    Mestra - Administrador de redes
    "O ser humano evolui ao reconhecer os próprios erros."


    segunda-feira, 27 de agosto de 2012 03:53
    Moderador
  • Olá Elias,

    Obrigado por sua resposta porem estou tendo problemas logo de inicio. 

    Para que você possa entender melhor a situação, atualmente tenho 1 AD principal e mais 4 replicando informações, sendo um destes exchange.

    Nos DC´s que estão na mesma rede que são, consigo efetuar normalmente a replicação, porem nos outros 2 não consigo obter sucesso. Logo de cara percebi que um dos DC está com o horário incorreto. Está com 9 minutos a mais que meu servidor principal. Tentei efetuar o ajuste do horário porem o servidor assim que altero para o valor desejado volta para o horário que ele quer ou seja 9 minutos  a mais. 

    ================================================

    Tracking G1474-FS.pop.corp [192.168.1.38].
    Collecting 1 samples.
    The current time is 8/27/2012 4:46:49 PM (local time).
    16:46:49, -551.1982798s

    ================================================

    Em relação aos demais passos segui normalmente, porem vi que no servidor que mandei os primeiros logs não consta o erro no event_viewer conforme mencionado. No servidor não consta nenhum dos erros. Porem nos servidores que tenho problemas de replicação sim.

    Abaixo o comando executado o qual obtive exito, tanto assim como com o  /advisory_mode

    =================================================================

    C:\Program Files\Support Tools>repadmin /removelingeringobjects G1474-FS 53ab054
    f-3c73-4d4e-862c-5f0eec6e1b6a  DC=pop,DC=corp CN=Configuration,DC=pop,DC=corp CN
    =Schema,CN=Configuration,DC=pop,DC=corp
    RemoveLingeringObjects sucessfull on G1474-FS.

    ==================================================================

    Grato pela ajuda até o momento.

    segunda-feira, 27 de agosto de 2012 19:47
  • Olá Rafael,

    No servidor que está com 9 minutos adiantados, faça o seguinte procedimento:

    Entre no editor de registro do servidor.

    Vá até o caminho abaixo:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters\
    Edite o registro abaixo:
    Value name: Type

    Value Data: NT5DS

    Ou faça a busca da fonte de tempo com a mesma fonte de tempo do servidor principal.

    Edite os seguintes registros abaixo:
    Value name: NTPServer
    Value data: <serverNTP>, 0x1

    Value name: Type

    Value Data: NTP

    Vá até o prompt de comando e dê um w32tm /config /update ,  verifique se a fonte de tempo é a que você colocou com o comando w32tm /query /source, depois dê o comando w32tm /resync.

    Verifique se o horário fica sincronizado com o DC principal.

    Em todos os servidores com Event ID 2042, 1388 e 1988, faça o procedimento citado anteriormente.


    Att,

    Elias Shuiti Yasuda
    MCP | MCTS | MCITP | MCSA 2K8 | ITIL v3 | Cobit
    Digisystem - Analista N2 Servidores
    Mestra - Administrador de redes
    "O ser humano evolui ao reconhecer os próprios erros."


    segunda-feira, 27 de agosto de 2012 22:47
    Moderador
  • Olá Elias,

    Obrigado pela resposta.

    Segue o novo status:

    Tenho 2 servidores ainda sem comunicação com o PDC.

    Um deles ao efetuar o procedimento descrito obtive o seguinte resultado.

    =======================================================================================================

    C:\Program Files\Support Tools>repadmin /removelingeringobjects /homeserver:192.
    168.2.11 W3KADPOPNHUGUACU  04de6416-06fa-4889-ad16-36fcf8c048fd DC=pop,DC=corp
    Repadmin can't connect to a "home server", because of the following error.  Try
    specifying a different
    home server with /homeserver:[dns name]
    Error: An LDAP lookup operation failed with the following error:

        LDAP Error 49(0x31): Invalid Credentials
        Server Win32 Error 0(0x0):
        Extended Information:

    =======================================================================================================

    Já no outro obtive sucesso na execução, porem não consigo efetuar a replicação.

    Ao clicar em Active Directory Sites and Services efetuei a replicação e obtive o seguinte erro:

    Following error occurred during the attempt to synchronize naming context pop.corp.com from doamain controller POPSD to Domain controller g1474-fs:

    The RPC server is unavailable.

    Segue abaixo o dcdiag dos servidores sem comunicação:

    POPSD

    =====================================================================================================



    Domain Controller Diagnosis

    Performing initial setup:
       Done gathering initial info.

    Doing initial required tests
       
       Testing server: POP-DEMOSTENES\POPSD
          Starting test: Connectivity
             ......................... POPSD passed test Connectivity

    Doing primary tests
       
       Testing server: POP-DEMOSTENES\POPSD
          Starting test: Replications
             [R410S1A] DsBindWithSpnEx() failed with error -2146893022,
             The target principal name is incorrect..
             [Replications Check,POPSD] A recent replication attempt failed:
                From R410S1A to POPSD
                Naming Context: DC=pop,DC=corp
                The replication generated an error (8606):
                Insufficient attributes were given to create an object.  This object may not exist because it may have been deleted and already garbage collected.
                The failure occurred at 2012-08-28 12:59:14.
                The last success occurred at 2012-06-06 10:54:39.
                2000 failures have occurred since the last success.
             [Replications Check,POPSD] A recent replication attempt failed:
                From G1474-FS to POPSD
                Naming Context: DC=pop,DC=corp
                The replication generated an error (8606):
                Insufficient attributes were given to create an object.  This object may not exist because it may have been deleted and already garbage collected.
                The failure occurred at 2012-08-28 12:59:18.
                The last success occurred at 2012-06-06 10:54:39.
                2014 failures have occurred since the last success.
             REPLICATION LATENCY WARNING
             ERROR: Expected notification link is missing.
             Source G1474-FS
             Replication of new changes along this path will be delayed.
             This problem should self-correct on the next periodic sync.
             [Replications Check,POPSD] A recent replication attempt failed:
                From W3POPEXCH to POPSD
                Naming Context: DC=pop,DC=corp
                The replication generated an error (8606):
                Insufficient attributes were given to create an object.  This object may not exist because it may have been deleted and already garbage collected.
                The failure occurred at 2012-08-28 13:00:10.
                The last success occurred at (never).
                686 failures have occurred since the last success.
             REPLICATION LATENCY WARNING
             ERROR: Expected notification link is missing.
             Source W3POPEXCH
             Replication of new changes along this path will be delayed.
             This problem should self-correct on the next periodic sync.
             [Replications Check,POPSD] A recent replication attempt failed:
                From R410POPEXC to POPSD
                Naming Context: DC=pop,DC=corp
                The replication generated an error (8606):
                Insufficient attributes were given to create an object.  This object may not exist because it may have been deleted and already garbage collected.
                The failure occurred at 2012-08-28 13:00:13.
                The last success occurred at (never).
                686 failures have occurred since the last success.
             REPLICATION LATENCY WARNING
             ERROR: Expected notification link is missing.
             Source R410POPEXC
             Replication of new changes along this path will be delayed.
             This problem should self-correct on the next periodic sync.
             [Replications Check,POPSD] A recent replication attempt failed:
                From W3KADPOPNHUGUACU to POPSD
                Naming Context: DC=pop,DC=corp
                The replication generated an error (8606):
                Insufficient attributes were given to create an object.  This object may not exist because it may have been deleted and already garbage collected.
                The failure occurred at 2012-08-28 13:14:26.
                The last success occurred at (never).
                696 failures have occurred since the last success.
             REPLICATION-RECEIVED LATENCY WARNING
             POPSD:  Current time is 2012-08-28 13:14:36.
                DC=pop,DC=corp
                   Last replication recieved from R410POPEXC at 2012-06-06 10:45:39.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from R410S1A at 2012-06-06 10:45:55.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from G1474-FS at 2012-06-06 10:45:55.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from W3POPEXCH at 2012-06-06 10:45:27.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from W3KADPOPNHUGUACU at 2011-03-29 18:59:33.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
             ......................... POPSD passed test Replications
          Starting test: NCSecDesc
             ......................... POPSD passed test NCSecDesc
          Starting test: NetLogons
             ......................... POPSD passed test NetLogons
          Starting test: Advertising
             ......................... POPSD passed test Advertising
          Starting test: KnowsOfRoleHolders
             ......................... POPSD passed test KnowsOfRoleHolders
          Starting test: RidManager
             ......................... POPSD passed test RidManager
          Starting test: MachineAccount
             ......................... POPSD passed test MachineAccount
          Starting test: Services
             ......................... POPSD passed test Services
          Starting test: ObjectsReplicated
             ......................... POPSD passed test ObjectsReplicated
          Starting test: frssysvol
             ......................... POPSD passed test frssysvol
          Starting test: frsevent
             There are warning or error events within the last 24 hours after the

             SYSVOL has been shared.  Failing SYSVOL replication problems may cause

             Group Policy problems. 
             ......................... POPSD failed test frsevent
          Starting test: kccevent
             An Error Event occured.  EventID: 0xC02507C4
                Time Generated: 08/28/2012   13:00:06
                (Event String could not be retrieved)
             An Error Event occured.  EventID: 0xC02507C4
                Time Generated: 08/28/2012   13:00:10
                (Event String could not be retrieved)
             An Error Event occured.  EventID: 0xC02507C4
                Time Generated: 08/28/2012   13:00:13
                (Event String could not be retrieved)
             An Error Event occured.  EventID: 0xC02507C4
                Time Generated: 08/28/2012   13:01:00
                (Event String could not be retrieved)
             ......................... POPSD failed test kccevent
          Starting test: systemlog
             An Error Event occured.  EventID: 0x40000004
                Time Generated: 08/28/2012   13:14:36
                Event String: The kerberos client received a

             ......................... POPSD failed test systemlog
          Starting test: VerifyReferences
             ......................... POPSD passed test VerifyReferences
       
       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 : pop
          Starting test: CrossRefValidation
             ......................... pop passed test CrossRefValidation
          Starting test: CheckSDRefDom
             ......................... pop passed test CheckSDRefDom
       
       Running enterprise tests on : pop.corp
          Starting test: Intersite
             ......................... pop.corp passed test Intersite
          Starting test: FsmoCheck
             ......................... pop.corp passed test FsmoCheck

    =====================================================================================================

    W3KADPOPNHUGUACU 

    =====================================================================================================


    Domain Controller Diagnosis

    Performing initial setup:
       [W3KADPOPNHUGUACU] Directory Binding Error 5:
       Access is denied.
       This may limit some of the tests that can be performed.
       Done gathering initial info.

    Doing initial required tests
       
       Testing server: POP-DEMOSTENES\W3KADPOPNHUGUACU
          Starting test: Connectivity
             ......................... W3KADPOPNHUGUACU passed test Connectivity

    Doing primary tests
       
       Testing server: POP-DEMOSTENES\W3KADPOPNHUGUACU
          Starting test: Replications
             [Replications Check,W3KADPOPNHUGUACU] A recent replication attempt failed:
                From R410POPEXC to W3KADPOPNHUGUACU
                Naming Context: DC=ForestDnsZones,DC=pop,DC=corp
                The replication generated an error (1256):
                The remote system is not available. For information about network troubleshooting, see Windows Help.
                The failure occurred at 2012-08-28 13:00:10.
                The last success occurred at 2012-08-16 02:58:02.
                298 failures have occurred since the last success.
             [R410POPEXC] DsBindWithSpnEx() failed with error 1722,
             The RPC server is unavailable..
             [Replications Check,W3KADPOPNHUGUACU] A recent replication attempt failed:
                From R410S1A to W3KADPOPNHUGUACU
                Naming Context: DC=ForestDnsZones,DC=pop,DC=corp
                The replication generated an error (1256):
                The remote system is not available. For information about network troubleshooting, see Windows Help.
                The failure occurred at 2012-08-28 13:00:12.
                The last success occurred at 2012-08-15 07:58:00.
                317 failures have occurred since the last success.
             [R410S1A] DsBindWithSpnEx() failed with error 1722,
             The RPC server is unavailable..
             [Replications Check,W3KADPOPNHUGUACU] A recent replication attempt failed:
                From G1474-FS to W3KADPOPNHUGUACU
                Naming Context: DC=ForestDnsZones,DC=pop,DC=corp
                The replication generated an error (8606):
                Insufficient attributes were given to create an object.  This object may not exist because it may have been deleted and already garbage collected.
                The failure occurred at 2012-08-28 13:00:46.
                The last success occurred at 2012-08-27 10:59:53.
                26 failures have occurred since the last success.
             [G1474-FS] DsBindWithSpnEx() failed with error -2146893022,
             The target principal name is incorrect..
             [Replications Check,W3KADPOPNHUGUACU] A recent replication attempt failed:
                From W3POPEXCH to W3KADPOPNHUGUACU
                Naming Context: DC=ForestDnsZones,DC=pop,DC=corp
                The replication generated an error (8606):
                Insufficient attributes were given to create an object.  This object may not exist because it may have been deleted and already garbage collected.
                The failure occurred at 2012-08-28 13:00:46.
                The last success occurred at 2012-08-27 10:59:53.
                26 failures have occurred since the last success.
             [Replications Check,W3KADPOPNHUGUACU] A recent replication attempt failed:
                From R410POPEXC to W3KADPOPNHUGUACU
                Naming Context: DC=DomainDnsZones,DC=pop,DC=corp
                The replication generated an error (1256):
                The remote system is not available. For information about network troubleshooting, see Windows Help.
                The failure occurred at 2012-08-28 13:00:10.
                The last success occurred at (never).
                1868 failures have occurred since the last success.
             [Replications Check,W3KADPOPNHUGUACU] A recent replication attempt failed:
                From R410S1A to W3KADPOPNHUGUACU
                Naming Context: DC=DomainDnsZones,DC=pop,DC=corp
                The replication generated an error (1256):
                The remote system is not available. For information about network troubleshooting, see Windows Help.
                The failure occurred at 2012-08-28 13:00:12.
                The last success occurred at (never).
                334 failures have occurred since the last success.
             [Replications Check,W3KADPOPNHUGUACU] A recent replication attempt failed:
                From W3POPEXCH to W3KADPOPNHUGUACU
                Naming Context: DC=DomainDnsZones,DC=pop,DC=corp
                The replication generated an error (8614):
                The Active Directory cannot replicate with this server because the time since the last replication with this server has exceeded the tombstone lifetime.
                The failure occurred at 2012-08-28 13:00:46.
                The last success occurred at 2011-08-29 11:55:33.
                8752 failures have occurred since the last success.
             REPLICATION LATENCY WARNING
             ERROR: Expected notification link is missing.
             Source W3POPEXCH
             Replication of new changes along this path will be delayed.
             This problem should self-correct on the next periodic sync.
             [Replications Check,W3KADPOPNHUGUACU] A recent replication attempt failed:
                From R410POPEXC to W3KADPOPNHUGUACU
                Naming Context: CN=Schema,CN=Configuration,DC=pop,DC=corp
                The replication generated an error (8524):
                The DSA operation is unable to proceed because of a DNS lookup failure.
                The failure occurred at 2012-08-28 13:00:38.
                The last success occurred at 2012-08-16 02:57:59.
                298 failures have occurred since the last success.
                The guid-based DNS name 982073eb-756d-46e5-8d77-67c07547e751._msdcs.pop.corp
                is not registered on one or more DNS servers.
             [Replications Check,W3KADPOPNHUGUACU] A recent replication attempt failed:
                From R410S1A to W3KADPOPNHUGUACU
                Naming Context: CN=Schema,CN=Configuration,DC=pop,DC=corp
                The replication generated an error (8524):
                The DSA operation is unable to proceed because of a DNS lookup failure.
                The failure occurred at 2012-08-28 13:00:40.
                The last success occurred at 2012-08-15 07:57:59.
                317 failures have occurred since the last success.
                The guid-based DNS name 89feee97-6019-485e-bc31-51be8a8fc383._msdcs.pop.corp
                is not registered on one or more DNS servers.
             [Replications Check,W3KADPOPNHUGUACU] A recent replication attempt failed:
                From R410POPEXC to W3KADPOPNHUGUACU
                Naming Context: CN=Configuration,DC=pop,DC=corp
                The replication generated an error (8524):
                The DSA operation is unable to proceed because of a DNS lookup failure.
                The failure occurred at 2012-08-28 13:00:10.
                The last success occurred at 2012-08-16 02:57:56.
                298 failures have occurred since the last success.
                The guid-based DNS name 982073eb-756d-46e5-8d77-67c07547e751._msdcs.pop.corp
                is not registered on one or more DNS servers.
             [Replications Check,W3KADPOPNHUGUACU] A recent replication attempt failed:
                From G1474-FS to W3KADPOPNHUGUACU
                Naming Context: CN=Configuration,DC=pop,DC=corp
                The replication generated an error (8606):
                Insufficient attributes were given to create an object.  This object may not exist because it may have been deleted and already garbage collected.
                The failure occurred at 2012-08-28 13:00:10.
                The last success occurred at 2012-08-27 16:59:35.
                20 failures have occurred since the last success.
             [Replications Check,W3KADPOPNHUGUACU] A recent replication attempt failed:
                From W3POPEXCH to W3KADPOPNHUGUACU
                Naming Context: CN=Configuration,DC=pop,DC=corp
                The replication generated an error (8606):
                Insufficient attributes were given to create an object.  This object may not exist because it may have been deleted and already garbage collected.
                The failure occurred at 2012-08-28 13:00:10.
                The last success occurred at 2012-08-27 16:59:36.
                20 failures have occurred since the last success.
             [Replications Check,W3KADPOPNHUGUACU] A recent replication attempt failed:
                From R410S1A to W3KADPOPNHUGUACU
                Naming Context: CN=Configuration,DC=pop,DC=corp
                The replication generated an error (8524):
                The DSA operation is unable to proceed because of a DNS lookup failure.
                The failure occurred at 2012-08-28 13:00:12.
                The last success occurred at 2012-08-15 07:57:58.
                317 failures have occurred since the last success.
                The guid-based DNS name 89feee97-6019-485e-bc31-51be8a8fc383._msdcs.pop.corp
                is not registered on one or more DNS servers.
             [Replications Check,W3KADPOPNHUGUACU] A recent replication attempt failed:
                From POPSD to W3KADPOPNHUGUACU
                Naming Context: CN=Configuration,DC=pop,DC=corp
                The replication generated an error (8606):
                Insufficient attributes were given to create an object.  This object may not exist because it may have been deleted and already garbage collected.
                The failure occurred at 2012-08-28 13:00:35.
                The last success occurred at 2012-08-27 18:11:40.
                24 failures have occurred since the last success.
             [Replications Check,W3KADPOPNHUGUACU] A recent replication attempt failed:
                From W3POPEXCH to W3KADPOPNHUGUACU
                Naming Context: DC=pop,DC=corp
                The replication generated an error (8614):
                The Active Directory cannot replicate with this server because the time since the last replication with this server has exceeded the tombstone lifetime.
                The failure occurred at 2012-08-28 13:00:07.
                The last success occurred at 2012-01-12 07:45:52.
                5491 failures have occurred since the last success.
             REPLICATION LATENCY WARNING
             ERROR: Expected notification link is missing.
             Source W3POPEXCH
             Replication of new changes along this path will be delayed.
             This problem should self-correct on the next periodic sync.
             [Replications Check,W3KADPOPNHUGUACU] A recent replication attempt failed:
                From R410POPEXC to W3KADPOPNHUGUACU
                Naming Context: DC=pop,DC=corp
                The replication generated an error (8524):
                The DSA operation is unable to proceed because of a DNS lookup failure.
                The failure occurred at 2012-08-28 13:00:49.
                The last success occurred at (never).
                1868 failures have occurred since the last success.
                The guid-based DNS name 982073eb-756d-46e5-8d77-67c07547e751._msdcs.pop.corp
                is not registered on one or more DNS servers.
             [Replications Check,W3KADPOPNHUGUACU] A recent replication attempt failed:
                From G1474-FS to W3KADPOPNHUGUACU
                Naming Context: DC=pop,DC=corp
                The replication generated an error (8614):
                The Active Directory cannot replicate with this server because the time since the last replication with this server has exceeded the tombstone lifetime.
                The failure occurred at 2012-08-28 13:01:28.
                The last success occurred at (never).
                5094 failures have occurred since the last success.
             [Replications Check,W3KADPOPNHUGUACU] A recent replication attempt failed:
                From R410S1A to W3KADPOPNHUGUACU
                Naming Context: DC=pop,DC=corp
                The replication generated an error (8524):
                The DSA operation is unable to proceed because of a DNS lookup failure.
                The failure occurred at 2012-08-28 13:01:30.
                The last success occurred at (never).
                334 failures have occurred since the last success.
                The guid-based DNS name 89feee97-6019-485e-bc31-51be8a8fc383._msdcs.pop.corp
                is not registered on one or more DNS servers.
             REPLICATION-RECEIVED LATENCY WARNING
             W3KADPOPNHUGUACU:  Current time is 2012-08-28 13:16:01.
                DC=ForestDnsZones,DC=pop,DC=corp
                   Last replication recieved from R410POPEXC at 2012-08-27 10:55:07.
                   Last replication recieved from R410S1A at 2012-08-27 10:55:07.
                   Last replication recieved from G1474-FS at 2012-08-27 10:59:53.
                   Last replication recieved from W3POPEXCH at 2012-08-27 10:59:53.
                DC=DomainDnsZones,DC=pop,DC=corp
                   Last replication recieved from G1474-FS at 2011-09-05 13:55:45.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from W3POPEXCH at 2011-09-05 13:51:30.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                CN=Configuration,DC=pop,DC=corp
                   Last replication recieved from R410POPEXC at 2012-08-27 17:35:52.
                   Last replication recieved from R410S1A at 2012-08-27 17:35:52.
                   Last replication recieved from G1474-FS at 2012-08-27 17:35:52.
                   Last replication recieved from W3POPEXCH at 2012-08-27 17:35:52.
                   Last replication recieved from POPSD at 2012-08-27 18:20:51.
                DC=pop,DC=corp
                   Last replication recieved from G1474-FS at 2012-01-12 07:45:54.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from W3POPEXCH at 2012-01-12 07:45:52.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from POPSD at 2011-12-17 12:42:08.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
             ......................... W3KADPOPNHUGUACU passed test Replications
          Starting test: NCSecDesc
             ......................... W3KADPOPNHUGUACU passed test NCSecDesc
          Starting test: NetLogons
             Unable to connect to the NETLOGON share! (\\W3KADPOPNHUGUACU\netlogon)
             [W3KADPOPNHUGUACU] An net use or LsaPolicy operation failed with error 1203, No network provider accepted the given network path..
             ......................... W3KADPOPNHUGUACU failed test NetLogons
          Starting test: Advertising
             Warning: DsGetDcName returned information for \\W3POPEXCH.pop.corp, when we were trying to reach W3KADPOPNHUGUACU.
             Server is not responding or is not considered suitable.
             Warning: W3KADPOPNHUGUACU is not advertising as a global catalog.
             Check that server finished GC promotion.
             Check the event log on server that enough source replicas for the GC are available.
             ......................... W3KADPOPNHUGUACU failed test Advertising
          Starting test: KnowsOfRoleHolders
             Warning: G1474-FS is the Schema Owner, but is not responding to DS RPC Bind.
             [G1474-FS] LDAP bind failed with error 8341,
             A directory service error has occurred..
             Warning: G1474-FS is the Schema Owner, but is not responding to LDAP Bind.
             Warning: G1474-FS is the Domain Owner, but is not responding to DS RPC Bind.
             Warning: G1474-FS is the Domain Owner, but is not responding to LDAP Bind.
             Warning: G1474-FS is the PDC Owner, but is not responding to DS RPC Bind.
             Warning: G1474-FS is the PDC Owner, but is not responding to LDAP Bind.
             Warning: G1474-FS is the Rid Owner, but is not responding to DS RPC Bind.
             Warning: G1474-FS is the Rid Owner, but is not responding to LDAP Bind.
             Warning: G1474-FS is the Infrastructure Update Owner, but is not responding to DS RPC Bind.
             Warning: G1474-FS is the Infrastructure Update Owner, but is not responding to LDAP Bind.
             ......................... W3KADPOPNHUGUACU failed test KnowsOfRoleHolders
          Starting test: RidManager
             ......................... W3KADPOPNHUGUACU failed test RidManager
          Starting test: MachineAccount
             ***Error: The server W3KADPOPNHUGUACU is missing its machine account.

             Try running with the /repairmachineaccount option. 
             * The current DC is not in the domain controller's OU
             * Missing SPN :LDAP/W3KADPOPNHUGUACU
             * Missing SPN :HOST/W3KADPOPNHUGUACU
             ......................... W3KADPOPNHUGUACU failed test MachineAccount
          Starting test: Services
             ......................... W3KADPOPNHUGUACU passed test Services
          Starting test: ObjectsReplicated
             ......................... W3KADPOPNHUGUACU passed test ObjectsReplicated
          Starting test: frssysvol
             ......................... W3KADPOPNHUGUACU passed test frssysvol
          Starting test: frsevent
             ......................... W3KADPOPNHUGUACU passed test frsevent
          Starting test: kccevent
             An Error Event occured.  EventID: 0xC00007FA
                Time Generated: 08/28/2012   13:01:28
                (Event String could not be retrieved)
             An Error Event occured.  EventID: 0xC00007FA
                Time Generated: 08/28/2012   13:06:56
                (Event String could not be retrieved)
             An Warning Event occured.  EventID: 0x80000785
                Time Generated: 08/28/2012   13:06:56
                Event String: The attempt to establish a replication link for

             An Error Event occured.  EventID: 0xC00007FA
                Time Generated: 08/28/2012   13:06:58
                (Event String could not be retrieved)
             An Warning Event occured.  EventID: 0x80000785
                Time Generated: 08/28/2012   13:06:58
                Event String: The attempt to establish a replication link for

             ......................... W3KADPOPNHUGUACU failed test kccevent
          Starting test: systemlog
             An Error Event occured.  EventID: 0x40000004
                Time Generated: 08/28/2012   12:36:50
                Event String: The kerberos client received a

             An Error Event occured.  EventID: 0x40000004
                Time Generated: 08/28/2012   13:16:05
                Event String: The kerberos client received a

             ......................... W3KADPOPNHUGUACU failed test systemlog
          Starting test: VerifyReferences
             ......................... W3KADPOPNHUGUACU passed test VerifyReferences
       
       Running partition tests on : ForestDnsZones
          Starting test: CrossRefValidation
             ......................... ForestDnsZones passed test CrossRefValidation
          Starting test: CheckSDRefDom
             ......................... ForestDnsZones passed test CheckSDRefDom
       
       Running partition tests on : DomainDnsZones
          Starting test: CrossRefValidation
             ......................... DomainDnsZones passed test CrossRefValidation
          Starting test: CheckSDRefDom
             ......................... DomainDnsZones passed test CheckSDRefDom
       
       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 : pop
          Starting test: CrossRefValidation
             ......................... pop passed test CrossRefValidation
          Starting test: CheckSDRefDom
             ......................... pop passed test CheckSDRefDom
       
       Running enterprise tests on : pop.corp
          Starting test: Intersite
             ......................... pop.corp passed test Intersite
          Starting test: FsmoCheck
             Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355
             A Global Catalog Server could not be located - All GC's are down.
             Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1355
             A Primary Domain Controller could not be located.
             The server holding the PDC role is down.
             ......................... pop.corp failed test FsmoCheck

    Grato pela ajuda até o momento.


    terça-feira, 28 de agosto de 2012 16:16
  • Olá Rafael,

    Não sei se você chegou a ver, mas segue KB com o seu problema: http://support.microsoft.com/kb/2028495

    Tem mais alguns comandos neste KB.

    Sobre o segundo DC ele não está achando o GC nem os FSMOs por causa dos registros DNS do DNS server configurado na placa deste servidor.

    Sugiro comparar os DNS Servers que estão normais com os que estão com problemas de replicação, pois creio que estes que estão faltando registros, como por exemplo, registros SRV.


    Att,

    Elias Shuiti Yasuda
    MCP | MCTS | MCITP | MCSA 2K8 | ITIL v3 | Cobit
    Digisystem - Analista N2 Servidores
    Mestra - Administrador de redes
    "O ser humano evolui ao reconhecer os próprios erros."


    quarta-feira, 29 de agosto de 2012 02:05
    Moderador
  • Vlw Elias.

    Obrigado pela ajuda mas conversando junto com meu chefe, ele optou por efetuar a remoção do DC e a inserção novamente.

    Apesar de um não achar a melhor solução resolveu temporariamente o problema.

    Estamos pensando em refazer o PDC juntamente com os DCS uma vez que eles estão com problemas.

    Mais uma vez obrigado pela ajuda.

    Atenciosamente

    quinta-feira, 30 de agosto de 2012 14:11