复制域控制器时,“RPC服务器不可用”

我有两个域控制器

DC1:Win2k3 R2 EGDC1:Win2k8 R2

当我尝试复制这两个(通过Manage Sites and Services并在NTDS Settings )通过selectReplicate Now ,我收到错误消息The RPC Server is unavailable 。 如果我在遥控DC1或DC2的情况下尝试此操作并不重要。

根据这个technet文章 ,这是一个机器被closures的问题。 不过,我可以另外有两个域控制器相互ping通,所以没有DNS问题,也没有任何连接问题。 两者都在同一局域网上,甚至在同一个子网上,所以没有像这样的VPN / WIFI /防火墙/古怪的问题应该是一个问题。

另外,我validation了RPC服务在两个盒子上运行。

有什么问题可以解决吗?

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 

它看起来像上次在10-05复制,那么改变了什么? 我的猜测是你在两个DC的DNS中的SRVlogging有一些不匹配。 AD复制需要的不仅仅是Ping使用的Alogging,所以Ping可以给你一个关于DNS健康的假阴性。 尝试将两台服务器设置为相同的DNS服务器,然后重启两者上的netlogin服务。 然后再次尝试复制。

一个dcdiag /fix将重新注册该DC的DNSlogging,并应该解决这个问题。

您可以调整registry中的RPC端口,然后您必须重新启动一次完成。

registry编辑器 – >本地机器 – >软件 – > microsoft – > rpc-> internet,然后将端口从默认5000-5002更改为5000-5200(最小调整为200)。

问候,

EL-IT-ISTA

尝试这个 :

  1. 不要将本地服务器指向DNS
  2. 运行ipconfig /flushdns
  3. 重新启动netlogon服务
  4. 运行repadmin /syncall /AeDP