Serv 2003 c AD, DHCP, DNS

[White-Lion]

Всем добрый день.
Сразу хочу предупредить. Админ я недавно, до этого занимался программированием (Сильно не пинать и громко не смеяться :beta: :sorry: ).

Стоит Srv 2003 R2 x64 Standart. На нем подняты AD, DHCP, DNS, WINS.

Объясните пожалуйста почему в записи DHCP есть запись 10.83.10.16 - Work01.do****.
А при пинге данного айпи выдает laptop05.do****.
В DHCP нет записи laptop05.

Так же есть еще некоторые подобные несоответствия.
Может и не правильно но я думаю что в DNS настройка что то не так. Но куда смотреть? :oszone:

Подскажите пожалуйста как это исправить. :help:

[exo]

Доброго дня.
В DHCP нет записи laptop05. »
в DNS посмотрите. Эта служба занимается сопоставлением имён и IP адресов.
что в DNS настройка что то не так. Но куда смотреть? »
проверьте настройки динамического обновления в DHCP

[White-Lion]

проверьте настройки динамического обновления в DHCP »

В настойках DHCP Стоят настройки. Скриншот.

[astomper7]

White-Lion, анализируйте зону прямого просмотра на dns сервере.

[White-Lion]

анализируйте зону прямого просмотра на dns сервере. »
:sorry: С удовольствием проанализирую. Знать бы еще на что смотреть, и обращать внимание, что норма а что является плохим состоянием дел.

[exo]

Знать бы еще на что смотреть, и обращать внимание »
на записи с одинаковыми IP адресами. оставить только нужные.

[White-Lion]

на записи с одинаковыми IP адресами. »

Записи с одинаковыми IP есть.

оставить только нужные. »

Удалять вручную?

Можно ли понять почему старые записи не удаляются сами? Чтобы избежать этого в будущем.

оставить только нужные. »

Можно ли как нибудь обновить динамически?

[exo]

Удалять вручную? »
дя
Можно ли как нибудь обновить динамически? »
всё уже настроено, судя по скрину. хз почему старые записи не удаляются.

[astomper7]

White-Lion, переставьте радиобаттон на "Always dinamically update dns a and ptr records".

[White-Lion]

переставьте радиобаттон на "Always dinamically update dns a and ptr records". »

Уже сделал. (на свой страх и риск. :tomato2: ).
Жду почти час ничего не происходит.

Как запустить обновление данных?

[astomper7]

пуск - cmd - dnscmd /clearcache

[White-Lion]

dnscmd /clearcache »

Т.е. Для меня это будет команда:
dnscmd [МойСервер.домен] /clearcache

Правильно?

[astomper7]

Без [МойСервер.домен]

White-Lion, можете также вместо этого рестартануть сервис dns

[White-Lion]

можете также вместо этого рестартануть сервис dns »

Вчера в 15 часов запустил Clear Cache правой кнопкой мышки по серверу в dnsmgmt.

Ждал до вечера. В логах ничего не появилось.
Сегодня Решил сделать рестарт DNS. В логах стоп и старт прошли успешно.
Но я краем глаза заглянул в логи Directory Service. Стало страшно. :o

В общем лог dcdiag.


Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: RU-Ryazan\RYSDC1
Starting test: Connectivity
......................... RYSDC1 passed test Connectivity

Doing primary tests

