2
W2k Server Replikationsprobleme
Hallo,
ich habe folgendes Problem:
In meiner Domäne befinden sich 2 W2k Server, welche beide redundant eingerichtet sind/waren. Beide als DC im AD. Replikation und so weiter haben bis zu meinem D-day ohne Probleme funktioniert.
Jetzt ist kürzlich in dem einen Server die Systemfestplatte ausgefallen und wurde durch eine neue ersetzt. Danach habe ich ein 5 tage altes Backup aufgespielt und damit begannen die Probleme. Am nächsten Tag nach dem Backup wurden die Nutzerprofile nicht mehr vernünftig, oder gar nicht geladen.
Ich hab jetzt soweit schon feststellen können, dass die Replikation zwischen den beiden Servern nicht mehr stattfindet. Wundert mich auch nicht weiter bei der Empfindlichkeit in Sachen Zeit beim Active Directory (dem einen Server fehlen ja quasi die 5 Tage, die seit dem Backup verstrichen sind).
Server_A: auf diesem war die Festplatte kaput und das Backup eingespielt.
Server_B: der andere Server halt.
Ich hab mal auf beiden dcdiag ausgeführt, hier die Ergebnisse:
Server_A:
DC Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial non skippeable tests
Testing server: Default-First-Site-Name\Server_A
Starting test: Connectivity
......................... Server_A passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\Server_A
Starting test: Replications
[Replications Check,Server_A] Inbound replication is disabled.
To correct, run "repadmin /options Server_A -DISABLE_INBOUND_REPL"
[Replications Check,Server_A] Outbound replication is disabled.
To correct, run "repadmin /options Server_A -DISABLE_OUTBOUND_REPL"
......................... Server_A failed test Replications
Starting test: NCSecDesc
......................... Server_A passed test NCSecDesc
Starting test: NetLogons
......................... Server_A passed test NetLogons
Starting test: Advertising
Fatal Error:DsGetDcName (Server_A) call failed, error 1355
The Locator could not find the server.
......................... Server_A failed test Advertising
Starting test: KnowsOfRoleHolders
......................... Server_A passed test KnowsOfRoleHolders
Starting test: RidManager
......................... Server_A passed test RidManager
Starting test: MachineAccount
......................... Server_A passed test MachineAccount
Starting test: Services
NETLOGON Service is paused on [Server_A]
......................... Server_A failed test Services
Starting test: ObjectsReplicated
......................... Server_A passed test ObjectsReplicated
Starting test: frssysvol
There are errors after the SYSVOL has been shared.
The SYSVOL can prevent the AD from starting.
......................... Server_A passed test frssysvol
Starting test: kccevent
......................... Server_A passed test kccevent
Starting test: systemlog
......................... Server_A passed test systemlog
Running enterprise tests on : d.i.c.t.d
Starting test: Intersite
......................... d.i.c.t.d passed test Intersite
Starting test: FsmoCheck
Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355
A Global Catalog Server could not be located - All GC's are down.
Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
A Time Server could not be located.
The server holding the PDC role is down.
Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error 1355
A Good Time Server could not be located.
Warning: DcGetDcName(KDC_REQUIRED) call failed, error 1355
A KDC could not be located - All the KDCs are down.
......................... d.i.c.t.d failed test FsmoCheck
Server_B
DC Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial non skippeable tests
Testing server: Default-First-Site-Name\Server_B
Starting test: Connectivity
......................... Server_B passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\Server_B
Starting test: Replications
[Replications Check,Server_B] A recent replication attempt failed:
From Server_A to Server_B
Naming Context: CN=Schema,CN=Configuration,DC=d,DC=i,DC=c,DC=t,DC=de
The replication generated an error (1908):
Could not find the domain controller for this domain.
The failure occurred at 2009-10-06 16:56.49.
The last success occurred at 2009-10-01 15:47.27.
99 failures have occurred since the last success.
Kerberos Error.
A KDC was not found to authenticate the call.
Check that sufficient domain controllers are available.
[Server_A] DsBind() failed with error -2146893022,
The target principal name is incorrect..
[Replications Check,Server_B] A recent replication attempt failed:
From Server_A to Server_B
Naming Context: CN=Configuration,DC=d,DC=i,DC=c,DC=t,DC=de
The replication generated an error (1908):
Could not find the domain controller for this domain.
The failure occurred at 2009-10-06 17:01.13.
The last success occurred at 2009-10-01 16:28.31.
662 failures have occurred since the last success.
Kerberos Error.
A KDC was not found to authenticate the call.
Check that sufficient domain controllers are available.
[Replications Check,Server_B] A recent replication attempt failed:
From Server_A to Server_B
Naming Context: DC=d,DC=i,DC=c,DC=t,DC=de
The replication generated an error (1908):
Could not find the domain controller for this domain.
The failure occurred at 2009-10-06 16:59.03.
The last success occurred at 2009-10-01 16:22.02.
520 failures have occurred since the last success.
Kerberos Error.
A KDC was not found to authenticate the call.
Check that sufficient domain controllers are available.
......................... Server_B passed test Replications
Starting test: NcecDesc
......................... Server_B passed test NcecDesc
Starting test: NetLogons
......................... Server_B passed test NetLogons
Starting test: Advertising
Warning: DsGetDcName returned information for \\Server_A.d.i.c.t.d, when we were trying to reach Server_B.
Server is not responding or is not considered suitable.
......................... Server_B failed test Advertising
Starting test: KnowsOfRoleHolders
Warning: Server_A is the Schema Owner, but is not responding to DS RPC Bind.
[Server_A] LDAP bind failed with error 31,
A device attached to the system is not functioning..
Warning: Server_A is the Schema Owner, but is not responding to LDAP Bind.
Warning: Server_A is the Domain Owner, but is not responding to DS RPC Bind.
Warning: Server_A is the Domain Owner, but is not responding to LDAP Bind.
Warning: Server_A is the PDC Owner, but is not responding to DS RPC Bind.
Warning: Server_A is the PDC Owner, but is not responding to LDAP Bind.
Warning: Server_A is the Rid Owner, but is not responding to DS RPC Bind.
Warning: Server_A is the Rid Owner, but is not responding to LDAP Bind.
Warning: Server_A is the Infrastructure Update Owner, but is not responding to DS RPC Bind.
Warning: Server_A is the Infrastructure Update Owner, but is not responding to LDAP Bind.
......................... Server_B failed test KnowsOfRoleHolders
Starting test: RidManager
[Server_B] DsBindWithCred() failed with error -2146893022. The target principal name is incorrect.
......................... Server_B failed test RidManager
Starting test: MachineAccount
......................... Server_B passed test MachineAccount
Starting test: Services
RPCLOCATOR Service is stopped on [Server_B]
NETLOGON Service is paused on [Server_B]
......................... Server_B failed test Services
Starting test: ObjectsReplicated
......................... Server_B passed test ObjectsReplicated
Starting test: frssysvol
There are errors after the SYSVOL has been shared.
The SYSVOL can prevent the AD from starting.
......................... Server_B passed test frssysvol
Starting test: kccevent
......................... Server_B passed test kccevent
Starting test: systemlog
An Error Event occured. EventID: 0x0000168E
Time Generated: 10/06/2009 16:13:26
(Event String could not be retrieved)
An Error Event occured. EventID: 0x0000041B
Time Generated: 10/06/2009 17:00:32
Event String: The DHCP/BINL service has determined that it is
......................... Server_B failed test systemlog
Running enterprise tests on : d.i.c.t.d
Starting test: Intersite
......................... d.i.c.t.d passed test Intersite
Starting test: FsmoCheck
Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355
A Global Catalog Server could not be located - All GC's are down.
Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
A Time Server could not be located.
The server holding the PDC role is down.
Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error 1355
A Good Time Server could not be located.
Warning: DcGetDcName(KDC_REQUIRED) call failed, error 1355
A KDC could not be located - All the KDc are down.
......................... d.i.c.t.d failed test FsmoCheck
Weitere Fehler und Merkmale:
- Server_B kommt nichtmehr in AD und behauptet die Domäne gibt es nicht mehr
- Server_A hat soweit keine Probleme mit dem AD, aber sagt, keine Replikation mit Server_B möglich
Ich wäre über Hinweise oder Lösungen, wie ich das Problem lösen kann sehr dankbar. Ich hab auch schon versucht Server_B herunterzustufen, aber ohne Erfolg. Er bricht dies mit einer Fehlermeldung ab.
Nach meinen Überlegungen würde ich gerne Server_B zwingen sich mit Server_A zu replizieren, geht das? Und wenn ja wie?
Viele Grüße,
Flouw
ich habe folgendes Problem:
In meiner Domäne befinden sich 2 W2k Server, welche beide redundant eingerichtet sind/waren. Beide als DC im AD. Replikation und so weiter haben bis zu meinem D-day ohne Probleme funktioniert.
Jetzt ist kürzlich in dem einen Server die Systemfestplatte ausgefallen und wurde durch eine neue ersetzt. Danach habe ich ein 5 tage altes Backup aufgespielt und damit begannen die Probleme. Am nächsten Tag nach dem Backup wurden die Nutzerprofile nicht mehr vernünftig, oder gar nicht geladen.
Ich hab jetzt soweit schon feststellen können, dass die Replikation zwischen den beiden Servern nicht mehr stattfindet. Wundert mich auch nicht weiter bei der Empfindlichkeit in Sachen Zeit beim Active Directory (dem einen Server fehlen ja quasi die 5 Tage, die seit dem Backup verstrichen sind).
Server_A: auf diesem war die Festplatte kaput und das Backup eingespielt.
Server_B: der andere Server halt.
Ich hab mal auf beiden dcdiag ausgeführt, hier die Ergebnisse:
Server_A:
DC Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial non skippeable tests
Testing server: Default-First-Site-Name\Server_A
Starting test: Connectivity
......................... Server_A passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\Server_A
Starting test: Replications
[Replications Check,Server_A] Inbound replication is disabled.
To correct, run "repadmin /options Server_A -DISABLE_INBOUND_REPL"
[Replications Check,Server_A] Outbound replication is disabled.
To correct, run "repadmin /options Server_A -DISABLE_OUTBOUND_REPL"
......................... Server_A failed test Replications
Starting test: NCSecDesc
......................... Server_A passed test NCSecDesc
Starting test: NetLogons
......................... Server_A passed test NetLogons
Starting test: Advertising
Fatal Error:DsGetDcName (Server_A) call failed, error 1355
The Locator could not find the server.
......................... Server_A failed test Advertising
Starting test: KnowsOfRoleHolders
......................... Server_A passed test KnowsOfRoleHolders
Starting test: RidManager
......................... Server_A passed test RidManager
Starting test: MachineAccount
......................... Server_A passed test MachineAccount
Starting test: Services
NETLOGON Service is paused on [Server_A]
......................... Server_A failed test Services
Starting test: ObjectsReplicated
......................... Server_A passed test ObjectsReplicated
Starting test: frssysvol
There are errors after the SYSVOL has been shared.
The SYSVOL can prevent the AD from starting.
......................... Server_A passed test frssysvol
Starting test: kccevent
......................... Server_A passed test kccevent
Starting test: systemlog
......................... Server_A passed test systemlog
Running enterprise tests on : d.i.c.t.d
Starting test: Intersite
......................... d.i.c.t.d passed test Intersite
Starting test: FsmoCheck
Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355
A Global Catalog Server could not be located - All GC's are down.
Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
A Time Server could not be located.
The server holding the PDC role is down.
Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error 1355
A Good Time Server could not be located.
Warning: DcGetDcName(KDC_REQUIRED) call failed, error 1355
A KDC could not be located - All the KDCs are down.
......................... d.i.c.t.d failed test FsmoCheck
Server_B
DC Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial non skippeable tests
Testing server: Default-First-Site-Name\Server_B
Starting test: Connectivity
......................... Server_B passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\Server_B
Starting test: Replications
[Replications Check,Server_B] A recent replication attempt failed:
From Server_A to Server_B
Naming Context: CN=Schema,CN=Configuration,DC=d,DC=i,DC=c,DC=t,DC=de
The replication generated an error (1908):
Could not find the domain controller for this domain.
The failure occurred at 2009-10-06 16:56.49.
The last success occurred at 2009-10-01 15:47.27.
99 failures have occurred since the last success.
Kerberos Error.
A KDC was not found to authenticate the call.
Check that sufficient domain controllers are available.
[Server_A] DsBind() failed with error -2146893022,
The target principal name is incorrect..
[Replications Check,Server_B] A recent replication attempt failed:
From Server_A to Server_B
Naming Context: CN=Configuration,DC=d,DC=i,DC=c,DC=t,DC=de
The replication generated an error (1908):
Could not find the domain controller for this domain.
The failure occurred at 2009-10-06 17:01.13.
The last success occurred at 2009-10-01 16:28.31.
662 failures have occurred since the last success.
Kerberos Error.
A KDC was not found to authenticate the call.
Check that sufficient domain controllers are available.
[Replications Check,Server_B] A recent replication attempt failed:
From Server_A to Server_B
Naming Context: DC=d,DC=i,DC=c,DC=t,DC=de
The replication generated an error (1908):
Could not find the domain controller for this domain.
The failure occurred at 2009-10-06 16:59.03.
The last success occurred at 2009-10-01 16:22.02.
520 failures have occurred since the last success.
Kerberos Error.
A KDC was not found to authenticate the call.
Check that sufficient domain controllers are available.
......................... Server_B passed test Replications
Starting test: NcecDesc
......................... Server_B passed test NcecDesc
Starting test: NetLogons
......................... Server_B passed test NetLogons
Starting test: Advertising
Warning: DsGetDcName returned information for \\Server_A.d.i.c.t.d, when we were trying to reach Server_B.
Server is not responding or is not considered suitable.
......................... Server_B failed test Advertising
Starting test: KnowsOfRoleHolders
Warning: Server_A is the Schema Owner, but is not responding to DS RPC Bind.
[Server_A] LDAP bind failed with error 31,
A device attached to the system is not functioning..
Warning: Server_A is the Schema Owner, but is not responding to LDAP Bind.
Warning: Server_A is the Domain Owner, but is not responding to DS RPC Bind.
Warning: Server_A is the Domain Owner, but is not responding to LDAP Bind.
Warning: Server_A is the PDC Owner, but is not responding to DS RPC Bind.
Warning: Server_A is the PDC Owner, but is not responding to LDAP Bind.
Warning: Server_A is the Rid Owner, but is not responding to DS RPC Bind.
Warning: Server_A is the Rid Owner, but is not responding to LDAP Bind.
Warning: Server_A is the Infrastructure Update Owner, but is not responding to DS RPC Bind.
Warning: Server_A is the Infrastructure Update Owner, but is not responding to LDAP Bind.
......................... Server_B failed test KnowsOfRoleHolders
Starting test: RidManager
[Server_B] DsBindWithCred() failed with error -2146893022. The target principal name is incorrect.
......................... Server_B failed test RidManager
Starting test: MachineAccount
......................... Server_B passed test MachineAccount
Starting test: Services
RPCLOCATOR Service is stopped on [Server_B]
NETLOGON Service is paused on [Server_B]
......................... Server_B failed test Services
Starting test: ObjectsReplicated
......................... Server_B passed test ObjectsReplicated
Starting test: frssysvol
There are errors after the SYSVOL has been shared.
The SYSVOL can prevent the AD from starting.
......................... Server_B passed test frssysvol
Starting test: kccevent
......................... Server_B passed test kccevent
Starting test: systemlog
An Error Event occured. EventID: 0x0000168E
Time Generated: 10/06/2009 16:13:26
(Event String could not be retrieved)
An Error Event occured. EventID: 0x0000041B
Time Generated: 10/06/2009 17:00:32
Event String: The DHCP/BINL service has determined that it is
......................... Server_B failed test systemlog
Running enterprise tests on : d.i.c.t.d
Starting test: Intersite
......................... d.i.c.t.d passed test Intersite
Starting test: FsmoCheck
Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355
A Global Catalog Server could not be located - All GC's are down.
Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
A Time Server could not be located.
The server holding the PDC role is down.
Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error 1355
A Good Time Server could not be located.
Warning: DcGetDcName(KDC_REQUIRED) call failed, error 1355
A KDC could not be located - All the KDc are down.
......................... d.i.c.t.d failed test FsmoCheck
Weitere Fehler und Merkmale:
- Server_B kommt nichtmehr in AD und behauptet die Domäne gibt es nicht mehr
- Server_A hat soweit keine Probleme mit dem AD, aber sagt, keine Replikation mit Server_B möglich
Ich wäre über Hinweise oder Lösungen, wie ich das Problem lösen kann sehr dankbar. Ich hab auch schon versucht Server_B herunterzustufen, aber ohne Erfolg. Er bricht dies mit einer Fehlermeldung ab.
Nach meinen Überlegungen würde ich gerne Server_B zwingen sich mit Server_A zu replizieren, geht das? Und wenn ja wie?
Viele Grüße,
Flouw
Share on Facebook
Share on Twitter
Share on Reddit
Share on LinkedinPlease also mark the comments that contributed to the solution of the article
Content-Key: 126574
Url: https://administrator.de/contentid/126574
Printed on: April 20, 2024 at 00:04 o'clock
2 Comments
Latest comment
Moin,
welcher hat die FSMO-Rollen?
Gruß
24
welcher hat die FSMO-Rollen?
Gruß
24
Hallo,
Server_A hat die FSMO-Rollen.
Server_A hat die FSMO-Rollen.
