Дочерний домен. Ошибки репликации
Модератор: Модераторы
Сообщений: 10
• Страница 1 из 1
Все на Win2003. Ситуация такая. Есть главный домен леса adm.local с контроллером kodeks.
Завел дочерний домен ce.adm.local с контроллером ceserver1.
Создал сайт Admsite и две подсети 192.168.1.0/24 и 192.168.3.0/24
Причем на контроллере ceserver1 появились откуда-то еще две подсети 192.168.1.0/24CNF:4f9806fe-d079-4ea9-ab74-1aa05eceafee
и
192.168.3.0/24CNF:fcf6d51c-608e-4b31-8187-c2a6f36de181
которые не могу удалить.
После всех настроек netdiag на обоих контроллерах проходит без ошибок. dcdiag на ceserver1 с ошибками:
Domain Controller Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial required tests
Testing server: AdmSite\CESERVER1
Starting test: Connectivity
......................... CESERVER1 passed test Connectivity
Doing primary tests
Testing server: AdmSite\CESERVER1
Starting test: Replications
[Replications Check,CESERVER1] A recent replication attempt failed:
From KODEKS to CESERVER1
Naming Context: DC=ForestDnsZones,DC=Adm,DC=local
The replication generated an error (1256):
Win32 Error 1256
The failure occurred at 2005-10-04 16:53:42.
The last success occurred at 2005-09-15 10:16:30.
1940 failures have occurred since the last success.
[KODEKS] DsBindWithSpnEx() failed with error 5,
Win32 Error 5.
[Replications Check,CESERVER1] A recent replication attempt failed:
From KODEKS to CESERVER1
Naming Context: CN=Schema,CN=Configuration,DC=Adm,DC=local
The replication generated an error (5):
Win32 Error 5
The failure occurred at 2005-10-04 16:53:42.
The last success occurred at 2005-09-15 10:16:30.
1851 failures have occurred since the last success.
[Replications Check,CESERVER1] A recent replication attempt failed:
From KODEKS to CESERVER1
Naming Context: CN=Configuration,DC=Adm,DC=local
The replication generated an error (5):
Win32 Error 5
The failure occurred at 2005-10-04 16:53:42.
The last success occurred at 2005-09-15 10:16:30.
1861 failures have occurred since the last success.
[Replications Check,CESERVER1] A recent replication attempt failed:
From KODEKS to CESERVER1
Naming Context: DC=Adm,DC=local
The replication generated an error (1256):
Win32 Error 1256
The failure occurred at 2005-10-04 16:53:42.
The last success occurred at 2005-09-15 10:16:30.
1868 failures have occurred since the last success.
REPLICATION-RECEIVED LATENCY WARNING
CESERVER1: Current time is 2005-10-04 16:57:29.
DC=ForestDnsZones,DC=Adm,DC=local
Last replication recieved from KODEKS at 2005-09-15 10:16:30.
CN=Schema,CN=Configuration,DC=Adm,DC=local
Last replication recieved from KODEKS at 2005-09-15 10:16:30.
CN=Configuration,DC=Adm,DC=local
Last replication recieved from KODEKS at 2005-09-15 10:16:30.
DC=Adm,DC=local
Last replication recieved from KODEKS at 2005-09-15 10:16:30.
......................... CESERVER1 passed test Replications
Starting test: NCSecDesc
......................... CESERVER1 passed test NCSecDesc
Starting test: NetLogons
......................... CESERVER1 passed test NetLogons
Starting test: Advertising
......................... CESERVER1 passed test Advertising
Starting test: KnowsOfRoleHolders
Warning: KODEKS is the Schema Owner, but is not responding to DS RPC Bi
nd.
[KODEKS] LDAP bind failed with error 1323,
Win32 Error 1323.
Warning: KODEKS is the Schema Owner, but is not responding to LDAP Bind
.
Warning: KODEKS is the Domain Owner, but is not responding to DS RPC Bi
nd.
Warning: KODEKS is the Domain Owner, but is not responding to LDAP Bind
.
......................... CESERVER1 failed test KnowsOfRoleHolders
Starting test: RidManager
......................... CESERVER1 passed test RidManager
Starting test: MachineAccount
......................... CESERVER1 passed test MachineAccount
Starting test: Services
......................... CESERVER1 passed test Services
Starting test: ObjectsReplicated
......................... CESERVER1 passed test ObjectsReplicated
Starting test: frssysvol
......................... CESERVER1 passed test frssysvol
Starting test: frsevent
......................... CESERVER1 passed test frsevent
Starting test: kccevent
......................... CESERVER1 passed test kccevent
Starting test: systemlog
......................... CESERVER1 passed test systemlog
Starting test: VerifyReferences
......................... CESERVER1 passed test VerifyReferences
Running partition tests on : ce
Starting test: CrossRefValidation
......................... ce passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... ce 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 : 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 : Adm.local
Starting test: Intersite
......................... Adm.local passed test Intersite
Starting test: FsmoCheck
......................... Adm.local passed test FsmoCheck
Помогите разобраться в чем дело.
Олег
Завел дочерний домен ce.adm.local с контроллером ceserver1.
Создал сайт Admsite и две подсети 192.168.1.0/24 и 192.168.3.0/24
Причем на контроллере ceserver1 появились откуда-то еще две подсети 192.168.1.0/24CNF:4f9806fe-d079-4ea9-ab74-1aa05eceafee
и
192.168.3.0/24CNF:fcf6d51c-608e-4b31-8187-c2a6f36de181
которые не могу удалить.
После всех настроек netdiag на обоих контроллерах проходит без ошибок. dcdiag на ceserver1 с ошибками:
Domain Controller Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial required tests
Testing server: AdmSite\CESERVER1
Starting test: Connectivity
......................... CESERVER1 passed test Connectivity
Doing primary tests
Testing server: AdmSite\CESERVER1
Starting test: Replications
[Replications Check,CESERVER1] A recent replication attempt failed:
From KODEKS to CESERVER1
Naming Context: DC=ForestDnsZones,DC=Adm,DC=local
The replication generated an error (1256):
Win32 Error 1256
The failure occurred at 2005-10-04 16:53:42.
The last success occurred at 2005-09-15 10:16:30.
1940 failures have occurred since the last success.
[KODEKS] DsBindWithSpnEx() failed with error 5,
Win32 Error 5.
[Replications Check,CESERVER1] A recent replication attempt failed:
From KODEKS to CESERVER1
Naming Context: CN=Schema,CN=Configuration,DC=Adm,DC=local
The replication generated an error (5):
Win32 Error 5
The failure occurred at 2005-10-04 16:53:42.
The last success occurred at 2005-09-15 10:16:30.
1851 failures have occurred since the last success.
[Replications Check,CESERVER1] A recent replication attempt failed:
From KODEKS to CESERVER1
Naming Context: CN=Configuration,DC=Adm,DC=local
The replication generated an error (5):
Win32 Error 5
The failure occurred at 2005-10-04 16:53:42.
The last success occurred at 2005-09-15 10:16:30.
1861 failures have occurred since the last success.
[Replications Check,CESERVER1] A recent replication attempt failed:
From KODEKS to CESERVER1
Naming Context: DC=Adm,DC=local
The replication generated an error (1256):
Win32 Error 1256
The failure occurred at 2005-10-04 16:53:42.
The last success occurred at 2005-09-15 10:16:30.
1868 failures have occurred since the last success.
REPLICATION-RECEIVED LATENCY WARNING
CESERVER1: Current time is 2005-10-04 16:57:29.
DC=ForestDnsZones,DC=Adm,DC=local
Last replication recieved from KODEKS at 2005-09-15 10:16:30.
CN=Schema,CN=Configuration,DC=Adm,DC=local
Last replication recieved from KODEKS at 2005-09-15 10:16:30.
CN=Configuration,DC=Adm,DC=local
Last replication recieved from KODEKS at 2005-09-15 10:16:30.
DC=Adm,DC=local
Last replication recieved from KODEKS at 2005-09-15 10:16:30.
......................... CESERVER1 passed test Replications
Starting test: NCSecDesc
......................... CESERVER1 passed test NCSecDesc
Starting test: NetLogons
......................... CESERVER1 passed test NetLogons
Starting test: Advertising
......................... CESERVER1 passed test Advertising
Starting test: KnowsOfRoleHolders
Warning: KODEKS is the Schema Owner, but is not responding to DS RPC Bi
nd.
[KODEKS] LDAP bind failed with error 1323,
Win32 Error 1323.
Warning: KODEKS is the Schema Owner, but is not responding to LDAP Bind
.
Warning: KODEKS is the Domain Owner, but is not responding to DS RPC Bi
nd.
Warning: KODEKS is the Domain Owner, but is not responding to LDAP Bind
.
......................... CESERVER1 failed test KnowsOfRoleHolders
Starting test: RidManager
......................... CESERVER1 passed test RidManager
Starting test: MachineAccount
......................... CESERVER1 passed test MachineAccount
Starting test: Services
......................... CESERVER1 passed test Services
Starting test: ObjectsReplicated
......................... CESERVER1 passed test ObjectsReplicated
Starting test: frssysvol
......................... CESERVER1 passed test frssysvol
Starting test: frsevent
......................... CESERVER1 passed test frsevent
Starting test: kccevent
......................... CESERVER1 passed test kccevent
Starting test: systemlog
......................... CESERVER1 passed test systemlog
Starting test: VerifyReferences
......................... CESERVER1 passed test VerifyReferences
Running partition tests on : ce
Starting test: CrossRefValidation
......................... ce passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... ce 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 : 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 : Adm.local
Starting test: Intersite
......................... Adm.local passed test Intersite
Starting test: FsmoCheck
......................... Adm.local passed test FsmoCheck
Помогите разобраться в чем дело.
Олег
- slz
- Активный пользователь
- Сообщения: 1229
- Зарегистрирован: 08 июл 2004, 06:17
- Откуда: Новосибирск
GeloSoft
С сетями ничего не понятно.
Какой контролеер в какой сети находится?
В каком сайте находится каждый контроллер?
Физически где расположены контроллеры и каким каналом связаны?
ечас можно сказать, только то, что ошибки репликации между DC валятся и что KODEKS является мастером схемы и именования доменов (так как он корневой DC), но не отвечает на запросы RPC и LDAP.
С сетями ничего не понятно.
Какой контролеер в какой сети находится?
В каком сайте находится каждый контроллер?
Физически где расположены контроллеры и каким каналом связаны?
ечас можно сказать, только то, что ошибки репликации между DC валятся и что KODEKS является мастером схемы и именования доменов (так как он корневой DC), но не отвечает на запросы RPC и LDAP.
- slz
- Активный пользователь
- Сообщения: 1229
- Зарегистрирован: 08 июл 2004, 06:17
- Откуда: Новосибирск
GeloSoft
Процедура поиска стандартная
на DC
ipconfig /all
netdiag
Ни какие сайты и подсети создавать вооще не надо было!
Аксесс листы на роутере
На одном из DC запусти любую оснастку, например ADUC и попробуй прицепиться к другому.
Процедура поиска стандартная
на DC
ipconfig /all
netdiag
Ни какие сайты и подсети создавать вооще не надо было!
Аксесс листы на роутере
На одном из DC запусти любую оснастку, например ADUC и попробуй прицепиться к другому.
Сообщений: 10
• Страница 1 из 1
Вернуться в Сетевые операционные системы
Кто сейчас на конференции
Сейчас этот форум просматривают: нет зарегистрированных пользователей и гости: 7