Testing server: RU-Ryazan\RYSDC1
Starting test: Replications
[Replications Check,RYSDC1] A recent replication attempt failed:
From BRSEUDC01 to RYSDC1
Naming Context: DC=ForestDnsZones,DC=xxxxxx,DC=ads
The replication generated an error (8606):
Win32 Error 8606
The failure occurred at 2013-07-30 11:01:27.
The last success occurred at 2012-06-21 15:49:46.
9871 failures have occurred since the last success.
REPLICATION-RECEIVED LATENCY WARNING
RYSDC1: Current time is 2013-07-30 11:06:15.
DC=ForestDnsZones,DC=xxxxxx,DC=ads
Last replication recieved from ADSUSDC3 at 2013-05-14 13:19:51.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from WBSUSDC1 at 2013-04-19 09:52:06.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from RCSUSDC1 at 2013-04-20 05:52:14.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from MVSUSDC3 at 2013-04-19 14:52:07.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from COSUSDC1 at 2013-04-18 17:52:08.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from GLSDC01 at 2013-07-10 14:17:10.
Last replication recieved from SZSBRADC01 at 2012-03-05 05:53:53.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from SPSBRADC02 at 2013-05-13 15:55:11.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from BRSEUDC01 at 2013-06-19 17:48:14.
Last replication recieved from ERSDC2 at 2012-08-14 19:32:29.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from SPSBRADC03 at 2013-05-13 15:55:10.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from BXSBRADC01 at 2013-01-19 11:57:48.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from BWSUSDC1 at 2013-04-18 14:51:52.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from CHSUSDC1 at 2013-04-18 14:52:18.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from ESCSEUDC01 at 2013-05-09 06:45:29.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from CHSUSDC2 at 2013-05-16 06:49:37.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from GRSEUDC01 at 2013-05-15 14:10:49.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from EBVUSDC01 at 2013-04-18 14:51:52.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from EBVDC01 at 2013-06-16 07:44:51.
Last replication recieved from MVSFILE2 at 2013-04-19 14:47:30.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from BTSEUDC01 at 2013-07-07 18:27:47.
Last replication recieved from ERSDC3 at 2012-08-14 19:17:27.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from TBSBRADC01 at 2012-07-28 15:27:56.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from ANSUSDC at 2013-04-20 17:52:10.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from DOVDC01 at 2013-06-17 15:30:06.
Last replication recieved from NCFSUSDC2 at 2013-06-02 01:49:40.
Last replication recieved from ILFSUSDC1 at 2013-05-14 12:52:01.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from SPSBRADC01 at 2013-05-12 16:06:15.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from WOSUSDC1 at 2013-04-18 14:50:31.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from HOSUSDC at 2013-04-18 14:52:18.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from ERSEUDC01 at 2013-05-13 15:19:04.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from BUSUSDC at 2013-04-19 15:52:08.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
CN=Schema,CN=Configuration,DC=xxxxxx,DC=ads
Last replication recieved from GRSEUDC01 at 2013-07-29 18:52:10.
Last replication recieved from FOSEUDC01 at 2013-07-29 18:45:24.
CN=Configuration,DC=xxxxxx,DC=ads
Last replication recieved from GRSEUDC01 at 2013-07-29 18:52:03.
Last replication recieved from FOSEUDC01 at 2013-07-29 18:45:23.
DC=DomainDnsZones,DC=eu,DC=xxxxxx,DC=ads
Last replication recieved from GRSEUDC01 at 2013-07-29 18:52:19.
Last replication recieved from FOSEUDC01 at 2013-07-29 18:45:26.
DC=eu,DC=xxxxxx,DC=ads
Last replication recieved from GRSEUDC01 at 2013-07-29 18:52:12.
Last replication recieved from FOSEUDC01 at 2013-07-29 18:45:24.
......................... RYSDC1 passed test Replications
Starting test: NCSecDesc
......................... RYSDC1 passed test NCSecDesc
Starting test: NetLogons
......................... RYSDC1 passed test NetLogons
Starting test: Advertising
......................... RYSDC1 passed test Advertising
Starting test: KnowsOfRoleHolders
......................... RYSDC1 passed test KnowsOfRoleHolders
Starting test: RidManager
......................... RYSDC1 passed test RidManager
Starting test: MachineAccount
......................... RYSDC1 passed test MachineAccount
Starting test: Services
......................... RYSDC1 passed test Services
Starting test: ObjectsReplicated
......................... RYSDC1 passed test ObjectsReplicated
Starting test: frssysvol
......................... RYSDC1 passed test frssysvol
Starting test: frsevent
......................... RYSDC1 passed test frsevent
Starting test: kccevent
......................... RYSDC1 passed test kccevent
Starting test: systemlog
An Error Event occured. EventID: 0xC0000424
Time Generated: 07/30/2013 10:40:39
(Event String could not be retrieved)
An Error Event occured. EventID: 0xC0000424
Time Generated: 07/30/2013 10:42:08
(Event String could not be retrieved)
An Error Event occured. EventID: 0xC0000424
Time Generated: 07/30/2013 10:42:59
(Event String could not be retrieved)
An Error Event occured. EventID: 0xC0000424
Time Generated: 07/30/2013 10:43:04
(Event String could not be retrieved)
An Error Event occured. EventID: 0xC0000424
Time Generated: 07/30/2013 10:43:41
(Event String could not be retrieved)
An Error Event occured. EventID: 0xC0000424
Time Generated: 07/30/2013 10:43:46
(Event String could not be retrieved)
An Error Event occured. EventID: 0xC0000424
Time Generated: 07/30/2013 10:44:22
(Event String could not be retrieved)
......................... RYSDC1 failed test systemlog
Starting test: VerifyReferences
......................... RYSDC1 passed test VerifyReferences

Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom

Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom

