Eu tenho dois controladores de domínio:
DC1: Win2k3 R2 EGDC1: Win2k8 R2
Quando tento replicar esses dois (via Manage Sites and Services e NTDS Settings ) selecionando Replicate Now , recebo a mensagem de erro The RPC Server is unavailable . Não importa se eu tentar isso enquanto remotamente em DC1 ou DC2.
De acordo com este artigo de technet , este é um problema com a queda de uma máquina. No entanto, eu também posso fazer com que ambos os controladores de domínio façam ping uns aos outros sem problemas, então não há nenhum problema de DNS nem nenhum problema de conectividade. Ambos estão na mesma LAN e até na mesma sub-rede, portanto, nenhum problema de VPN / wifi / firewall / peculiar como esse deve ser um problema.
Além disso, verifiquei que o serviço RPC está sendo executado nas duas caixas.
Qual poderia ser o problema e como eu resolveria isso?
resultados dcdiag:
Directory Server Diagnosis
Performing initial setup:
Trying to find home server...
Home Server = EGDC1
* Identified AD Forest.
Ldap search capabality attribute search failed on server DC1, return value =
81
Got error while checking if the DC is using FRS or DFSR. Error:
Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail
because of this error.
Done gathering initial info.
Doing initial required tests
Testing server: INF\EGDC1
Starting test: Connectivity
......................... EGDC1 passed test Connectivity
Doing primary tests
Testing server: INF\EGDC1
Starting test: Advertising
......................... EGDC1 passed test Advertising
Starting test: FrsEvent
......................... EGDC1 passed test FrsEvent
Starting test: DFSREvent
......................... EGDC1 passed test DFSREvent
Starting test: SysVolCheck
......................... EGDC1 passed test SysVolCheck
Starting test: KccEvent
......................... EGDC1 passed test KccEvent
Starting test: KnowsOfRoleHolders
[DC1] DsBindWithSpnEx() failed with error 1722,
The RPC server is unavailable..
Warning: DC1 is the Schema Owner, but is not responding to DS RPC
Bind.
Warning: DC1 is the Schema Owner, but is not responding to LDAP Bind.
Warning: DC1 is the Domain Owner, but is not responding to DS RPC
Bind.
Warning: DC1 is the Domain Owner, but is not responding to LDAP Bind.
Warning: DC1 is the PDC Owner, but is not responding to DS RPC Bind.
Warning: DC1 is the PDC Owner, but is not responding to LDAP Bind.
Warning: DC1 is the Rid Owner, but is not responding to DS RPC Bind.
Warning: DC1 is the Rid Owner, but is not responding to LDAP Bind.
Warning: DC1 is the Infrastructure Update Owner, but is not responding
to DS RPC Bind.
Warning: DC1 is the Infrastructure Update Owner, but is not responding
to LDAP Bind.
......................... EGDC1 failed test KnowsOfRoleHolders
Starting test: MachineAccount
......................... EGDC1 passed test MachineAccount
Starting test: NCSecDesc
Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
Replicating Directory Changes In Filtered Set
access rights for the naming context:
DC=ForestDnsZones,DC=eg,DC=local
Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
Replicating Directory Changes In Filtered Set
access rights for the naming context:
DC=DomainDnsZones,DC=eg,DC=local
......................... EGDC1 failed test NCSecDesc
Starting test: NetLogons
......................... EGDC1 passed test NetLogons
Starting test: ObjectsReplicated
......................... EGDC1 passed test ObjectsReplicated
Starting test: Replications
[Replications Check,EGDC1] A recent replication attempt failed:
From DC1 to EGDC1
Naming Context: DC=ForestDnsZones,DC=eg,DC=local
The replication generated an error (1256):
The remote system is not available. For information about network tr
oubleshooting, see Windows Help.
The failure occurred at 2010-11-29 08:56:33.
The last success occurred at 2010-10-05 01:10:06.
1330 failures have occurred since the last success.
[Replications Check,EGDC1] A recent replication attempt failed:
From DC1 to EGDC1
Naming Context: DC=DomainDnsZones,DC=eg,DC=local
The replication generated an error (1256):
The remote system is not available. For information about network tr
oubleshooting, see Windows Help.
The failure occurred at 2010-11-29 08:56:33.
The last success occurred at 2010-10-05 01:10:03.
1330 failures have occurred since the last success.
[Replications Check,EGDC1] A recent replication attempt failed:
From DC1 to EGDC1
Naming Context: CN=Schema,CN=Configuration,DC=eg,DC=local
The replication generated an error (1722):
The RPC server is unavailable.
The failure occurred at 2010-11-29 08:57:15.
The last success occurred at 2010-10-05 00:48:18.
1330 failures have occurred since the last success.
The source remains down. Please check the machine.
[Replications Check,EGDC1] A recent replication attempt failed:
From DC1 to EGDC1
Naming Context: CN=Configuration,DC=eg,DC=local
The replication generated an error (1722):
The RPC server is unavailable.
The failure occurred at 2010-11-29 08:56:54.
The last success occurred at 2010-10-05 00:48:18.
1330 failures have occurred since the last success.
The source remains down. Please check the machine.
[Replications Check,EGDC1] A recent replication attempt failed:
From DC1 to EGDC1
Naming Context: DC=eg,DC=local
The replication generated an error (1722):
The RPC server is unavailable.
The failure occurred at 2010-11-29 08:56:33.
The last success occurred at 2010-10-05 01:09:58.
1331 failures have occurred since the last success.
The source remains down. Please check the machine.
......................... EGDC1 failed test Replications
Starting test: RidManager
......................... EGDC1 failed test RidManager
Starting test: Services
......................... EGDC1 passed test Services
Starting test: SystemLog
......................... EGDC1 passed test SystemLog
Starting test: VerifyReferences
......................... EGDC1 passed test VerifyReferences
Running partition tests on : ForestDnsZones
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation
Running partition tests on : DomainDnsZones
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... DomainDnsZones passed test
CrossRefValidation
Running partition tests on : Schema
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Running partition tests on : Configuration
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Running partition tests on : eg
Starting test: CheckSDRefDom
......................... eg passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... eg passed test CrossRefValidation
Running enterprise tests on : eg.local
Starting test: LocatorCheck
......................... eg.local passed test LocatorCheck
Starting test: Intersite
......................... eg.local passed test Intersite
Parece que foi replicado pela última vez em 10-05, o que mudou depois? Meu palpite é que você tem algum tipo de incompatibilidade nos registros SRV no DNS para os dois DCs. A replicação do AD precisa de mais do que apenas o registro A que o ping usa, portanto, o Ping pode fornecer um falso negativo em relação à integridade do DNS. Tente definir os dois servidores para o mesmo servidor DNS e reinicie o serviço netlogin em ambos. Em seguida, tente a replicação novamente.
Um dcdiag /fix registrará novamente os registros DNS do DC e deverá corrigir isso.
Você pode ajustar a porta RPC no registro e depois reiniciá-la assim que terminar.
regedit- > máquina local > software > microsoft & rt; rpc > internet, em seguida, altera a porta do padrão 5000-5002 para 5000-5200 (o ajuste mínimo é 200).
Atenciosamente,
El-IT-ista
Tente isto:
ipconfig /flushdns
repadmin /syncall /AeDP