LeonesIT
asked on
Event 1188 1232 NTDS Replication problems
Hello, I'm experiencing some problems concernign replication between my 3 Domain Controllers. 2 DC's are on the same Lan (named DC1005 and DC1006), one is on another location connected through a WAN 6Mbit line (named DCNOC001). A couple of times per week I'm experiencing replication problems between DCNOC001 and the DC1005 or DC1006. In the event viewer on the DCNOC001 there are the following event id's: 1188 and 1232.
From the DCNOC001 I cannot RDP to the DC1005.
I can ping DC1005 from the DCNOC001
I can do a nslookup on the DCNOC001 and DC1005 and DC1006, works fine
The only thing I can do to solve this is to reboot the DC1005.
I hope someone can give me some advise.
Thank you in advance.
DCDIAG on the DC1005 gets stuck on the replication test.
Dcdiag on the DCNOC001 tells me the following:
Domain Controller Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\DC NOC001
Starting test: Connectivity
......................... DCNOC001 passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\DC NOC001
Starting test: Replications
[Replications Check,DCNOC001] A recent replication attempt failed:
From DC1005 to DCNOC001
Naming Context: DC=ForestDnsZones,DC=ds-op m,DC=lan
The replication generated an error (1726):
The remote procedure call failed.
The failure occurred at 2007-12-03 08:06:17.
The last success occurred at 2007-12-01 12:45:12.
43 failures have occurred since the last success.
The replication RPC call executed for too long at the server and
was cancelled.
Check load and resouce usage on DC1005.
[Replications Check,DCNOC001] A recent replication attempt failed:
From DC1005 to DCNOC001
Naming Context: DC=DomainDnsZones,DC=ds-op m,DC=lan
The replication generated an error (1726):
The remote procedure call failed.
The failure occurred at 2007-12-03 08:03:13.
The last success occurred at 2007-12-01 12:45:12.
43 failures have occurred since the last success.
The replication RPC call executed for too long at the server and
was cancelled.
Check load and resouce usage on DC1005.
[Replications Check,DCNOC001] A recent replication attempt failed:
From DC1005 to DCNOC001
Naming Context: CN=Schema,CN=Configuration ,DC=ds-opm ,DC=lan
The replication generated an error (1726):
The remote procedure call failed.
The failure occurred at 2007-12-03 07:54:10.
The last success occurred at 2007-12-01 12:45:12.
43 failures have occurred since the last success.
The replication RPC call executed for too long at the server and
was cancelled.
Check load and resouce usage on DC1005.
[Replications Check,DCNOC001] A recent replication attempt failed:
From DC1005 to DCNOC001
Naming Context: CN=Configuration,DC=ds-opm ,DC=lan
The replication generated an error (1726):
The remote procedure call failed.
The failure occurred at 2007-12-03 08:40:46.
The last success occurred at 2007-12-01 13:05:40.
103 failures have occurred since the last success.
The replication RPC call executed for too long at the server and
was cancelled.
Check load and resouce usage on DC1005.
[Replications Check,DCNOC001] A recent replication attempt failed:
From DC1005 to DCNOC001
Naming Context: DC=ds-opm,DC=lan
The replication generated an error (1726):
The remote procedure call failed.
The failure occurred at 2007-12-03 08:36:34.
The last success occurred at 2007-12-01 13:42:05.
328 failures have occurred since the last success.
The replication RPC call executed for too long at the server and
was cancelled.
Check load and resouce usage on DC1005.
......................... DCNOC001 passed test Replications
Starting test: NCSecDesc
......................... DCNOC001 passed test NCSecDesc
Starting test: NetLogons
......................... DCNOC001 passed test NetLogons
Starting test: Advertising
......................... DCNOC001 passed test Advertising
Starting test: KnowsOfRoleHolders
[DC1005] LDAP bind failed with error 1053,
The service did not respond to the start or control request in a timely
fashion..
Warning: DC1005 is the Schema Owner, but is not responding to LDAP Bind
.
Warning: DC1005 is the Domain Owner, but is not responding to LDAP Bind
.
Warning: DC1005 is the PDC Owner, but is not responding to LDAP Bind.
Warning: DC1005 is the Rid Owner, but is not responding to LDAP Bind.
Warning: DC1005 is the Infrastructure Update Owner, but is not respondi
ng to LDAP Bind.
......................... DCNOC001 failed test KnowsOfRoleHolders
Starting test: RidManager
......................... DCNOC001 passed test RidManager
Starting test: MachineAccount
......................... DCNOC001 passed test MachineAccount
Starting test: Services
......................... DCNOC001 passed test Services
Starting test: ObjectsReplicated
......................... DCNOC001 passed test ObjectsReplicated
Starting test: frssysvol
......................... DCNOC001 passed test frssysvol
Starting test: frsevent
......................... DCNOC001 passed test frsevent
Starting test: kccevent
An Warning Event occured. EventID: 0x8000072F
Time Generated: 12/03/2007 08:45:13
(Event String could not be retrieved)
......................... DCNOC001 failed test kccevent
Starting test: systemlog
......................... DCNOC001 passed test systemlog
Starting test: VerifyReferences
......................... DCNOC001 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 : ds-opm
Starting test: CrossRefValidation
......................... ds-opm passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... ds-opm passed test CheckSDRefDom
Running enterprise tests on : ds-opm.lan
Starting test: Intersite
......................... ds-opm.lan passed test Intersite
Starting test: FsmoCheck
......................... ds-opm.lan passed test FsmoCheck
From the DCNOC001 I cannot RDP to the DC1005.
I can ping DC1005 from the DCNOC001
I can do a nslookup on the DCNOC001 and DC1005 and DC1006, works fine
The only thing I can do to solve this is to reboot the DC1005.
I hope someone can give me some advise.
Thank you in advance.
DCDIAG on the DC1005 gets stuck on the replication test.
Dcdiag on the DCNOC001 tells me the following:
Domain Controller Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\DC
Starting test: Connectivity
......................... DCNOC001 passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\DC
Starting test: Replications
[Replications Check,DCNOC001] A recent replication attempt failed:
From DC1005 to DCNOC001
Naming Context: DC=ForestDnsZones,DC=ds-op
The replication generated an error (1726):
The remote procedure call failed.
The failure occurred at 2007-12-03 08:06:17.
The last success occurred at 2007-12-01 12:45:12.
43 failures have occurred since the last success.
The replication RPC call executed for too long at the server and
was cancelled.
Check load and resouce usage on DC1005.
[Replications Check,DCNOC001] A recent replication attempt failed:
From DC1005 to DCNOC001
Naming Context: DC=DomainDnsZones,DC=ds-op
The replication generated an error (1726):
The remote procedure call failed.
The failure occurred at 2007-12-03 08:03:13.
The last success occurred at 2007-12-01 12:45:12.
43 failures have occurred since the last success.
The replication RPC call executed for too long at the server and
was cancelled.
Check load and resouce usage on DC1005.
[Replications Check,DCNOC001] A recent replication attempt failed:
From DC1005 to DCNOC001
Naming Context: CN=Schema,CN=Configuration
The replication generated an error (1726):
The remote procedure call failed.
The failure occurred at 2007-12-03 07:54:10.
The last success occurred at 2007-12-01 12:45:12.
43 failures have occurred since the last success.
The replication RPC call executed for too long at the server and
was cancelled.
Check load and resouce usage on DC1005.
[Replications Check,DCNOC001] A recent replication attempt failed:
From DC1005 to DCNOC001
Naming Context: CN=Configuration,DC=ds-opm
The replication generated an error (1726):
The remote procedure call failed.
The failure occurred at 2007-12-03 08:40:46.
The last success occurred at 2007-12-01 13:05:40.
103 failures have occurred since the last success.
The replication RPC call executed for too long at the server and
was cancelled.
Check load and resouce usage on DC1005.
[Replications Check,DCNOC001] A recent replication attempt failed:
From DC1005 to DCNOC001
Naming Context: DC=ds-opm,DC=lan
The replication generated an error (1726):
The remote procedure call failed.
The failure occurred at 2007-12-03 08:36:34.
The last success occurred at 2007-12-01 13:42:05.
328 failures have occurred since the last success.
The replication RPC call executed for too long at the server and
was cancelled.
Check load and resouce usage on DC1005.
......................... DCNOC001 passed test Replications
Starting test: NCSecDesc
......................... DCNOC001 passed test NCSecDesc
Starting test: NetLogons
......................... DCNOC001 passed test NetLogons
Starting test: Advertising
......................... DCNOC001 passed test Advertising
Starting test: KnowsOfRoleHolders
[DC1005] LDAP bind failed with error 1053,
The service did not respond to the start or control request in a timely
fashion..
Warning: DC1005 is the Schema Owner, but is not responding to LDAP Bind
.
Warning: DC1005 is the Domain Owner, but is not responding to LDAP Bind
.
Warning: DC1005 is the PDC Owner, but is not responding to LDAP Bind.
Warning: DC1005 is the Rid Owner, but is not responding to LDAP Bind.
Warning: DC1005 is the Infrastructure Update Owner, but is not respondi
ng to LDAP Bind.
......................... DCNOC001 failed test KnowsOfRoleHolders
Starting test: RidManager
......................... DCNOC001 passed test RidManager
Starting test: MachineAccount
......................... DCNOC001 passed test MachineAccount
Starting test: Services
......................... DCNOC001 passed test Services
Starting test: ObjectsReplicated
......................... DCNOC001 passed test ObjectsReplicated
Starting test: frssysvol
......................... DCNOC001 passed test frssysvol
Starting test: frsevent
......................... DCNOC001 passed test frsevent
Starting test: kccevent
An Warning Event occured. EventID: 0x8000072F
Time Generated: 12/03/2007 08:45:13
(Event String could not be retrieved)
......................... DCNOC001 failed test kccevent
Starting test: systemlog
......................... DCNOC001 passed test systemlog
Starting test: VerifyReferences
......................... DCNOC001 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 : ds-opm
Starting test: CrossRefValidation
......................... ds-opm passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... ds-opm passed test CheckSDRefDom
Running enterprise tests on : ds-opm.lan
Starting test: Intersite
......................... ds-opm.lan passed test Intersite
Starting test: FsmoCheck
......................... ds-opm.lan passed test FsmoCheck
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Would have been my next question, if you are current with post SP1 hotfixes...
I'd recommend 2 things:
- Upgrade network card drivers on all DCs with the latest version from the vendor
- Upgrade to SP2 on the 2 servers with SP1
Hope it helps,
Michael
I'd recommend 2 things:
- Upgrade network card drivers on all DCs with the latest version from the vendor
- Upgrade to SP2 on the 2 servers with SP1
Hope it helps,
Michael
Get PortQryUI http://support.microsoft.com/kb/310456/en-us
and follow the instructions to verify connectivity between the 3 DC's
It could be a VPN issue or firewall issue.