Running partition tests on : eu
Starting test: CrossRefValidation
......................... eu passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... eu 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 enterprise tests on : xxxxxx.ads
Starting test: Intersite
Doing intersite inbound replication test on site RU-Ryazan:
*Warning: Remote bridgehead DE-Bruehl\BRSEUDC01 is not eligible as

a bridgehead due to too many failures. Replication may be

disrupted into the local site RU-Ryazan.
......................... xxxxxx.ads passed test Intersite
Starting test: FsmoCheck
......................... xxxxxx.ads passed test FsmoCheck



И лог repadmin /showreps

RU-Ryazan\RYSDC1

DC Options: IS_GC

Site Options: (none)

DC object GUID: 7e4b2d34-368c-4f8b-b8cd-c7f4d2a086bc

DC invocationID: 06a5fd35-5cd6-4021-8bb8-d0c80f2a4230



==== INBOUND NEIGHBORS ======================================



CN=Configuration,DC=xxxxxx,DC=ads

DE-Bruehl\BRSEUDC02 via RPC

DC object GUID: 60f2bf27-ff72-46c2-9f38-c153fee87729

Last attempt @ 2013-07-30 11:16:26 was successful.

DE-Bruehl\BRSDC01 via RPC

DC object GUID: 9c546f59-38f9-4b82-8c39-fcb602a4f823

Last attempt @ 2013-07-30 11:16:27 was successful.

DE-Bruehl\BRSEUDC01 via RPC

DC object GUID: 1ba8291c-ce77-46f8-ba1b-2a64a91d9e4a

Last attempt @ 2013-07-30 11:31:26 was successful.



CN=Schema,CN=Configuration,DC=xxxxxx,DC=ads

DE-Bruehl\BRSEUDC02 via RPC

DC object GUID: 60f2bf27-ff72-46c2-9f38-c153fee87729

Last attempt @ 2013-07-30 11:16:28 was successful.

DE-Bruehl\BRSDC01 via RPC

DC object GUID: 9c546f59-38f9-4b82-8c39-fcb602a4f823

Last attempt @ 2013-07-30 11:16:28 was successful.

DE-Bruehl\BRSEUDC01 via RPC

DC object GUID: 1ba8291c-ce77-46f8-ba1b-2a64a91d9e4a

Last attempt @ 2013-07-30 11:31:26 was successful.



DC=eu,DC=xxxxxx,DC=ads

DE-Bruehl\BRSEUDC02 via RPC

DC object GUID: 60f2bf27-ff72-46c2-9f38-c153fee87729

Last attempt @ 2013-07-30 11:16:28 was successful.

DE-Bruehl\BRSEUDC01 via RPC

DC object GUID: 1ba8291c-ce77-46f8-ba1b-2a64a91d9e4a

Last attempt @ 2013-07-30 11:31:26 was successful.



DC=ForestDnsZones,DC=xxxxxx,DC=ads

DE-Bruehl\BRSEUDC02 via RPC

DC object GUID: 60f2bf27-ff72-46c2-9f38-c153fee87729

Last attempt @ 2013-07-30 11:16:28 was successful.

DE-Bruehl\BRSDC01 via RPC

DC object GUID: 9c546f59-38f9-4b82-8c39-fcb602a4f823

Last attempt @ 2013-07-30 11:16:28 was successful.

DE-Bruehl\BRSEUDC01 via RPC

DC object GUID: 1ba8291c-ce77-46f8-ba1b-2a64a91d9e4a

Last attempt @ 2013-07-30 11:31:27 failed, result 8606 (0x219e):

Can't retrieve message string 8606 (0x219e), error 1815.

9873 consecutive failure(s).

Last success @ 2012-06-21 15:49:46.



DC=DomainDnsZones,DC=eu,DC=xxxxxx,DC=ads

