День добрый! Ситуация такая, есть 3 DC, на всех трех работает DNS, упорно не хочет ходить репликация между некоторыми серверами.
Результат replmon c основонго КД:
Active Directory Replication Domain Controller Replication Failure Output
Printed at 04.12.2012 12:38:23
Below are the replication failures detected on Domain Controllers for this domain:
Domain Controller Name: APPS
Directory Partition: DC=mkmgr,DC=local
Replication Partner: Default-First-Site-NameBCD
Failure Code: 1722
Failure Reason: Сервер RPC недоступен.
Domain Controller Name: APPS
Directory Partition: CN=Configuration,DC=mkmgr,DC=local
Replication Partner: Default-First-Site-NameBCD
Failure Code: 1722
Failure Reason: Сервер RPC недоступен.
Domain Controller Name: APPS
Directory Partition: CN=Schema,CN=Configuration,DC=mkmgr,DC=local
Replication Partner: Default-First-Site-NameBCD
Failure Code: 1722
Failure Reason: Сервер RPC недоступен.
Domain Controller Name: APPS
Directory Partition: DC=DomainDnsZones,DC=mkmgr,DC=local
Replication Partner: Default-First-Site-NameBCD
Failure Code: 1256
Failure Reason: Удаленная система недоступна. За информацией о разрешении проблем в сети, обратитесь к справочной
системе Windows.
Domain Controller Name: APPS
Directory Partition: DC=ForestDnsZones,DC=mkmgr,DC=local
Replication Partner: Default-First-Site-NameBCD
Failure Code: 1256
Failure Reason: Удаленная система недоступна. За информацией о разрешении проблем в сети, обратитесь к справочной
системе Windows.
Domain Controller Name: PDC
Directory Partition: DC=mkmgr,DC=local
Replication Partner: Default-First-Site-NameBCD
Failure Code: 1722
Failure Reason: Сервер RPC недоступен.
Domain Controller Name: PDC
Directory Partition: CN=Configuration,DC=mkmgr,DC=local
Replication Partner: Default-First-Site-NameBCD
Failure Code: 1722
Failure Reason: Сервер RPC недоступен.
Domain Controller Name: PDC
Directory Partition: CN=Schema,CN=Configuration,DC=mkmgr,DC=local
Replication Partner: Default-First-Site-NameBCD
Failure Code: 1722
Failure Reason: Сервер RPC недоступен.
Domain Controller Name: PDC
Directory Partition: DC=DomainDnsZones,DC=mkmgr,DC=local
Replication Partner: Default-First-Site-NameBCD
Failure Code: 1256
Failure Reason: Удаленная система недоступна. За информацией о разрешении проблем в сети, обратитесь к справочной
системе Windows.
Domain Controller Name: PDC
Directory Partition: DC=ForestDnsZones,DC=mkmgr,DC=local
Replication Partner: Default-First-Site-NameBCD
Failure Code: 1256
Failure Reason: Удаленная система недоступна. За информацией о разрешении проблем в сети, обратитесь к справочной
системе Windows.
Основной КД : Server 2003
Настройка протокола IP для Windows
Имя компьютера . . . . . . . . . : bcd
Основной DNS-суффикс . . . . . . : mkmgr.local
Тип узла. . . . . . . . . . . . . : неизвестный
IP-маршрутизация включена . . . . : нет
WINS-прокси включен . . . . . . . : нет
Порядок просмотра суффиксов DNS . : mkmgr.local
Подключение по локальной сети — Ethernet адаптер:
DNS-суффикс этого подключения . . :
Описание . . . . . . . . . . . . : Embedded Broadcom NetXtreme 5721 PCI-E Gigabit NIC
Физический адрес. . . . . . . . . : 00-13-21-B4-D6-3B
DHCP включен. . . . . . . . . . . : нет
IP-адрес . . . . . . . . . . . . : 192.168.1.2
Маска подсети . . . . . . . . . . : 255.255.255.0
Основной шлюз . . . . . . . . . . : 192.168.1.11
DNS-серверы . . . . . . . . . . . : 192.168.1.2
192.168.1.11
Резервный КД
Настройка протокола IP для Windows
Имя компьютера . . . . . . . . . : APPS
Основной DNS-суффикс . . . . . . : mkmgr.local
Тип узла. . . . . . . . . . . . . : Гибридный
IP-маршрутизация включена . . . . : Да
WINS-прокси включен . . . . . . . : Нет
Порядок просмотра суффиксов DNS . : mkmgr.local
Ethernet adapter Подключение по локальной сети 2:
DNS-суффикс подключения . . . . . :
Описание. . . . . . . . . . . . . : Адаптер Broadcom NetXtreme для сети Ethernet, 1 Гбит/с #2
Физический адрес. . . . . . . . . : 00-05-5D-4E-CF-40
DHCP включен. . . . . . . . . . . : Нет
Автонастройка включена. . . . . . : Да
IPv4-адрес. . . . . . . . . . . . : 212.44.***.***(Основной)
Маска подсети . . . . . . . . . . : 255.255.255.192
Основной шлюз. . . . . . . . . : 212.44.132.65
DNS-серверы. . . . . . . . . . . : 212.44.132.65
212.44.130.6
NetBios через TCP/IP. . . . . . . . : Включен
Ethernet adapter Подключение по локальной сети:
DNS-суффикс подключения . . . . . : mkmgr.local
Описание. . . . . . . . . . . . . : Адаптер Broadcom NetXtreme для сети Ethernet, 1 Гбит/с
Физический адрес. . . . . . . . . : 00-12-3F-FF-0B-AB
DHCP включен. . . . . . . . . . . : Нет
Автонастройка включена. . . . . . : Да
IPv4-адрес. . . . . . . . . . . . : 192.168.1.11(Основной)
Маска подсети . . . . . . . . . . : 255.255.255.0
Основной шлюз. . . . . . . . . :
DNS-серверы. . . . . . . . . . . : 192.168.1.2
192.168.1.11
NetBios через TCP/IP. . . . . . . . : Включен
Ethernet adapter Kerio Virtual Network:
Состояние носителя. . . . . . . . : Носитель отключен
DNS-суффикс подключения . . . . . :
Описание. . . . . . . . . . . . . : Kerio Virtual Network Adapter
Физический адрес. . . . . . . . . : 44-45-53-54-4F-53
DHCP включен. . . . . . . . . . . : Да
Автонастройка включена. . . . . . : Да
Туннельный адаптер Подключение по локальной сети*:
Состояние носителя. . . . . . . . : Носитель отключен
DNS-суффикс подключения . . . . . : mkmgr.local
Описание. . . . . . . . . . . . . : isatap.mkmgr.local
Физический адрес. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP включен. . . . . . . . . . . : Нет
Автонастройка включена. . . . . . : Да
Туннельный адаптер Подключение по локальной сети* 9:
DNS-суффикс подключения . . . . . :
Описание. . . . . . . . . . . . . : 6TO4 Adapter
Физический адрес. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP включен. . . . . . . . . . . : Нет
Автонастройка включена. . . . . . : Да
IPv6-адрес. . . . . . . . . . . . : 2002:d42c:8463::d42c:8463(Основной)
Основной шлюз. . . . . . . . . : 2002:c058:6301::c058:6301
DNS-серверы. . . . . . . . . . . : 212.44.132.65
212.44.130.6
NetBios через TCP/IP. . . . . . . . : Отключен
Туннельный адаптер Подключение по локальной сети* 11:
Состояние носителя. . . . . . . . : Носитель отключен
DNS-суффикс подключения . . . . . :
Описание. . . . . . . . . . . . . : isatap.{0A2CE4F7-863E-4CCC-8CA2-5B93A49E68CD}
Физический адрес. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP включен. . . . . . . . . . . : Нет
Автонастройка включена. . . . . . : Да
Туннельный адаптер Подключение по локальной сети* 12:
Состояние носителя. . . . . . . . : Носитель отключен
DNS-суффикс подключения . . . . . :
Описание. . . . . . . . . . . . . : isatap.{28ECABD7-1114-43C8-8F47-D77419CB166D}
Физический адрес. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP включен. . . . . . . . . . . : Нет
Автонастройка включена. . . . . . : Да
Резервный КД
Настройка протокола IP для Windows
Имя компьютера . . . . . . . . . : pdc
Основной DNS-суффикс . . . . . . : mkmgr.local
Тип узла. . . . . . . . . . . . . : неизвестный
IP-маршрутизация включена . . . . : нет
WINS-прокси включен . . . . . . . : нет
Порядок просмотра суффиксов DNS . : mkmgr.local
Подключение по локальной сети — Ethernet адаптер:
DNS-суффикс этого подключения . . :
Описание . . . . . . . . . . . . : Embedded Broadcom NetXtreme 5721 PCI-E Gigabit NIC
Физический адрес. . . . . . . . . : 00-13-21-B4-D6-3B
DHCP включен. . . . . . . . . . . : нет
IP-адрес . . . . . . . . . . . . : 192.168.1.1
Маска подсети . . . . . . . . . . : 255.255.255.0
Основной шлюз . . . . . . . . . . : 192.168.1.11
DNS-серверы . . . . . . . . . . . : 192.168.1.2
192.168.1.1
БУДУ РАД ЛЮБОЙ ПОМОЩИ!!!
Hi,
We have one DC and ADC which is running on the same premises. Few days back the ADC got power failure and after that long it thrown an error of some services are not started. We checked the event viewer to find out the service failed but not
found the same. In Services all the services are in started mode. Restarted server serval time. Still the replication not happening with DC. If any one can help me out to find out the real issue will very helpful.
Pasting Below dciag and showrepl results ,
repadmin running command /showrepl against server localhost
Default-First-Site-NameBACKUPDC
DC Options: (none)
Site Options: (none)
DC object GUID: bcbf105f-e755-4c24-b846-01d447834480
DC invocationID: da4dec2a-3c22-4b5f-8f36-586ee3969ea2
==== INBOUND NEIGHBORS ======================================
DC=bannaridc,DC=com
Default-First-Site-NameDC via RPC
DC object GUID: 2a328743-72f5-48c7-b932-cbe8f957a580
Last attempt @ 2014-06-30 12:28:05 failed, result 5 (0x5):
Access is denied.
1479 consecutive failure(s).
Last success @ 2014-05-12 09:42:25.
CN=Configuration,DC=bannaridc,DC=com
Default-First-Site-NameDC via RPC
DC object GUID: 2a328743-72f5-48c7-b932-cbe8f957a580
Last attempt @ 2014-06-30 12:28:06 failed, result 5 (0x5):
Access is denied.
1182 consecutive failure(s).
Last success @ 2014-05-12 09:23:26.
CN=Schema,CN=Configuration,DC=bannaridc,DC=com
Default-First-Site-NameDC via RPC
DC object GUID: 2a328743-72f5-48c7-b932-cbe8f957a580
Last attempt @ 2014-06-30 12:28:06 failed, result 5 (0x5):
Access is denied.
1182 consecutive failure(s).
Last success @ 2014-05-12 09:23:26.
DC=DomainDnsZones,DC=bannaridc,DC=com
Default-First-Site-NameDC via RPC
DC object GUID: 2a328743-72f5-48c7-b932-cbe8f957a580
Last attempt @ 2014-06-30 12:28:05 failed, result 1256 (0x4e8):
The remote system is not available. For information about network troubleshooting, see Windows Help.
1182 consecutive failure(s).
Last success @ 2014-05-12 09:33:40.
DC=ForestDnsZones,DC=bannaridc,DC=com
Default-First-Site-NameDC via RPC
DC object GUID: 2a328743-72f5-48c7-b932-cbe8f957a580
Last attempt @ 2014-06-30 12:28:05 failed, result 1256 (0x4e8):
The remote system is not available. For information about network troubleshooting, see Windows Help.
1182 consecutive failure(s).
Last success @ 2014-05-12 09:23:27.
Source: Default-First-Site-NameDC
******* 1479 CONSECUTIVE FAILURES since 2014-05-12 09:42:25
Last error: 1256 (0x4e8):
The remote system is not available. For information about network troubleshooting, see Windows Help.
Replication Summary Start Time: 2014-06-30 12:49:41
Beginning data collection for replication summary, this may take awhile:
…..
Source DC largest delta fails/total %% error
BACKUPDC 49d.03h:30m:38s 5 / 5 100 (2148074274) The target principal name is incorrect.
DC 49d.03h:26m:15s 5 / 5 100 (5) Access is denied.
Destination DC largest delta fails/total %% error
BACKUPDC 49d.03h:26m:16s 5 / 5 100 (5) Access is denied.
DC 49d.03h:30m:39s 5 / 5 100 (2148074274) The target principal name is incorrect.
Domain Controller Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-NameBACKUPDC
Starting test: Connectivity
……………………. BACKUPDC passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-NameBACKUPDC
Starting test: Replications
[Replications Check,BACKUPDC] A recent replication attempt failed:
From DC to BACKUPDC
Naming Context: DC=ForestDnsZones,DC=bannaridc,DC=com
The replication generated an error (1256):
The remote system is not available. For information about network troubleshooting, see Windows Help.
The failure occurred at 2014-06-30 11:28:05.
The last success occurred at 2014-05-12 09:23:27.
1181 failures have occurred since the last success.
REPLICATION LATENCY WARNING
ERROR: Expected notification link is missing.
Source DC
Replication of new changes along this path will be delayed.
This problem should self-correct on the next periodic sync.
[Replications Check,BACKUPDC] A recent replication attempt failed:
From DC to BACKUPDC
Naming Context: DC=DomainDnsZones,DC=bannaridc,DC=com
The replication generated an error (1256):
The remote system is not available. For information about network troubleshooting, see Windows Help.
The failure occurred at 2014-06-30 11:28:05.
The last success occurred at 2014-05-12 09:33:40.
1181 failures have occurred since the last success.
REPLICATION LATENCY WARNING
ERROR: Expected notification link is missing.
Source DC
Replication of new changes along this path will be delayed.
This problem should self-correct on the next periodic sync.
[Replications Check,BACKUPDC] A recent replication attempt failed:
From DC to BACKUPDC
Naming Context: CN=Schema,CN=Configuration,DC=bannaridc,DC=com
The replication generated an error (5):
Access is denied.
The failure occurred at 2014-06-30 11:28:05.
The last success occurred at 2014-05-12 09:23:26.
1181 failures have occurred since the last success.
[Replications Check,BACKUPDC] A recent replication attempt failed:
From DC to BACKUPDC
Naming Context: CN=Configuration,DC=bannaridc,DC=com
The replication generated an error (5):
Access is denied.
The failure occurred at 2014-06-30 11:28:05.
The last success occurred at 2014-05-12 09:23:26.
1181 failures have occurred since the last success.
REPLICATION LATENCY WARNING
ERROR: Expected notification link is missing.
Source DC
Replication of new changes along this path will be delayed.
This problem should self-correct on the next periodic sync.
[Replications Check,BACKUPDC] A recent replication attempt failed:
From DC to BACKUPDC
Naming Context: DC=bannaridc,DC=com
The replication generated an error (5):
Access is denied.
The failure occurred at 2014-06-30 11:28:05.
The last success occurred at 2014-05-12 09:42:25.
1477 failures have occurred since the last success.
REPLICATION LATENCY WARNING
ERROR: Expected notification link is missing.
Source DC
Replication of new changes along this path will be delayed.
This problem should self-correct on the next periodic sync.
REPLICATION-RECEIVED LATENCY WARNING
BACKUPDC: Current time is 2014-06-30 12:20:45.
DC=ForestDnsZones,DC=bannaridc,DC=com
Last replication recieved from DC at 2014-05-12 09:23:27.
DC=DomainDnsZones,DC=bannaridc,DC=com
Last replication recieved from DC at 2014-05-12 09:33:40.
CN=Schema,CN=Configuration,DC=bannaridc,DC=com
Last replication recieved from DC at 2014-05-12 09:23:26.
CN=Configuration,DC=bannaridc,DC=com
Last replication recieved from DC at 2014-05-12 09:23:26.
DC=bannaridc,DC=com
Last replication recieved from DC at 2014-05-12 09:42:25.
……………………. BACKUPDC passed test Replications
Starting test: NCSecDesc
……………………. BACKUPDC passed test NCSecDesc
Starting test: NetLogons
……………………. BACKUPDC passed test NetLogons
Starting test: Advertising
……………………. BACKUPDC passed test Advertising
Starting test: KnowsOfRoleHolders
……………………. BACKUPDC passed test KnowsOfRoleHolders
Starting test: RidManager
……………………. BACKUPDC passed test RidManager
Starting test: MachineAccount
……………………. BACKUPDC passed test MachineAccount
Starting test: Services
……………………. BACKUPDC passed test Services
Starting test: ObjectsReplicated
……………………. BACKUPDC passed test ObjectsReplicated
Starting test: frssysvol
……………………. BACKUPDC passed test frssysvol
Starting test: frsevent
……………………. BACKUPDC passed test frsevent
Starting test: kccevent
……………………. BACKUPDC passed test kccevent
Starting test: systemlog
……………………. BACKUPDC passed test systemlog
Starting test: VerifyReferences
……………………. BACKUPDC 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 : bannaridc
Starting test: CrossRefValidation
……………………. bannaridc passed test CrossRefValidation
Starting test: CheckSDRefDom
……………………. bannaridc passed test CheckSDRefDom
Running enterprise tests on : bannaridc.com
Starting test: Intersite
……………………. bannaridc.com passed test Intersite
Starting test: FsmoCheck
……………………. bannaridc.com passed test FsmoCheck
Domain Controller Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-NameDC
Starting test: Connectivity
……………………. DC passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-NameDC
DNS Tests are running and not hung. Please wait a few minutes…
Running partition tests on : ForestDnsZones
Running partition tests on : DomainDnsZones
Running partition tests on : Schema
Running partition tests on : Configuration
Running partition tests on : bannaridc
Running enterprise tests on : bannaridc.com
Starting test: DNS
……………………. bannaridc.com passed test DNS
Hi,
We have one DC and ADC which is running on the same premises. Few days back the ADC got power failure and after that long it thrown an error of some services are not started. We checked the event viewer to find out the service failed but not
found the same. In Services all the services are in started mode. Restarted server serval time. Still the replication not happening with DC. If any one can help me out to find out the real issue will very helpful.
Pasting Below dciag and showrepl results ,
repadmin running command /showrepl against server localhost
Default-First-Site-NameBACKUPDC
DC Options: (none)
Site Options: (none)
DC object GUID: bcbf105f-e755-4c24-b846-01d447834480
DC invocationID: da4dec2a-3c22-4b5f-8f36-586ee3969ea2
==== INBOUND NEIGHBORS ======================================
DC=bannaridc,DC=com
Default-First-Site-NameDC via RPC
DC object GUID: 2a328743-72f5-48c7-b932-cbe8f957a580
Last attempt @ 2014-06-30 12:28:05 failed, result 5 (0x5):
Access is denied.
1479 consecutive failure(s).
Last success @ 2014-05-12 09:42:25.
CN=Configuration,DC=bannaridc,DC=com
Default-First-Site-NameDC via RPC
DC object GUID: 2a328743-72f5-48c7-b932-cbe8f957a580
Last attempt @ 2014-06-30 12:28:06 failed, result 5 (0x5):
Access is denied.
1182 consecutive failure(s).
Last success @ 2014-05-12 09:23:26.
CN=Schema,CN=Configuration,DC=bannaridc,DC=com
Default-First-Site-NameDC via RPC
DC object GUID: 2a328743-72f5-48c7-b932-cbe8f957a580
Last attempt @ 2014-06-30 12:28:06 failed, result 5 (0x5):
Access is denied.
1182 consecutive failure(s).
Last success @ 2014-05-12 09:23:26.
DC=DomainDnsZones,DC=bannaridc,DC=com
Default-First-Site-NameDC via RPC
DC object GUID: 2a328743-72f5-48c7-b932-cbe8f957a580
Last attempt @ 2014-06-30 12:28:05 failed, result 1256 (0x4e8):
The remote system is not available. For information about network troubleshooting, see Windows Help.
1182 consecutive failure(s).
Last success @ 2014-05-12 09:33:40.
DC=ForestDnsZones,DC=bannaridc,DC=com
Default-First-Site-NameDC via RPC
DC object GUID: 2a328743-72f5-48c7-b932-cbe8f957a580
Last attempt @ 2014-06-30 12:28:05 failed, result 1256 (0x4e8):
The remote system is not available. For information about network troubleshooting, see Windows Help.
1182 consecutive failure(s).
Last success @ 2014-05-12 09:23:27.
Source: Default-First-Site-NameDC
******* 1479 CONSECUTIVE FAILURES since 2014-05-12 09:42:25
Last error: 1256 (0x4e8):
The remote system is not available. For information about network troubleshooting, see Windows Help.
Replication Summary Start Time: 2014-06-30 12:49:41
Beginning data collection for replication summary, this may take awhile:
…..
Source DC largest delta fails/total %% error
BACKUPDC 49d.03h:30m:38s 5 / 5 100 (2148074274) The target principal name is incorrect.
DC 49d.03h:26m:15s 5 / 5 100 (5) Access is denied.
Destination DC largest delta fails/total %% error
BACKUPDC 49d.03h:26m:16s 5 / 5 100 (5) Access is denied.
DC 49d.03h:30m:39s 5 / 5 100 (2148074274) The target principal name is incorrect.
Domain Controller Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-NameBACKUPDC
Starting test: Connectivity
……………………. BACKUPDC passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-NameBACKUPDC
Starting test: Replications
[Replications Check,BACKUPDC] A recent replication attempt failed:
From DC to BACKUPDC
Naming Context: DC=ForestDnsZones,DC=bannaridc,DC=com
The replication generated an error (1256):
The remote system is not available. For information about network troubleshooting, see Windows Help.
The failure occurred at 2014-06-30 11:28:05.
The last success occurred at 2014-05-12 09:23:27.
1181 failures have occurred since the last success.
REPLICATION LATENCY WARNING
ERROR: Expected notification link is missing.
Source DC
Replication of new changes along this path will be delayed.
This problem should self-correct on the next periodic sync.
[Replications Check,BACKUPDC] A recent replication attempt failed:
From DC to BACKUPDC
Naming Context: DC=DomainDnsZones,DC=bannaridc,DC=com
The replication generated an error (1256):
The remote system is not available. For information about network troubleshooting, see Windows Help.
The failure occurred at 2014-06-30 11:28:05.
The last success occurred at 2014-05-12 09:33:40.
1181 failures have occurred since the last success.
REPLICATION LATENCY WARNING
ERROR: Expected notification link is missing.
Source DC
Replication of new changes along this path will be delayed.
This problem should self-correct on the next periodic sync.
[Replications Check,BACKUPDC] A recent replication attempt failed:
From DC to BACKUPDC
Naming Context: CN=Schema,CN=Configuration,DC=bannaridc,DC=com
The replication generated an error (5):
Access is denied.
The failure occurred at 2014-06-30 11:28:05.
The last success occurred at 2014-05-12 09:23:26.
1181 failures have occurred since the last success.
[Replications Check,BACKUPDC] A recent replication attempt failed:
From DC to BACKUPDC
Naming Context: CN=Configuration,DC=bannaridc,DC=com
The replication generated an error (5):
Access is denied.
The failure occurred at 2014-06-30 11:28:05.
The last success occurred at 2014-05-12 09:23:26.
1181 failures have occurred since the last success.
REPLICATION LATENCY WARNING
ERROR: Expected notification link is missing.
Source DC
Replication of new changes along this path will be delayed.
This problem should self-correct on the next periodic sync.
[Replications Check,BACKUPDC] A recent replication attempt failed:
From DC to BACKUPDC
Naming Context: DC=bannaridc,DC=com
The replication generated an error (5):
Access is denied.
The failure occurred at 2014-06-30 11:28:05.
The last success occurred at 2014-05-12 09:42:25.
1477 failures have occurred since the last success.
REPLICATION LATENCY WARNING
ERROR: Expected notification link is missing.
Source DC
Replication of new changes along this path will be delayed.
This problem should self-correct on the next periodic sync.
REPLICATION-RECEIVED LATENCY WARNING
BACKUPDC: Current time is 2014-06-30 12:20:45.
DC=ForestDnsZones,DC=bannaridc,DC=com
Last replication recieved from DC at 2014-05-12 09:23:27.
DC=DomainDnsZones,DC=bannaridc,DC=com
Last replication recieved from DC at 2014-05-12 09:33:40.
CN=Schema,CN=Configuration,DC=bannaridc,DC=com
Last replication recieved from DC at 2014-05-12 09:23:26.
CN=Configuration,DC=bannaridc,DC=com
Last replication recieved from DC at 2014-05-12 09:23:26.
DC=bannaridc,DC=com
Last replication recieved from DC at 2014-05-12 09:42:25.
……………………. BACKUPDC passed test Replications
Starting test: NCSecDesc
……………………. BACKUPDC passed test NCSecDesc
Starting test: NetLogons
……………………. BACKUPDC passed test NetLogons
Starting test: Advertising
……………………. BACKUPDC passed test Advertising
Starting test: KnowsOfRoleHolders
……………………. BACKUPDC passed test KnowsOfRoleHolders
Starting test: RidManager
……………………. BACKUPDC passed test RidManager
Starting test: MachineAccount
……………………. BACKUPDC passed test MachineAccount
Starting test: Services
……………………. BACKUPDC passed test Services
Starting test: ObjectsReplicated
……………………. BACKUPDC passed test ObjectsReplicated
Starting test: frssysvol
……………………. BACKUPDC passed test frssysvol
Starting test: frsevent
……………………. BACKUPDC passed test frsevent
Starting test: kccevent
……………………. BACKUPDC passed test kccevent
Starting test: systemlog
……………………. BACKUPDC passed test systemlog
Starting test: VerifyReferences
……………………. BACKUPDC 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 : bannaridc
Starting test: CrossRefValidation
……………………. bannaridc passed test CrossRefValidation
Starting test: CheckSDRefDom
……………………. bannaridc passed test CheckSDRefDom
Running enterprise tests on : bannaridc.com
Starting test: Intersite
……………………. bannaridc.com passed test Intersite
Starting test: FsmoCheck
……………………. bannaridc.com passed test FsmoCheck
Domain Controller Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-NameDC
Starting test: Connectivity
……………………. DC passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-NameDC
DNS Tests are running and not hung. Please wait a few minutes…
Running partition tests on : ForestDnsZones
Running partition tests on : DomainDnsZones
Running partition tests on : Schema
Running partition tests on : Configuration
Running partition tests on : bannaridc
Running enterprise tests on : bannaridc.com
Starting test: DNS
……………………. bannaridc.com passed test DNS
Добрый день! Уважаемые читатели и гости одного из крупнейших IT блогов по системному администрированию. В прошлый раз мы с вами устанавливали Windows 11 в домен Active Directory. Сегодня я хочу поговорить так же об активном каталоге и показать, как устраняется ошибка репликации, при которой в глобальном каталоге видятся удаленные объекты, которых не должно быть, при попытке посмотреть свойства данного объекта «Не удается отобразить объект Active Directory». Давайте смотреть в чем дело.
📛Описание ошибки The remote system is not available
Произошла аварийная ситуация и некоторая часть контроллеров домена вывалилась с синими экраном 0xc00002e2. В таких случаях такие контроллеры просто удаляют, даже если они и не доступны по сети. Там утилита ntdsutil делает все по красоте и должна вычистить все метаданные. Подождав немного я решил проверить репликацию между контроллерами домена, напоминаю сделать это можно через команду:
Но утилита показала, что удаленные контроллеры домена были в схеме репликации и не доступны, по статусу они имели ошибки:
- (2148074274) The target principal name is incorrect
- (1256) The remote system is not available. For information about network troubleshooting, see Windows Help.
Ошибку «(2148074274) The target principal name is incorrect» мы успешно устраняли ранее, но там нужен, чтобы контроллер домена был доступен, тут он был в ауте и его нельзя было вернуть, второй контроллер так же был в ауте.
Если вы запустите ADUC, и попытаетесь поискать имена сбойных контроллеров домена, то вы с большой вероятностью их обнаружите. У них будет описание «Контроллер домена доступный для записи (Writable Domane Controller)»
Если открыть свойства самого объекта, то вы увидите:
Не удалось отобразить объект служб Active Directory. не удается найти объект доменных служб Active Directory. Возможно он удален другим пользователем или контроллер домена Active Directory временно недоступен (Failed to map the Active Directory object. cannot find the Active Directory Domain Services object. It may have been deleted by another user or the Active Directory domain controller is temporarily unavailable)
Удалить он отсюда не дает данный объект «Windows cannot delete object because Directory object not found»
⚙️Как устранять ошибку репликации
Первое, что вы должны сделать, это выполнить команду на работающем контроллере домена:
С высокой долей вероятности вы увидите, где еще остались хвосты со старыми удаленными контроллерами домена.
SyncAll reported the following errors:
Error contacting server CN=NTDS Settings,CN=DC01,CN=Servers,CN=ISI,CN=Sites, CN=Configuration,DC=Pyatilistnik,DC=ORG (network error): 1722 (0x6ba):
The RPC server is unavailable.
Error contacting server CN=NTDS Settings,CN=IVAC,CN=Servers, CN=CO-IVA,CN=Sites,CN=Configuration,DC=Pyatilistnik,DC=ORG (network error): 1722 (0x6ba):
The RPC server is unavailable.
Error contacting server CN=NTDS Settings,CN=TVCO, CN=Servers,CN=CO-TV,CN=Sites,CN=Configuration,DC=Pyatilistnik,DC=ORG (network error): 1722 (0x6ba):
The RPC server is unavailable.
Syncing partition: DC=main,DC=Pyatilistnik,DC=ORG
CALLBACK MESSAGE: Error contacting server CN=NTDS Settings, CN=IVAC,CN=Servers,CN=CO-IVA,CN=Sites,CN=Configuration,DC=Pyatilistnik,DC=ORG (network error): 1722 (0x6ba):
The RPC server is unavailable.
CALLBACK MESSAGE: Error contacting server CN=NTDS Settings,CN=TVCO,CN=Servers,CN=CO-TV,CN=Sites, CN=Configuration,DC=Pyatilistnik,DC=ORG (network error): 1722 (0x6ba):
The RPC server is unavailable.
Вся загвоздка в том, что вам нужно в разделе «Configuration» удалить старую информацию.
Берем утилиту ADSIEdit и подключаемся к разделу конфигурации, после чего идем по тем путям, что указаны в ошибках.
Находим нужные записи в. моем случае это в сайтах AD.
И удаляем их всех.
После того, как вы все почистили, еще можно проверить оставшиеся записи в DNS, в основных зонах _msdcs. После всех манипуляций в ADUC выполните поиск удаленных компьютеров, у меня ничего не нашлось.
Запустим реплику:
Ошибок не стало и все реплики успешно прошли.
На этом все, мы с вами успешно удалили остатки мертвых контроллеров домена .устранили ошибки репликации «(1256) The remote system is not available. For information about network troubleshooting, see Windows Help». С вами был Иван Сёмин, автор и создатель IT портала Pyatilistnik.org.
| title | description | ms.date | author | ms.author | manager | audience | ms.topic | ms.prod | localization_priority | ms.reviewer | ms.custom | ms.technology |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Active Directory replication error 1256 |
Describes how to Active Directory replication error 1256. |
10/15/2020 |
Deland-Han |
delhan |
dcscontentpm |
itpro |
troubleshooting |
windows-server |
medium |
kaushika, justintu |
sap:active-directory-replication, csstroubleshoot |
windows-server-active-directory |
Active Directory replication error 1256: The remote system is not available
This article describes the symptoms, cause, and resolution steps for cases when Active Directory replication fails with error 1256: The remote system is not available.
Applies to: Windows Server 2012 R2
Original KB number: 2200187
Symptoms
-
The DCDIAG reports that the Active Directory Replications test has failed with error 1256: The remote system is not available.
Starting test: Replications
[Replications Check, <Destination DC>] A recent replication attempt failed:
From <source DC> to <destination DC>
Naming Context: <directory partition DN path>
The replication generated an error (1256):
The remote system is not available. For information about network troubleshooting, see Windows Help.
The failure occurred at <date> <time>
The last success occurred at <date> <time> -
REPADMIN.EXE reports that a replication attempt has failed with status 1256.
REPADMIN commands that commonly cite the 1256 status include but are not limited to:REPADMIN /REPLSUMREPADMIN /SHOWREPSREPADMIN /SHOWREPLREPADMIN /FAILCACHE
Sample output from
REPADMIN /SHOWREPSdepicting inbound replication from LonEMEADC to LonContosoDC failing with The remote system is not available error is shown below:Repadmin: running command /showrepl against full DC localhost
LondonLONCONTOSODC
DSA Options: IS_GC
Site Options: (none)
DSA object GUID: a29bbfda-8425-4cb9-9c66-8e07d505a5c6
DSA invocationID: d58a6322-6a28-4708-82d3-53b7dcc13c1a==== INBOUND NEIGHBORS ======================================
<snip>
DC=ForestDnsZones,DC=Contoso,DC=com
LondonLONEMEADC via RPC
DSA object GUID: cd691606-63d1-4cc8-b77a-055674ba569d
Last attempt @ 2010-06-10 17:35:46 failed, result 1256 (0x4e8):
The remote system is not available. For information about network troubleshooting, see Windows Help.
<#> consecutive failure(s).
Last success @ <date> <time>. -
NTDS KCC, NTDS Replication, or ActiveDirectory_DomainService events with the 1256 status are logged in the directory service event log.
Event Source Event ID Event String NTDS Replication ActiveDirectory_DomainService 1085 * Internal event: Active Directory Domain Services could not synchronize the following directory partition with the directory service at the following network address. NTDS KCC ActiveDirectory_DomainService 1308 The Knowledge Consistency Checker (KCC) has detected that successive attempts to replicate with the following domain controller has consistently failed. The Knowledge Consistency Checker (KCC) has detected that successive attempts to replicate with the following directory service has consistently failed. [!NOTE]
Event 1085 is only logged if the NTDS Diagnostics value 5 Replication Events has been set to a value of 1 or higher.
Cause
Replication status 1256 is logged for the following reason:
When the destination DC fails to bind to the source DC using RPC a win32 error code in the Repsfrom status for that partition — usually Schema or Configuration since these partitions are replicated at a higher priority. After an RPC bind failure has occurred, a cleanup routine will run to clear the destination DCs queue from that same source DC. This is done to avoid wasting time attempting to replicate with a DC that it can’t connect to. Since it hasn’t attempted a sync for the partitions that have been cleared from the queue, a status 1256 is logged. In a scenario where destination DC replicates Schema, Configuration, and several GC non-writable partitions from the source DC, the win32 error status for the Schema and Configuration partitions that caused the RPC bind failure is logged. The destination DC will then cancel the pending replication tasks for the remaining partitions and log win32 error 1256 for the status.
In summary: 1256 is logged as the replication status per partition as a result of the destination DC cancelling the sync request from the source DC due to a connectivity failure previously encountered.
Resolution
The win32 error 1256 should not be the focus of troubleshooting efforts, instead find the replication status that led to the RPC bind failure and then follow the corresponding Troubleshooting Active Directory operations that fail with error… article.
Diagnose Active Directory replication failures.
In order to determine the actual win32 error to troubleshoot, use one of the following methods:
-
View
repadmin /showrepsor/showreploutput on the destination DC- Identify Source DC in the output and list all win32 status messages per partition
- The win32 status that is listed that is not a 1256 should be the focus of troubleshooting efforts
-
Use
repadmin /showrepl * /csvoutput:- Filter column K, Last Failure Status: Deselect 0 and (Blanks)
- Filter column C, Destination DSA: Deselect (Select All) and select just the DC where the 1256 status is logged.
- If 1256 is logged on more than one Source DC, Filter column F, Source DSA: Deselect (Select All) and Select just one DC to narrow the focus.
- Column K, Last Failure Status will list the 1256’s along with the real win32 error that led to the RPC bind failure.
In the following example, win32 error 1722 is logged for the Configuration and Schema partitions and should be the focus of troubleshooting.
B C D E F H I J K Destination DSA Site Destination DSA Naming Context Source DSA Site Source DSA Number of Failures Last Failure Time Last Success Time Last Failure Status London LONCONTOSODC CN=Configuration,DC=Contoso,DC=com London LONEMEADC 11 6/10/2010 17:35 6/10/2010 14:50 1722 London LONCONTOSODC CN=Schema,CN=Configuration, DC=Contoso,DC=com London LONEMEADC 11 6/10/2010 17:36 6/10/2010 14:50 1722 London LONCONTOSODC DC=ForestDnsZones,DC=Contoso,DC=com London LONEMEADC 11 6/10/2010 17:35 6/10/2010 14:50 1256 London LONCONTOSODC DC=corp,DC=Contoso,DC=com London LONEMEADC 11 6/10/2010 17:35 6/10/2010 14:50 1256 London LONCONTOSODC DC=EMEA,DC=Contoso,DC=com London LONEMEADC 11 6/10/2010 17:35 6/10/2010 14:54 1256 London LONCONTOSODC DC=apac,DC=Contoso,DC=com London LONEMEADC 11 6/10/2010 17:35 6/10/2010 14:50 1256 -
Initiate a manual replication sync between source and destination DCs using repadmin.
Repadmin /replicate DestinationDC SourceDC <DN of partition reporting status 1256>(This will require /readonly switch for GC partition or /selsecrets switch if destination is an RODC)repadmin /replicate loncontosodc lonemeadc.emea.contoso.com dc=forestdnszones,dc=contoso,dc=comDsReplicaSync() failed with status 1722 (0x6ba):
The RPC server is unavailable.
Take note that after manually initiating replication for the partition that the status has changed from 1256 to 1722:
B C D E F H I J K Destination DSA Site Destination DSA Naming Context Source DSA Site Source DSA Number of Failures Last Failure Time Last Success Time Last Failure Status London LONCONTOSODC CN=Configuration,DC=Contoso, DC=com London LONEMEADC 11 6/10/2010 17:35 6/10/2010 14:50 1722 London LONCONTOSODC CN=Schema,CN=Configuration, DC=Contoso,DC=com London LONEMEADC 11 6/10/2010 17:36 6/10/2010 14:50 1722 London LONCONTOSODC DC=ForestDnsZones, DC=Contoso,DC=com London LONEMEADC 12 6/10/2010 17:46 6/10/2010 14:50 1722 London LONCONTOSODC DC=corp,DC=Contoso,DC=com London LONEMEADC 11 6/10/2010 17:35 6/10/2010 14:50 1256 London LONCONTOSODC DC=EMEA,DC=Contoso,DC=com London LONEMEADC 11 6/10/2010 17:35 6/10/2010 14:54 1256 London LONCONTOSODC DC=apac,DC=Contoso,DC=com London LONEMEADC 11 6/10/2010 17:35 6/10/2010 14:50 1256
More information
The following articles contain the troubleshooting procedures for errors typically logged with win32 error 1256:
| Win32 error | Article |
|---|---|
| -2146893022 | Active Directory replication error -2146893022: The target principal name is incorrect |
| 5 | Active Directory replication error 5 — Access is denied |
| 1722 | Active Directory replication error 1722: The RPC server is unavailable |
| 1727 | Troubleshoot domain controller replication error 1727-The remote procedure call failed and did not execute |
| 1753 | Active Directory Replication Error 1753: There are no more endpoints available from the endpoint mapper |
| 1908 | Troubleshooting Active Directory operations that fail with error 1908: Could not find the domain controller for this domain |
| 8524 | Active Directory Replication Error 8524: The DSA operation is unable to proceed because of a DNS lookup failure |
| 8453 | Active Directory replication error 8453: Replication access was denied |
| title | description | ms.date | author | ms.author | manager | audience | ms.topic | ms.prod | localization_priority | ms.reviewer | ms.custom | ms.technology |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Active Directory replication error 1256 |
Describes how to Active Directory replication error 1256. |
10/15/2020 |
Deland-Han |
delhan |
dcscontentpm |
itpro |
troubleshooting |
windows-server |
medium |
kaushika, justintu |
sap:active-directory-replication, csstroubleshoot |
windows-server-active-directory |
Active Directory replication error 1256: The remote system is not available
This article describes the symptoms, cause, and resolution steps for cases when Active Directory replication fails with error 1256: The remote system is not available.
Applies to: Windows Server 2012 R2
Original KB number: 2200187
Symptoms
-
The DCDIAG reports that the Active Directory Replications test has failed with error 1256: The remote system is not available.
Starting test: Replications
[Replications Check, <Destination DC>] A recent replication attempt failed:
From <source DC> to <destination DC>
Naming Context: <directory partition DN path>
The replication generated an error (1256):
The remote system is not available. For information about network troubleshooting, see Windows Help.
The failure occurred at <date> <time>
The last success occurred at <date> <time> -
REPADMIN.EXE reports that a replication attempt has failed with status 1256.
REPADMIN commands that commonly cite the 1256 status include but are not limited to:REPADMIN /REPLSUMREPADMIN /SHOWREPSREPADMIN /SHOWREPLREPADMIN /FAILCACHE
Sample output from
REPADMIN /SHOWREPSdepicting inbound replication from LonEMEADC to LonContosoDC failing with The remote system is not available error is shown below:Repadmin: running command /showrepl against full DC localhost
LondonLONCONTOSODC
DSA Options: IS_GC
Site Options: (none)
DSA object GUID: a29bbfda-8425-4cb9-9c66-8e07d505a5c6
DSA invocationID: d58a6322-6a28-4708-82d3-53b7dcc13c1a==== INBOUND NEIGHBORS ======================================
<snip>
DC=ForestDnsZones,DC=Contoso,DC=com
LondonLONEMEADC via RPC
DSA object GUID: cd691606-63d1-4cc8-b77a-055674ba569d
Last attempt @ 2010-06-10 17:35:46 failed, result 1256 (0x4e8):
The remote system is not available. For information about network troubleshooting, see Windows Help.
<#> consecutive failure(s).
Last success @ <date> <time>. -
NTDS KCC, NTDS Replication, or ActiveDirectory_DomainService events with the 1256 status are logged in the directory service event log.
Event Source Event ID Event String NTDS Replication ActiveDirectory_DomainService 1085 * Internal event: Active Directory Domain Services could not synchronize the following directory partition with the directory service at the following network address. NTDS KCC ActiveDirectory_DomainService 1308 The Knowledge Consistency Checker (KCC) has detected that successive attempts to replicate with the following domain controller has consistently failed. The Knowledge Consistency Checker (KCC) has detected that successive attempts to replicate with the following directory service has consistently failed. [!NOTE]
Event 1085 is only logged if the NTDS Diagnostics value 5 Replication Events has been set to a value of 1 or higher.
Cause
Replication status 1256 is logged for the following reason:
When the destination DC fails to bind to the source DC using RPC a win32 error code in the Repsfrom status for that partition — usually Schema or Configuration since these partitions are replicated at a higher priority. After an RPC bind failure has occurred, a cleanup routine will run to clear the destination DCs queue from that same source DC. This is done to avoid wasting time attempting to replicate with a DC that it can’t connect to. Since it hasn’t attempted a sync for the partitions that have been cleared from the queue, a status 1256 is logged. In a scenario where destination DC replicates Schema, Configuration, and several GC non-writable partitions from the source DC, the win32 error status for the Schema and Configuration partitions that caused the RPC bind failure is logged. The destination DC will then cancel the pending replication tasks for the remaining partitions and log win32 error 1256 for the status.
In summary: 1256 is logged as the replication status per partition as a result of the destination DC cancelling the sync request from the source DC due to a connectivity failure previously encountered.
Resolution
The win32 error 1256 should not be the focus of troubleshooting efforts, instead find the replication status that led to the RPC bind failure and then follow the corresponding Troubleshooting Active Directory operations that fail with error… article.
Diagnose Active Directory replication failures.
In order to determine the actual win32 error to troubleshoot, use one of the following methods:
-
View
repadmin /showrepsor/showreploutput on the destination DC- Identify Source DC in the output and list all win32 status messages per partition
- The win32 status that is listed that is not a 1256 should be the focus of troubleshooting efforts
-
Use
repadmin /showrepl * /csvoutput:- Filter column K, Last Failure Status: Deselect 0 and (Blanks)
- Filter column C, Destination DSA: Deselect (Select All) and select just the DC where the 1256 status is logged.
- If 1256 is logged on more than one Source DC, Filter column F, Source DSA: Deselect (Select All) and Select just one DC to narrow the focus.
- Column K, Last Failure Status will list the 1256’s along with the real win32 error that led to the RPC bind failure.
In the following example, win32 error 1722 is logged for the Configuration and Schema partitions and should be the focus of troubleshooting.
B C D E F H I J K Destination DSA Site Destination DSA Naming Context Source DSA Site Source DSA Number of Failures Last Failure Time Last Success Time Last Failure Status London LONCONTOSODC CN=Configuration,DC=Contoso,DC=com London LONEMEADC 11 6/10/2010 17:35 6/10/2010 14:50 1722 London LONCONTOSODC CN=Schema,CN=Configuration, DC=Contoso,DC=com London LONEMEADC 11 6/10/2010 17:36 6/10/2010 14:50 1722 London LONCONTOSODC DC=ForestDnsZones,DC=Contoso,DC=com London LONEMEADC 11 6/10/2010 17:35 6/10/2010 14:50 1256 London LONCONTOSODC DC=corp,DC=Contoso,DC=com London LONEMEADC 11 6/10/2010 17:35 6/10/2010 14:50 1256 London LONCONTOSODC DC=EMEA,DC=Contoso,DC=com London LONEMEADC 11 6/10/2010 17:35 6/10/2010 14:54 1256 London LONCONTOSODC DC=apac,DC=Contoso,DC=com London LONEMEADC 11 6/10/2010 17:35 6/10/2010 14:50 1256 -
Initiate a manual replication sync between source and destination DCs using repadmin.
Repadmin /replicate DestinationDC SourceDC <DN of partition reporting status 1256>(This will require /readonly switch for GC partition or /selsecrets switch if destination is an RODC)repadmin /replicate loncontosodc lonemeadc.emea.contoso.com dc=forestdnszones,dc=contoso,dc=comDsReplicaSync() failed with status 1722 (0x6ba):
The RPC server is unavailable.
Take note that after manually initiating replication for the partition that the status has changed from 1256 to 1722:
B C D E F H I J K Destination DSA Site Destination DSA Naming Context Source DSA Site Source DSA Number of Failures Last Failure Time Last Success Time Last Failure Status London LONCONTOSODC CN=Configuration,DC=Contoso, DC=com London LONEMEADC 11 6/10/2010 17:35 6/10/2010 14:50 1722 London LONCONTOSODC CN=Schema,CN=Configuration, DC=Contoso,DC=com London LONEMEADC 11 6/10/2010 17:36 6/10/2010 14:50 1722 London LONCONTOSODC DC=ForestDnsZones, DC=Contoso,DC=com London LONEMEADC 12 6/10/2010 17:46 6/10/2010 14:50 1722 London LONCONTOSODC DC=corp,DC=Contoso,DC=com London LONEMEADC 11 6/10/2010 17:35 6/10/2010 14:50 1256 London LONCONTOSODC DC=EMEA,DC=Contoso,DC=com London LONEMEADC 11 6/10/2010 17:35 6/10/2010 14:54 1256 London LONCONTOSODC DC=apac,DC=Contoso,DC=com London LONEMEADC 11 6/10/2010 17:35 6/10/2010 14:50 1256
More information
The following articles contain the troubleshooting procedures for errors typically logged with win32 error 1256:
| Win32 error | Article |
|---|---|
| -2146893022 | Active Directory replication error -2146893022: The target principal name is incorrect |
| 5 | Active Directory replication error 5 — Access is denied |
| 1722 | Active Directory replication error 1722: The RPC server is unavailable |
| 1727 | Troubleshoot domain controller replication error 1727-The remote procedure call failed and did not execute |
| 1753 | Active Directory Replication Error 1753: There are no more endpoints available from the endpoint mapper |
| 1908 | Troubleshooting Active Directory operations that fail with error 1908: Could not find the domain controller for this domain |
| 8524 | Active Directory Replication Error 8524: The DSA operation is unable to proceed because of a DNS lookup failure |
| 8453 | Active Directory replication error 8453: Replication access was denied |