Ik heb voor een school een netwerk gebouwt dat bestaat uit 2 domein server... Deze domeinserver zijn middels een VPN verbinding (2 ISA proxy's) aan elkaar verbonden.
Het probleem is dat deze server elkaar niet meer willen repliceren. Iemand enig idee hoe het komt ? Ze kunnen elkaar prima bereiken middels tracert en ping.
netdiag geeft geen problemen... Ik heb hieronder dcdiag gezet... De server willen elkaar gewoon niet meer bereiken...
<code>
D:\Shared Apps>dcdiag -fix
Domain Controller Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\IS-MM-DS
Starting test: Connectivity
......................... IS-MM-DS passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\IS-MM-DS
Starting test: Replications
[Replications Check,IS-MM-DS] A recent replication attempt failed:
From BE-MM-DS to IS-MM-DS
Naming Context: DC=ForestDnsZones,DC=##########,DC=nl
The replication generated an error (1256):
The remote system is not available. For information about network tr
oubleshooting, see Windows Help.
The failure occurred at 2005-04-27 15:51:29.
The last success occurred at 2005-04-26 12:03:14.
106 failures have occurred since the last success.
[BE-MM-DS] DsBindWithSpnEx() failed with error 1722,
The RPC server is unavailable..
[Replications Check,IS-MM-DS] A recent replication attempt failed:
From BE-MM-DS to IS-MM-DS
Naming Context: DC=DomainDnsZones,DC=#########,DC=nl
The replication generated an error (1256):
The remote system is not available. For information about network tr
oubleshooting, see Windows Help.
The failure occurred at 2005-04-27 15:51:29.
The last success occurred at 2005-04-26 12:03:14.
106 failures have occurred since the last success.
[Replications Check,IS-MM-DS] A recent replication attempt failed:
From BE-MM-DS to IS-MM-DS
Naming Context: CN=Schema,CN=Configuration,DC=#########,DC=nl
The replication generated an error (8524):
The DSA operation is unable to proceed because of a DNS lookup failu
re.
The failure occurred at 2005-04-27 15:51:31.
The last success occurred at 2005-04-26 12:03:14.
105 failures have occurred since the last success.
The guid-based DNS name b87eb4b3-7936-4d23-8c12-3ff25aabb7c8._msdcs.
########.nl
is not registered on one or more DNS servers.
[Replications Check,IS-MM-DS] A recent replication attempt failed:
From BE-MM-DS to IS-MM-DS
Naming Context: CN=Configuration,DC=########,DC=nl
The replication generated an error (8524):
The DSA operation is unable to proceed because of a DNS lookup failu
re.
The failure occurred at 2005-04-27 15:51:29.
The last success occurred at 2005-04-26 12:06:57.
137 failures have occurred since the last success.
The guid-based DNS name b87eb4b3-7936-4d23-8c12-3ff25aabb7c8._msdcs.
##########.nl
is not registered on one or more DNS servers.
[Replications Check,IS-MM-DS] A recent replication attempt failed:
From BE-MM-DS to IS-MM-DS
Naming Context: DC=##########,DC=nl
The replication generated an error (8524):
The DSA operation is unable to proceed because of a DNS lookup failu
re.
The failure occurred at 2005-04-27 15:51:33.
The last success occurred at 2005-04-26 12:08:14.
1004 failures have occurred since the last success.
The guid-based DNS name b87eb4b3-7936-4d23-8c12-3ff25aabb7c8._msdcs.
##########.nl
is not registered on one or more DNS servers.
REPLICATION-RECEIVED LATENCY WARNING
IS-MM-DS: Current time is 2005-04-27 16:03:10.
DC=ForestDnsZones,DC=############,DC=nl
Last replication recieved from BE-MM-DS at 2005-04-26 12:03:14.
DC=DomainDnsZones,DC=###########,DC=nl
Last replication recieved from BE-MM-DS at 2005-04-26 12:03:14.
CN=Schema,CN=Configuration,DC=#########,DC=nl
Last replication recieved from BE-MM-DS at 2005-04-26 12:03:14.
CN=Configuration,DC=############,DC=nl
Last replication recieved from BE-MM-DS at 2005-04-26 12:06:57.
DC=##########,DC=nl
Last replication recieved from BE-MM-DS at 2005-04-26 12:08:14.
......................... IS-MM-DS passed test Replications
Starting test: NCSecDesc
......................... IS-MM-DS passed test NCSecDesc
Starting test: NetLogons
......................... IS-MM-DS passed test NetLogons
Starting test: Advertising
......................... IS-MM-DS passed test Advertising
Starting test: KnowsOfRoleHolders
Warning: BE-MM-DS is the Rid Owner, but is not responding to DS RPC Bin
d.
[BE-MM-DS] LDAP search failed with error 58,
The specified server cannot perform the requested operation..
Warning: BE-MM-DS is the Rid Owner, but is not responding to LDAP Bind.
......................... IS-MM-DS failed test KnowsOfRoleHolders
Starting test: RidManager
......................... IS-MM-DS failed test RidManager
Starting test: MachineAccount
......................... IS-MM-DS passed test MachineAccount
Starting test: Services
......................... IS-MM-DS passed test Services
Starting test: ObjectsReplicated
......................... IS-MM-DS passed test ObjectsReplicated
Starting test: frssysvol
......................... IS-MM-DS passed test frssysvol
Starting test: frsevent
There are warning or error events within the last 24 hours after the
SYSVOL has been shared. Failing SYSVOL replication problems may cause
Group Policy problems.
......................... IS-MM-DS failed test frsevent
Starting test: kccevent
An Warning Event occured. EventID: 0x8000072D
Time Generated: 04/27/2005 15:52:15
(Event String could not be retrieved)
......................... IS-MM-DS failed test kccevent
Starting test: systemlog
An Error Event occured. EventID: 0x00000423
Time Generated: 04/27/2005 15:22:50
Event String: The DHCP service failed to see a directory server
An Error Event occured. EventID: 0xC0000021
Time Generated: 04/27/2005 15:23:19
(Event String could not be retrieved)
An Error Event occured. EventID: 0xC0000021
Time Generated: 04/27/2005 15:23:19
(Event String could not be retrieved)
An Error Event occured. EventID: 0xC0000021
Time Generated: 04/27/2005 15:23:19
(Event String could not be retrieved)
An Error Event occured. EventID: 0xC0000021
Time Generated: 04/27/2005 15:23:19
(Event String could not be retrieved)
An Error Event occured. EventID: 0xC0000021
Time Generated: 04/27/2005 15:23:19
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000423
Time Generated: 04/27/2005 15:23:19
Event String: The DHCP service failed to see a directory server
An Error Event occured. EventID: 0xC00010E1
Time Generated: 04/27/2005 15:25:58
Event String: The name "########### :1b" could not be
An Error Event occured. EventID: 0xC0000423
Time Generated: 04/27/2005 15:37:15
(Event String could not be retrieved)
......................... IS-MM-DS failed test systemlog
Starting test: VerifyReferences
......................... IS-MM-DS 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 : ##########
Starting test: CrossRefValidation
......................... ########## passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... ########## passed test CheckSDRefDom
Running enterprise tests on : ##########.nl
Starting test: Intersite
......................... ###########.nl passed test Intersite
Starting test: FsmoCheck
......................... ###########.nl passed test FsmoCheck
D:\Shared Apps>
</code>
Het probleem is dat deze server elkaar niet meer willen repliceren. Iemand enig idee hoe het komt ? Ze kunnen elkaar prima bereiken middels tracert en ping.
netdiag geeft geen problemen... Ik heb hieronder dcdiag gezet... De server willen elkaar gewoon niet meer bereiken...
<code>
D:\Shared Apps>dcdiag -fix
Domain Controller Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\IS-MM-DS
Starting test: Connectivity
......................... IS-MM-DS passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\IS-MM-DS
Starting test: Replications
[Replications Check,IS-MM-DS] A recent replication attempt failed:
From BE-MM-DS to IS-MM-DS
Naming Context: DC=ForestDnsZones,DC=##########,DC=nl
The replication generated an error (1256):
The remote system is not available. For information about network tr
oubleshooting, see Windows Help.
The failure occurred at 2005-04-27 15:51:29.
The last success occurred at 2005-04-26 12:03:14.
106 failures have occurred since the last success.
[BE-MM-DS] DsBindWithSpnEx() failed with error 1722,
The RPC server is unavailable..
[Replications Check,IS-MM-DS] A recent replication attempt failed:
From BE-MM-DS to IS-MM-DS
Naming Context: DC=DomainDnsZones,DC=#########,DC=nl
The replication generated an error (1256):
The remote system is not available. For information about network tr
oubleshooting, see Windows Help.
The failure occurred at 2005-04-27 15:51:29.
The last success occurred at 2005-04-26 12:03:14.
106 failures have occurred since the last success.
[Replications Check,IS-MM-DS] A recent replication attempt failed:
From BE-MM-DS to IS-MM-DS
Naming Context: CN=Schema,CN=Configuration,DC=#########,DC=nl
The replication generated an error (8524):
The DSA operation is unable to proceed because of a DNS lookup failu
re.
The failure occurred at 2005-04-27 15:51:31.
The last success occurred at 2005-04-26 12:03:14.
105 failures have occurred since the last success.
The guid-based DNS name b87eb4b3-7936-4d23-8c12-3ff25aabb7c8._msdcs.
########.nl
is not registered on one or more DNS servers.
[Replications Check,IS-MM-DS] A recent replication attempt failed:
From BE-MM-DS to IS-MM-DS
Naming Context: CN=Configuration,DC=########,DC=nl
The replication generated an error (8524):
The DSA operation is unable to proceed because of a DNS lookup failu
re.
The failure occurred at 2005-04-27 15:51:29.
The last success occurred at 2005-04-26 12:06:57.
137 failures have occurred since the last success.
The guid-based DNS name b87eb4b3-7936-4d23-8c12-3ff25aabb7c8._msdcs.
##########.nl
is not registered on one or more DNS servers.
[Replications Check,IS-MM-DS] A recent replication attempt failed:
From BE-MM-DS to IS-MM-DS
Naming Context: DC=##########,DC=nl
The replication generated an error (8524):
The DSA operation is unable to proceed because of a DNS lookup failu
re.
The failure occurred at 2005-04-27 15:51:33.
The last success occurred at 2005-04-26 12:08:14.
1004 failures have occurred since the last success.
The guid-based DNS name b87eb4b3-7936-4d23-8c12-3ff25aabb7c8._msdcs.
##########.nl
is not registered on one or more DNS servers.
REPLICATION-RECEIVED LATENCY WARNING
IS-MM-DS: Current time is 2005-04-27 16:03:10.
DC=ForestDnsZones,DC=############,DC=nl
Last replication recieved from BE-MM-DS at 2005-04-26 12:03:14.
DC=DomainDnsZones,DC=###########,DC=nl
Last replication recieved from BE-MM-DS at 2005-04-26 12:03:14.
CN=Schema,CN=Configuration,DC=#########,DC=nl
Last replication recieved from BE-MM-DS at 2005-04-26 12:03:14.
CN=Configuration,DC=############,DC=nl
Last replication recieved from BE-MM-DS at 2005-04-26 12:06:57.
DC=##########,DC=nl
Last replication recieved from BE-MM-DS at 2005-04-26 12:08:14.
......................... IS-MM-DS passed test Replications
Starting test: NCSecDesc
......................... IS-MM-DS passed test NCSecDesc
Starting test: NetLogons
......................... IS-MM-DS passed test NetLogons
Starting test: Advertising
......................... IS-MM-DS passed test Advertising
Starting test: KnowsOfRoleHolders
Warning: BE-MM-DS is the Rid Owner, but is not responding to DS RPC Bin
d.
[BE-MM-DS] LDAP search failed with error 58,
The specified server cannot perform the requested operation..
Warning: BE-MM-DS is the Rid Owner, but is not responding to LDAP Bind.
......................... IS-MM-DS failed test KnowsOfRoleHolders
Starting test: RidManager
......................... IS-MM-DS failed test RidManager
Starting test: MachineAccount
......................... IS-MM-DS passed test MachineAccount
Starting test: Services
......................... IS-MM-DS passed test Services
Starting test: ObjectsReplicated
......................... IS-MM-DS passed test ObjectsReplicated
Starting test: frssysvol
......................... IS-MM-DS passed test frssysvol
Starting test: frsevent
There are warning or error events within the last 24 hours after the
SYSVOL has been shared. Failing SYSVOL replication problems may cause
Group Policy problems.
......................... IS-MM-DS failed test frsevent
Starting test: kccevent
An Warning Event occured. EventID: 0x8000072D
Time Generated: 04/27/2005 15:52:15
(Event String could not be retrieved)
......................... IS-MM-DS failed test kccevent
Starting test: systemlog
An Error Event occured. EventID: 0x00000423
Time Generated: 04/27/2005 15:22:50
Event String: The DHCP service failed to see a directory server
An Error Event occured. EventID: 0xC0000021
Time Generated: 04/27/2005 15:23:19
(Event String could not be retrieved)
An Error Event occured. EventID: 0xC0000021
Time Generated: 04/27/2005 15:23:19
(Event String could not be retrieved)
An Error Event occured. EventID: 0xC0000021
Time Generated: 04/27/2005 15:23:19
(Event String could not be retrieved)
An Error Event occured. EventID: 0xC0000021
Time Generated: 04/27/2005 15:23:19
(Event String could not be retrieved)
An Error Event occured. EventID: 0xC0000021
Time Generated: 04/27/2005 15:23:19
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000423
Time Generated: 04/27/2005 15:23:19
Event String: The DHCP service failed to see a directory server
An Error Event occured. EventID: 0xC00010E1
Time Generated: 04/27/2005 15:25:58
Event String: The name "########### :1b" could not be
An Error Event occured. EventID: 0xC0000423
Time Generated: 04/27/2005 15:37:15
(Event String could not be retrieved)
......................... IS-MM-DS failed test systemlog
Starting test: VerifyReferences
......................... IS-MM-DS 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 : ##########
Starting test: CrossRefValidation
......................... ########## passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... ########## passed test CheckSDRefDom
Running enterprise tests on : ##########.nl
Starting test: Intersite
......................... ###########.nl passed test Intersite
Starting test: FsmoCheck
......................... ###########.nl passed test FsmoCheck
D:\Shared Apps>
</code>
:strip_exif()/u/21590/icon4.gif?f=community)
Dit topic is gesloten.