DE-Bruehl\BRSEUDC02 via RPC

DC object GUID: 60f2bf27-ff72-46c2-9f38-c153fee87729

Last attempt @ 2013-07-30 11:16:29 was successful.

DE-Bruehl\BRSEUDC01 via RPC

DC object GUID: 1ba8291c-ce77-46f8-ba1b-2a64a91d9e4a

Last attempt @ 2013-07-30 11:31:28 was successful.



DC=xxxxxx,DC=ads

DE-Bruehl\BRSEUDC02 via RPC

DC object GUID: 60f2bf27-ff72-46c2-9f38-c153fee87729

Last attempt @ 2013-07-30 11:16:29 was successful.

DE-Bruehl\BRSDC01 via RPC

DC object GUID: 9c546f59-38f9-4b82-8c39-fcb602a4f823

Last attempt @ 2013-07-30 11:16:30 was successful.

DE-Bruehl\BRSEUDC01 via RPC

DC object GUID: 1ba8291c-ce77-46f8-ba1b-2a64a91d9e4a

Last attempt @ 2013-07-30 11:31:28 was successful.



DC=bra,DC=xxxxxx,DC=ads

DE-Bruehl\BRSEUDC02 via RPC

DC object GUID: 60f2bf27-ff72-46c2-9f38-c153fee87729

Last attempt @ 2013-07-30 11:16:30 was successful.

DE-Bruehl\BRSDC01 via RPC

DC object GUID: 9c546f59-38f9-4b82-8c39-fcb602a4f823

Last attempt @ 2013-07-30 11:16:30 was successful.

DE-Bruehl\BRSEUDC01 via RPC

DC object GUID: 1ba8291c-ce77-46f8-ba1b-2a64a91d9e4a

Last attempt @ 2013-07-30 11:31:28 was successful.



DC=us,DC=xxxxxx,DC=ads

DE-Bruehl\BRSEUDC02 via RPC

DC object GUID: 60f2bf27-ff72-46c2-9f38-c153fee87729

Last attempt @ 2013-07-30 11:16:30 was successful.

DE-Bruehl\BRSDC01 via RPC

DC object GUID: 9c546f59-38f9-4b82-8c39-fcb602a4f823

Last attempt @ 2013-07-30 11:16:30 was successful.

DE-Bruehl\BRSEUDC01 via RPC

DC object GUID: 1ba8291c-ce77-46f8-ba1b-2a64a91d9e4a

Last attempt @ 2013-07-30 11:31:28 was successful.



Source: DE-Bruehl\BRSEUDC01

******* 9872 CONSECUTIVE FAILURES since 2012-06-21 15:49:46

Last error: 8606 (0x219e):

Can't retrieve message string 8606 (0x219e), error 1815.



Анализирую такие логи впервые.
Как я понял у меня не проходит репликация AD.

Осталось выяснить почему......

хз почему старые записи не удаляются. »

Может ли из-за ошибок в репликах AD не обновляться в DNS старые записи?

[White-Lion]

Для решения проблеи реплик AD воспользовался ключами реестра:
Создал:
HKLM\System\CurrentControlSet\Services\NTDS\Parameters\
Allow Replication With Divergent and Corrupt Partner
1

Перезапустился..... Некоторые ошибки прошли.

Удалил ключ.

HKLM\System\CurrentControlSet\Services\NTDS\Parameters\
Strict Replication Consistency

Перезапустился. Ошибки пропали полностью.

Для верности подожду до завтра.
Отпишусь.
p.s. В dns в обратной моей зоне дублированые записи все еще есть. Посмотрим что будет после решения проблем репликаций.

[astomper7]

White-Lion, что с ошибками?

[White-Lion]

что с ошибками? »

