询问者
求助：一台备域出现硬件故障修复好后开机出现域内的计算机不定时大面积无法登陆域的情况。
-
如标题，我的域环境共有3台预控：
主域：PDCSVR
备域1：BDCSVR
备域2：BYDCSVR
域控都是windows2003 r2 sp1系统，其中最近备域1：BDCSVR出现硬件故障关了大约两周时间，修复好后备域1开机后出现域管理员密码被清空，域内计算机大面积不能登陆到域的情况，同时还发现没写计算机退域重新加域后重复出现不能登陆域的情况。
查看主域系统日志频繁出现：事件ID 5722 5723 5805
repadmin replsummary 如下：
Replication Summary Start Time: 2017-02-07 15:37:07
Beginning data collection for replication summary, this may take awhile:
........
Destination DC largest delta fails/total %% error
BAKDC >60 days 10 / 15 66 (1722) RPC 服务器不可用。
PDCSVR >60 days 15 / 20 75 (8524) 由于 DNS 查找故障，DSA 操作无法进行。
Experienced the following operational errors trying to retrieve replication information:
58 - bdcsvr.hbhospital.com
58 - TDCSVR.hbhospital.com
58 - BYDCSVR.hbhospital.com
DCDIAG如下：
Domain Controller Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\PDCSVR
Starting test: Connectivity
......................... PDCSVR passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\PDCSVR
Starting test: Replications
[Replications Check,PDCSVR] A recent replication attempt failed:
From TDCSVR to PDCSVR
Naming Context: DC=ForestDnsZones,DC=hbhospital,DC=com
The replication generated an error (1256):
远程系统不可用。有关网络疑难解答，请参阅 Windows 帮助。
The failure occurred at 2017-02-07 14:59:39.
The last success occurred at 2016-08-10 09:51:28.
4350 failures have occurred since the last success.
[TDCSVR] DsBindWithSpnEx() failed with error 1722,
RPC 服务器不可用。.
[Replications Check,PDCSVR] A recent replication attempt failed:
From BDCSVR to PDCSVR
Naming Context: DC=ForestDnsZones,DC=hbhospital,DC=com
The replication generated an error (1256):
远程系统不可用。有关网络疑难解答，请参阅 Windows 帮助。
The failure occurred at 2017-02-07 15:00:02.
The last success occurred at 2016-11-20 02:59:46.
1909 failures have occurred since the last success.
[BDCSVR] DsBindWithSpnEx() failed with error 1722,
RPC 服务器不可用。.
[Replications Check,PDCSVR] A recent replication attempt failed:
From BYDCSVR to PDCSVR
Naming Context: DC=ForestDnsZones,DC=hbhospital,DC=com
The replication generated an error (1256):
远程系统不可用。有关网络疑难解答，请参阅 Windows 帮助。
The failure occurred at 2017-02-07 15:00:05.
The last success occurred at 2016-12-30 07:58:44.
943 failures have occurred since the last success.
[BYDCSVR] DsBindWithSpnEx() failed with error 1722,
RPC 服务器不可用。.
[Replications Check,PDCSVR] A recent replication attempt failed:
From TDCSVR to PDCSVR
Naming Context: DC=DomainDnsZones,DC=hbhospital,DC=com
The replication generated an error (1256):
远程系统不可用。有关网络疑难解答，请参阅 Windows 帮助。
The failure occurred at 2017-02-07 14:59:39.
The last success occurred at 2016-08-10 09:51:28.
4350 failures have occurred since the last success.
[Replications Check,PDCSVR] A recent replication attempt failed:
From BDCSVR to PDCSVR
Naming Context: DC=DomainDnsZones,DC=hbhospital,DC=com
The replication generated an error (1256):
远程系统不可用。有关网络疑难解答，请参阅 Windows 帮助。
The failure occurred at 2017-02-07 15:00:02.
The last success occurred at 2016-11-20 02:59:46.
1909 failures have occurred since the last success.
[Replications Check,PDCSVR] A recent replication attempt failed:
From BYDCSVR to PDCSVR
Naming Context: DC=DomainDnsZones,DC=hbhospital,DC=com
The replication generated an error (1256):
远程系统不可用。有关网络疑难解答，请参阅 Windows 帮助。
The failure occurred at 2017-02-07 15:00:05.
The last success occurred at 2016-12-30 08:15:34.
1135 failures have occurred since the last success.
[Replications Check,PDCSVR] A recent replication attempt failed:
From TDCSVR to PDCSVR
Naming Context: CN=Schema,CN=Configuration,DC=hbhospital,DC=com
The replication generated an error (8524):
由于 DNS 查找故障，DSA 操作无法进行。
The failure occurred at 2017-02-07 15:00:07.
The last success occurred at 2016-08-10 09:51:28.
4350 failures have occurred since the last success.
The guid-based DNS name f0594f0f-a550-4f23-b90e-3ea27347f34e._msdcs.hbhospital.com
is not registered on one or more DNS servers.
[Replications Check,PDCSVR] A recent replication attempt failed:
From BDCSVR to PDCSVR
Naming Context: CN=Schema,CN=Configuration,DC=hbhospital,DC=com
The replication generated an error (1722):
RPC 服务器不可用。
The failure occurred at 2017-02-07 15:00:28.
The last success occurred at 2016-11-20 02:59:04.
1909 failures have occurred since the last success.
The source remains down. Please check the machine.
[Replications Check,PDCSVR] A recent replication attempt failed:
From BYDCSVR to PDCSVR
Naming Context: CN=Schema,CN=Configuration,DC=hbhospital,DC=com
The replication generated an error (8524):
由于 DNS 查找故障，DSA 操作无法进行。
The failure occurred at 2017-02-07 15:00:31.
The last success occurred at 2016-12-30 07:58:23.
943 failures have occurred since the last success.
The guid-based DNS name db58865d-fd5b-4df4-b84a-4d34f2717cc5._msdcs.hbhospital.com
is not registered on one or more DNS servers.
[Replications Check,PDCSVR] A recent replication attempt failed:
From TDCSVR to PDCSVR
Naming Context: CN=Configuration,DC=hbhospital,DC=com
The replication generated an error (8524):
由于 DNS 查找故障，DSA 操作无法进行。
The failure occurred at 2017-02-07 14:59:41.
The last success occurred at 2016-08-10 09:51:28.
4350 failures have occurred since the last success.
The guid-based DNS name f0594f0f-a550-4f23-b90e-3ea27347f34e._msdcs.hbhospital.com
is not registered on one or more DNS servers.
[Replications Check,PDCSVR] A recent replication attempt failed:
From BDCSVR to PDCSVR
Naming Context: CN=Configuration,DC=hbhospital,DC=com
The replication generated an error (1722):
RPC 服务器不可用。
The failure occurred at 2017-02-07 15:00:02.
The last success occurred at 2016-11-20 02:59:02.
1909 failures have occurred since the last success.
The source remains down. Please check the machine.
[Replications Check,PDCSVR] A recent replication attempt failed:
From BYDCSVR to PDCSVR
Naming Context: CN=Configuration,DC=hbhospital,DC=com
The replication generated an error (8524):
由于 DNS 查找故障，DSA 操作无法进行。
The failure occurred at 2017-02-07 15:00:05.
The last success occurred at 2016-12-30 07:57:59.
1758 failures have occurred since the last success.
The guid-based DNS name db58865d-fd5b-4df4-b84a-4d34f2717cc5._msdcs.hbhospital.com
is not registered on one or more DNS servers.
[Replications Check,PDCSVR] A recent replication attempt failed:
From TDCSVR to PDCSVR
Naming Context: DC=hbhospital,DC=com
The replication generated an error (8524):
由于 DNS 查找故障，DSA 操作无法进行。
The failure occurred at 2017-02-07 14:59:39.
The last success occurred at 2016-08-10 09:54:29.
4350 failures have occurred since the last success.
The guid-based DNS name f0594f0f-a550-4f23-b90e-3ea27347f34e._msdcs.hbhospital.com
is not registered on one or more DNS servers.
[Replications Check,PDCSVR] A recent replication attempt failed:
From BDCSVR to PDCSVR
Naming Context: DC=hbhospital,DC=com
The replication generated an error (1722):
RPC 服务器不可用。
The failure occurred at 2017-02-07 15:00:52.
The last success occurred at 2016-11-20 03:02:14.
1910 failures have occurred since the last success.
The source remains down. Please check the machine.
[Replications Check,PDCSVR] A recent replication attempt failed:
From BYDCSVR to PDCSVR
Naming Context: DC=hbhospital,DC=com
The replication generated an error (8524):
由于 DNS 查找故障，DSA 操作无法进行。
The failure occurred at 2017-02-07 15:15:01.
The last success occurred at 2016-12-30 08:22:11.
1944 failures have occurred since the last success.
The guid-based DNS name db58865d-fd5b-4df4-b84a-4d34f2717cc5._msdcs.hbhospital.com
is not registered on one or more DNS servers.
REPLICATION-RECEIVED LATENCY WARNING
PDCSVR: Current time is 2017-02-07 15:35:53.
DC=ForestDnsZones,DC=hbhospital,DC=com
Last replication recieved from TDCSVR at 2016-08-10 09:51:28.
WARNING: This latency is over the Tombstone Lifetime of 180 days!
Last replication recieved from BYDCSVR at 2016-12-30 07:59:22.
Last replication recieved from BDCSVR at 2016-11-20 02:59:46.
DC=DomainDnsZones,DC=hbhospital,DC=com
Last replication recieved from TDCSVR at 2016-08-10 09:51:28.
WARNING: This latency is over the Tombstone Lifetime of 180 days!
Last replication recieved from BYDCSVR at 2016-12-30 08:15:34.
Last replication recieved from BDCSVR at 2016-11-20 02:59:46.
CN=Schema,CN=Configuration,DC=hbhospital,DC=com
Last replication recieved from TDCSVR at 2016-08-10 09:51:28.
WARNING: This latency is over the Tombstone Lifetime of 180 days!
Last replication recieved from BYDCSVR at 2016-12-30 07:59:01.
Last replication recieved from BDCSVR at 2016-11-20 02:59:04.
CN=Configuration,DC=hbhospital,DC=com
Last replication recieved from TDCSVR at 2016-08-10 09:51:28.
WARNING: This latency is over the Tombstone Lifetime of 180 days!
Last replication recieved from BYDCSVR at 2016-12-30 07:59:00.
Last replication recieved from BDCSVR at 2016-11-20 02:59:02.
DC=hbhospital,DC=com
Last replication recieved from TDCSVR at 2016-08-10 09:54:45.
WARNING: This latency is over the Tombstone Lifetime of 180 days!
Last replication recieved from BYDCSVR at 2016-12-30 08:22:11.
Last replication recieved from BDCSVR at 2016-11-20 03:02:17.
......................... PDCSVR passed test Replications
Starting test: NCSecDesc
......................... PDCSVR passed test NCSecDesc
Starting test: NetLogons
......................... PDCSVR passed test NetLogons
Starting test: Advertising
......................... PDCSVR passed test Advertising
Starting test: KnowsOfRoleHolders
......................... PDCSVR passed test KnowsOfRoleHolders
Starting test: RidManager
......................... PDCSVR passed test RidManager
Starting test: MachineAccount
......................... PDCSVR passed test MachineAccount
Starting test: Services
......................... PDCSVR passed test Services
Starting test: ObjectsReplicated
......................... PDCSVR passed test ObjectsReplicated
Starting test: frssysvol
......................... PDCSVR passed test frssysvol
Starting test: frsevent
......................... PDCSVR passed test frsevent
Starting test: kccevent
......................... PDCSVR passed test kccevent
Starting test: systemlog
An Error Event occured. EventID: 0x0000165B
Time Generated: 02/07/2017 14:58:30
Event String: The session setup from computer 'MININT-G06N0GP'
An Error Event occured. EventID: 0x000016AD
Time Generated: 02/07/2017 15:00:24
Event String: The session setup from the computer
An Error Event occured. EventID: 0x00000457
Time Generated: 02/07/2017 15:02:46
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 02/07/2017 15:02:46
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 02/07/2017 15:02:47
(Event String could not be retrieved)
An Error Event occured. EventID: 0x000016AD
Time Generated: 02/07/2017 15:21:19
Event String: The session setup from the computer ZYNK-EMR-3404
An Error Event occured. EventID: 0x0000165B
Time Generated: 02/07/2017 15:33:12
Event String: The session setup from computer 'JYK-WSHW-06'
......................... PDCSVR failed test systemlog
Starting test: VerifyReferences
......................... PDCSVR 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 : hbhospital
Starting test: CrossRefValidation
......................... hbhospital passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... hbhospital passed test CheckSDRefDom
Running enterprise tests on : hbhospital.com
Starting test: Intersite
......................... hbhospital.com passed test Intersite
Starting test: FsmoCheck
......................... hbhospital.com passed test FsmoCheck其中主备域都部署了DNS，目前把备域1：BDCSVR关机了，在主域PDCSVR，使用NSLOOKUP 测试解析正常，判断DNS正常。
工作站DNS配置首先DNS指向主域PDCSVR的IP，备用DNS指向备域BDCSVR的IP。
~~~~~~~~~~~~~~~~~
注：上面的检查结果中‘TDCSVR ’这台域已经不存在了，是老的域控遗留下来的垃圾信息。‘备域2：BYDCSVR’这台备域控制器一直没有使用，出现故障没影响使用所以一直没管他。
问题
全部回复
-
你好！
请问您的备域控出现硬件故障是怎么修复的？又是如何重新加入域的？
备域控在出现硬件故障之前有没有哪些操作主机的角色安装在上面？
我建议检查域中操作主机在哪些域控上。
关于如何查看哪些域控上安装了操作主机，请参考下面这篇文章。
How to find out who has your FSMO Roles
https://blogs.technet.microsoft.com/mempson/2007/11/08/how-to-find-out-who-has-your-fsmo-roles/
Best Regards,
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.- 已建议为答案 Jay GuModerator 2017年2月28日 15:01
-
你好！
如果以上的回复解决了您的问题，请把它标记成答案。
谢谢。
Best Regards,
Jay
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
