Parece que estou tendo um problema com a replicação entre nossos controladores de domínio. A configuração é a seguinte:
um domínio
dois controladores de domínio (2008)
um é virtualizado
um é físico
mesmo site
ping entre controladores de domínio é bom.
Ok, basicamente tive que fazer uma atualização do BIOS para o servidor que estava hospedando as máquinas virtuais (o controlador de domínio era uma das máquinas virtuais). Após a atualização, tivemos um problema com o nosso Cisco Switch, já que as portas inteligentes estavam habilitadas e parando o tráfego entre todas as máquinas virtuais e a rede física que contém todas as outras máquinas físicas.
Agora, corrigimos isso desabilitando as portas inteligentes no 2960 e todas as máquinas virtuais podem se comunicar com êxito com as máquinas físicas e está tudo bem.
Contudo; Quando começamos a VM para o controlador de domínio demorou muito tempo para iniciar (comum com problemas de AD / DNS que eu conheço). Quando finalmente iniciei o login e imediatamente tentei fazer o ping no segundo DC. O ping respondeu bem e tudo estava ok rede sábia. Mas, de repente, os controladores de domínio não estão sincronizando. Eu tentei repadmin / syncall e erros estão chegando, eu tentei dcdiag / q e também estou recebendo erros.
O serviço RPC não pode se comunicar com o portador do FSMO (em suma).
Eu verifiquei e o serviço dfsr está funcionando bem. Troquei de firewalls e antivírus e eles ainda não podem se comunicar, exceto com ping. Nada mudou em nada ??
Alguém pode me indicar a direção certa de onde começar?
Para fins de teste, criei um objeto no segundo DC e ele não foi replicado para o primeiro DC (titular do FSMO).
C:\Users\Administrator>dcdiag /q
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.
......................... IME-DC1 failed test DFSREvent
[Replications Check,IME-DC1] A recent replication attempt failed:
From IME-DC2 to IME-DC1
Naming Context: DC=ForestDnsZones,DC=XXX,DC=com
The replication generated an error (1726):
The remote procedure call failed.
The failure occurred at 2013-10-02 21:11:34.
The last success occurred at 2013-10-02 20:05:07.
2 failures have occurred since the last success.
[Replications Check,IME-DC1] A recent replication attempt failed:
From IME-DC2 to IME-DC1
Naming Context: DC=DomainDnsZones,DC=XXX,DC=com
The replication generated an error (1726):
The remote procedure call failed.
The failure occurred at 2013-10-02 21:09:56.
The last success occurred at 2013-10-02 20:04:39.
2 failures have occurred since the last success.
[Replications Check,IME-DC1] A recent replication attempt failed:
From IME-DC2 to IME-DC1
Naming Context: CN=Schema,CN=Configuration,DC=XXX,DC=com
The replication generated an error (1726):
The remote procedure call failed.
The failure occurred at 2013-10-02 21:02:40.
The last success occurred at 2013-10-02 17:55:42.
6 failures have occurred since the last success.
[Replications Check,IME-DC1] A recent replication attempt failed:
From IME-DC2 to IME-DC1
Naming Context: CN=Configuration,DC=XXX,DC=com
The replication generated an error (1726):
The remote procedure call failed.
The failure occurred at 2013-10-02 20:57:56.
The last success occurred at 2013-10-02 20:04:36.
3 failures have occurred since the last success.
[Replications Check,IME-DC1] A recent replication attempt failed:
From IME-DC2 to IME-DC1
Naming Context: DC=XXX,DC=com
The replication generated an error (1726):
The remote procedure call failed.
The failure occurred at 2013-10-02 21:05:29.
The last success occurred at 2013-10-02 20:05:10.
2 failures have occurred since the last success.
......................... IME-DC1 failed test Replications
An Error Event occurred. EventID: 0x00000457
Time Generated: 10/02/2013 21:47:42
Event String:
Driver Microsoft XPS Document Writer v4 required for printer Microso
ft XPS Document Writer is unknown. Contact the administrator to install the driv
er before you log in again.
......................... IME-DC1 failed test SystemLog
C:\Users\Administrator>
Eu também incluí um erro de log de eventos do log do diretório ativo.
Log Name: Directory Service
Source: Microsoft-Windows-ActiveDirectory_DomainService
Date: 02/10/2013 22:13:33
Event ID: 1308
Task Category: Knowledge Consistency Checker
Level: Warning
Keywords: Classic
User: ANONYMOUS LOGON
Computer: IME-DC1.XXX.com
Description:
The Knowledge Consistency Checker (KCC) has detected that successive attempts to replicate with the following directory service has consistently failed.
Attempts:
7
Directory service:
CN=NTDS Settings,CN=IME-DC2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=XXX,DC=com
Period of time (minutes):
128
The Connection object for this directory service will be ignored, and a new temporary connection will be established to ensure that replication continues. Once replication with this directory service resumes, the temporary connection will be removed.
Additional Data
Error value:
1818 The remote procedure call was cancelled.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-ActiveDirectory_DomainService" Guid="{0e8478c5-3605-4e8c-8497-1e730c959516}" EventSourceName="NTDS KCC" />
<EventID Qualifiers="32768">1308</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>1</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2013-10-02T18:13:33.071Z" />
<EventRecordID>12274</EventRecordID>
<Correlation />
<Execution ProcessID="652" ThreadID="1332" />
<Channel>Directory Service</Channel>
<Computer>IME-DC1.XXX.com</Computer>
<Security UserID="S-1-5-7" />
</System>
<EventData>
<Data>7</Data>
<Data>CN=NTDS Settings,CN=IME-DC2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=XXX,DC=com</Data>
<Data>128</Data>
<Data>The remote procedure call was cancelled.</Data>
<Data>1818</Data>
</EventData>
</Event>