После нескольких дней.
В логах вылезали ошибки. {все ошибки: Event.zip (http://forum.oszone.net/attachment.php?attachmentid=102595&d=1375797513)}.

При использовании команды repadmin /showvector /latency получил очень много данных. теперь не знаю что делать дальше.

пример 1го отчета для ошибки из текстовика { rForestDnsZone.txt (http://forum.oszone.net/attachment.php?attachmentid=102595&stc=1&d=1375797694)}

repadmin /showvector /latency DC=ForestDnsZones,DC=xxxxxx,DC=ads


получил { rForestDnsZone_Rep.zip (http://forum.oszone.net/attachment.php?attachmentid=102595&stc=1&d=1375797694)}.

Копать дальше пока некогда. загрузили другой работой.

Если кто подскажет буду очень признателен.

[White-Lion]

Перекопал кучу информации :lamer: .
В голове каша из информации.
Немного резюмирую всю инфу.
Заметил что в DNS записях обратной зоны моей подсети существуют двойные ссылки.
Начал копать.
Понял что у меня не реплицируется DC=ForestDnsZones,DC=xxxxxx,DC=ads (ФорумчанЕ правильно ли я понял?)
Вот показания dcdiag /a



Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: RU-Ryazan\RYSDC1
Starting test: Connectivity
......................... RYSDC1 passed test Connectivity

Doing primary tests

Testing server: RU-Ryazan\RYSDC1
Starting test: Replications
[Replications Check,RYSDC1] A recent replication attempt failed:
From BRSEUDC01 to RYSDC1
Naming Context: DC=ForestDnsZones,DC=xxxxxx,DC=ads
The replication generated an error (8606):
Win32 Error 8606
The failure occurred at 2013-08-14 12:22:22.
The last success occurred at 2013-08-13 11:07:15.
101 failures have occurred since the last success.
REPLICATION-RECEIVED LATENCY WARNING
RYSDC1: Current time is 2013-08-14 12:23:14.
DC=us,DC=xxxxxx,DC=ads
Last replication recieved from CHSUSDC1 at 2013-08-12 02:23:08.
DC=ForestDnsZones,DC=xxxxxx,DC=ads
Last replication recieved from ADSUSDC3 at 2013-05-14 13:19:51.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from WBSUSDC1 at 2013-04-19 09:52:06.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from RCSUSDC1 at 2013-04-20 05:52:14.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from MVSUSDC3 at 2013-04-19 14:52:07.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from COSUSDC1 at 2013-04-18 17:52:08.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from GLSDC01 at 2013-07-10 14:17:10.
Last replication recieved from STASEUDC01 at 2013-08-13 10:28:58.
Last replication recieved from SZSBRADC01 at 2012-03-05 05:53:53.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from SPSBRADC02 at 2013-05-13 15:55:11.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from CREVEUDC01 at 2013-08-13 10:54:53.
Last replication recieved from BRSEUDC01 at 2013-08-13 11:07:15.
Last replication recieved from ERSDC2 at 2013-06-21 20:50:06.
Last replication recieved from SPSBRADC03 at 2013-05-13 15:55:10.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from BXSBRADC01 at 2013-01-19 11:57:48.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from BWSUSDC1 at 2013-04-18 14:51:52.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from ESCSEUDC01 at 2013-08-13 10:44:09.
Last replication recieved from CHSUSDC2 at 2013-05-16 06:49:37.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from GRSEUDC01 at 2013-08-13 10:54:50.
Last replication recieved from STPSEUDC01 at 2013-08-13 10:44:09.
Last replication recieved from EBVUSDC01 at 2013-04-18 14:51:52.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from EBVDC01 at 2013-06-16 07:44:51.
Last replication recieved from MVSFILE2 at 2013-04-19 14:47:30.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from BTSEUDC01 at 2013-08-13 10:54:53.
Last replication recieved from ERSDC3 at 2013-06-21 20:47:17.
Last replication recieved from TBSBRADC01 at 2012-07-28 15:27:56.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from ANSUSDC at 2013-04-20 17:52:10.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from DOVDC01 at 2013-06-17 15:30:06.
Last replication recieved from NCFSUSDC2 at 2013-06-02 01:49:40.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from ILFSUSDC1 at 2013-05-14 12:52:01.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from SPSBRADC01 at 2013-05-12 16:06:15.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from WOSUSDC1 at 2013-04-18 14:50:31.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from HOSUSDC at 2013-04-18 14:52:18.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
Last replication recieved from ERSEUDC01 at 2013-08-13 10:54:53.
Last replication recieved from BUSUSDC at 2013-04-19 15:52:08.
WARNING: This latency is over the Tombstone Lifetime of 60 days!
CN=Schema,CN=Configuration,DC=xxxxxx,DC=ads
Last replication recieved from CHSUSDC1 at 2013-08-12 01:58:21.
CN=Configuration,DC=xxxxxx,DC=ads
Last replication recieved from CHSUSDC1 at 2013-08-12 01:58:17.
......................... RYSDC1 passed test Replications
Starting test: NCSecDesc
......................... RYSDC1 passed test NCSecDesc
Starting test: NetLogons
......................... RYSDC1 passed test NetLogons
Starting test: Advertising
......................... RYSDC1 passed test Advertising
Starting test: KnowsOfRoleHolders
......................... RYSDC1 passed test KnowsOfRoleHolders
Starting test: RidManager
......................... RYSDC1 passed test RidManager
Starting test: MachineAccount
......................... RYSDC1 passed test MachineAccount
Starting test: Services
......................... RYSDC1 passed test Services
Starting test: ObjectsReplicated
......................... RYSDC1 passed test ObjectsReplicated
Starting test: frssysvol
......................... RYSDC1 passed test frssysvol
Starting test: frsevent
......................... RYSDC1 passed test frsevent
Starting test: kccevent
......................... RYSDC1 passed test kccevent
Starting test: systemlog
......................... RYSDC1 passed test systemlog
Starting test: VerifyReferences
......................... RYSDC1 passed test VerifyReferences

Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom

Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom

Running partition tests on : eu
Starting test: CrossRefValidation
......................... eu passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... eu 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 enterprise tests on : xxxxxx.ads
Starting test: Intersite
Doing intersite inbound replication test on site RU-Ryazan:
*Warning: Remote bridgehead DE-Bruehl\BRSEUDC01 is not eligible as

a bridgehead due to too many failures. Replication may be

disrupted into the local site RU-Ryazan.
......................... xxxxxx.ads passed test Intersite
Starting test: FsmoCheck
......................... xxxxxx.ads passed test FsmoCheck




Текущая схема \>ntdsutil: role

\>ntdsutil
ntdsutil: role
fsmo maintenance: connections
server connections: connect to server rysdc1
Binding to rysdc1 ...
Connected to rysdc1 using credentials of locally logged on user.
server connections: quit
fsmo maintenance: select operation target
select operation target: list roles for connected server
Server "rysdc1" knows about 5 roles

Schema - CN=NTDS Settings,CN=BRSDC01,CN=Servers,CN=DE-Bruehl,CN=Sites,CN=Configuration,DC=xxxxxx,DC=ads
Domain - CN=NTDS Settings,CN=BRSDC01,CN=Servers,CN=DE-Bruehl,CN=Sites,CN=Configuration,DC=xxxxxx,DC=ads
PDC - CN=NTDS Settings,CN=BRSEUDC01,CN=Servers,CN=DE-Bruehl,CN=Sites,CN=Configuration,DC=xxxxxx,DC=ads
RID - CN=NTDS Settings,CN=BRSEUDC01,CN=Servers,CN=DE-Bruehl,CN=Sites,CN=Configuration,DC=xxxxxx,DC=ads
Infrastructure - CN=NTDS Settings,CN=BRSEUDC01,CN=Servers,CN=DE-Bruehl,CN=Sites,CN=Configuration,DC=xxxxxx,DC=ads

select operation target: quit
fsmo maintenance: quit
ntdsutil: quit
Disconnecting from rysdc1...



Вот показания repadmin /replsum



Replication Summary Start Time: 2013-08-14 12:26:04

Beginning data collection for replication summary, this may take awhile:
..................................................
.....


Destination DC largest delta fails/total %% error
ADSUSDC3 05m:20s 0 / 16 0
ANSUSDC 37m:05s 0 / 7 0
BHSEUDC01 55d.18h:55m:03s 1 / 22 4 (8606) Can't retrieve message string 8606 (0x219e), error 1815.
BRSBRADC01 >60 days 1 / 34 2 (8614) Can't retrieve message string 8614 (0x21a6), error 1815.
BRSDC01 55d.18h:42m:06s 11 / 144 7 (8606) Can't retrieve message string 8606 (0x219e), error 1815.
BRSDC02 55d.18h:42m:13s 1 / 20 5 (8606) Can't retrieve message string 8606 (0x219e), error 1815.
BRSEUDC01 >60 days 1 / 114 0 (8614) Can't retrieve message string 8614 (0x21a6), error 1815.
BRSEUDC02 41m:21s 4 / 120 3 (8606) Can't retrieve message string 8606 (0x219e), error 1815.
BRSUSDC01 >60 days 2 / 39 5 (8614) Can't retrieve message string 8614 (0x21a6), error 1815.
BTSEUDC01 02m:27s 3 / 22 13 (8614) Can't retrieve message string 8614 (0x21a6), error 1815.
BUSUSDC 28m:28s 0 / 7 0
BWSUSDC1 02d.10h:39m:12s 8 / 113 7 (1722) Can't retrieve message string 1722 (0x6ba), error 1815.
CHSUSDC2 >60 days 8 / 15 53 (1256) Can't retrieve message string 1256 (0x4e8), error 1815.
COSUSDC1 38m:26s 0 / 7 0
CREVEUDC01 05m:01s 3 / 46 6 (8606) Can't retrieve message string 8606 (0x219e), error 1815.
DOVDC01 34m:19s 0 / 14 0
DOVEUDC01 57d.21h:35m:03s 2 / 22 9 (8606) Can't retrieve message string 8606 (0x219e), error 1815.
EBVDC01 33m:40s 18 / 106 16 (8606) Can't retrieve message string 8606 (0x219e), error 1815.
EBVUSDC01 02d.10h:41m:20s 8 / 70 11 (1722) Can't retrieve message string 1722 (0x6ba), error 1815.
ERSDC2 >60 days 1 / 16 6 (8614) Can't retrieve message string 8614 (0x21a6), error 1815.
ERSDC3 03m:39s 2 / 36 5 (8614) Can't retrieve message string 8614 (0x21a6), error 1815.
ERSEUDC01 >60 days 3 / 24 12 (8614) Can't retrieve message string 8614 (0x21a6), error 1815.
ESCSEUDC01 12m:58s 0 / 8 0
FOSEUDC01 33d.21h:05m:07s 1 / 8 12 (8606) Can't retrieve message string 8606 (0x219e), error 1815.
GRSEUDC01 07m:06s 2 / 28 7 (8606) Can't retrieve message string 8606 (0x219e), error 1815.
HHSEUDC01 55d.18h:40m:30s 1 / 22 4 (8606) Can't retrieve message string 8606 (0x219e), error 1815.
HOSUSDC 35m:42s 0 / 7 0
ILFSUSDC1 33m:18s 0 / 7 0
LBSEUDC01 13m:59s 1 / 22 4 (8606) Can't retrieve message string 8606 (0x219e), error 1815.
MVSFILE2 30m:19s 0 / 5 0
MVSUSDC3 42m:48s 0 / 9 0
NCFSUSDC2 36m:07s 0 / 7 0
OOSEUDC01 55d.18h:49m:12s 1 / 22 4 (8606) Can't retrieve message string 8606 (0x219e), error 1815.
RCSUSDC1 35m:30s 0 / 7 0
ROSUSDC2 06m:58s 4 / 30 13 (8614) Can't retrieve message string 8614 (0x21a6), error 1815.
RYSDC1 01d.01h:20m:25s 1 / 22 4 (8606) Can't retrieve message string 8606 (0x219e), error 1815.
STASEUDC01 13m:07s 0 / 8 0
STPSEUDC01 02m:09s 0 / 8 0
WBSUSDC1 37m:33s 0 / 7 0
WOSUSDC1 46m:38s 0 / 7 0

Experienced the following operational errors trying to retrieve replication information:
58 - CHSUSDC1.us.xxxxxx.ads
58 - BXSBRADC01.bra.xxxxxx.ads
58 - SPSBRADC03.bra.xxxxxx.ads
58 - SZSBRADC01.bra.xxxxxx.ads
58 - MTSBRADC01.bra.xxxxxx.ads
58 - SPSBRADC02.bra.xxxxxx.ads
58 - SPSBRADC01.bra.xxxxxx.ads
58 - SPSDC01.xxxxxx.ads
58 - GESEUDC01.eu.xxxxxx.ads
58 - TBSBRADC01.bra.xxxxxx.ads
58 - JYSDC01.xxxxxx.ads
58 - GLSDC01.xxxxxx.ads



Сейчас в логах есть ошибки. 1988,1864.
И предупреждение 1862.

Я понял что из-за того что репликация долго проходила с ошибками у меня есть Устаревшие объекты.
Вычитал что это лечиться repadmin /removelingeringobjects

В правильном ли я иду направлении? :help:
Что необходимо учесть? и Что сделать?