询问者
域控复制问题 error 1727 error 55

问题
-
父域:domain.cn 域控:PRODDC-3,PRODDC-4
子域:wuhan.domain.cn 域控:PRODDC-1,PRODDC-2
问题描述:
使用父域的账号登录子域加域的部分计算机,会提示用户名和密码错误。
两台子域域控的防火墙已关闭,可以互相ping通,端口也是通的。
检查日志发现PRODDC-2无法从PRODDC-1复制数据,以下是dcdiag test失败的部分。
......................... PRODDC-2 failed test KccEvent
Starting test: KnowsOfRoleHolders
[PRODDC-1] DsBindWithSpnEx() failed with error 1727,
The remote procedure call failed and did not execute..
Warning: PRODDC-1 is the PDC Owner, but is not responding to DSRPC Bind.
[PRODDC-1] LDAP bind failed with error 55,
The specified network resource or device is no longer available..
Warning: PRODDC-1 is the PDC Owner, but is not responding to LDAPBind.
Warning: PRODDC-1 is the Rid Owner, but is not responding to DS
RPC Bind.
Warning: PRODDC-1 is the Rid Owner, but is not responding to LDAP
Bind.
Warning: PRODDC-1 is the Infrastructure Update Owner, but is not
responding to DS RPC Bind.
Warning: PRODDC-1 is the Infrastructure Update Owner, but is not
responding to LDAP Bind.
Starting test: ReplicationsREPLICATION LATENCY WARNING
ERROR: Expected notification link is missing.
Source PRODDC-4
Replication of new changes along this path will be delayed.
This problem should self-correct on the next periodic sync.
[Replications Check,PRODDC-2] A recent replication attempt
failed:
From PRODDC-1 to PRODDC-2
Naming Context: DC=ForestDnsZones,DC=domain,DC=cn
The replication generated an error (1256):
The remote system is not available. For information about network troubleshooting, see Windows Help.
The failure occurred at 2017-04-17 10:51:29.
The last success occurred at 2017-04-17 10:28:09.
2 failures have occurred since the last success.
[Replications Check,PRODDC-2] A recent replication attempt
failed:
From PRODDC-1 to PRODDC-2
Naming Context: CN=Schema,CN=Configuration,DC=domain,DC=cn
The replication generated an error (1727):
The remote procedure call failed and did not execute.
The failure occurred at 2017-04-17 10:54:38.
The last success occurred at 2017-04-17 10:37:58.
1 failures have occurred since the last success.
[Replications Check,PRODDC-2] A recent replication attempt
failed:
From PRODDC-1 to PRODDC-2
Naming Context: CN=Configuration,DC=domain,DC=cn
The replication generated an error (1727):
The remote procedure call failed and did not execute.
The failure occurred at 2017-04-17 10:53:23.
The last success occurred at 2017-04-17 10:37:08.
1 failures have occurred since the last success.
[Replications Check,PRODDC-2] A recent replication attempt
failed:
From PRODDC-1 to PRODDC-2
Naming Context: DC=domain,DC=cn
The replication generated an error (1256):
The remote system is not available. For information about network troubleshooting, see Windows Help.
The failure occurred at 2017-04-17 10:51:29.
The last success occurred at 2017-04-17 10:36:18.
1 failures have occurred since the last success.
[Replications Check,PRODDC-2] A recent replication attempt
failed:
From PRODDC-1 to PRODDC-2
Naming Context: DC=wuhan,DC=domain,DC=cn
The replication generated an error (1727):
The remote procedure call failed and did not execute.
The failure occurred at 2017-04-17 10:51:29.
The last success occurred at 2017-04-11 15:44:57.
15586 failures have occurred since the last success.
......................... PRODDC-2 failed test Replications
全部回复
-
Hi,
在这台DC 是否安装的其他的三方软件特别是杀毒软件?有的话暂时disable 查看一下。
另外检查防护墙是不是屏蔽了部分AD 所需的端口。
https://technet.microsoft.com/en-us/library/dd772723%28WS.10%29.aspx?f=255&MSPPError=-2147217396
在 AD 复制环境,目标 DC 上的 RPC 客户端无法成功连接到的源 DC 上的 RPC 服务器。这样的常见原因是︰
- 链路本地故障
- DHCP 故障
- DNS 故障
- WINS 失败
- 路由故障 (包括防火墙阻止的端口)
- IPSec / 网络身份验证失败
- 资源限制
- 更高层的协议未运行
- 返回此错误的更高层的协议
建议你根据以下的KB来排错.
另外你还可以查看一下event viewer, 是否有其他错误信息。
Best Regards,
Mary
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.- 已建议为答案 Mary DongModerator 2017年4月25日 6:59
-
Hi,
如果你有更多的的更新也可以继续分享讨论。
Best Regards,
Mary
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com. -
没找到问题所在。
直接降级->退域->加域->升级域控,解决了。
计算机名称和IP都没变,服务正常。
- 已建议为答案 Mary DongModerator 2017年8月2日 8:48