Fehler beim Hinzufügen eines XP Prof. Clients zur Domäne

Erst mal Danke für die schnelle Antwort.

Ein Ping auf Server.domain.local war ebenfalls erfolgreich.

DCDiag lieferte mir folgendes Ergebnis:

Domain Controller Diagnosis
Performing initial setup:

• Verifying that the local machine server2, is a DC.
• Connecting to directory service on server server2.
• Collecting site info.
• Identifying all servers.
• Found 2 DC(s). Testing 1 of them.

Done gathering initial info.
Doing initial required tests

Testing server: Standardname-des-ersten-Standorts\SERVER2
Starting test: Connectivity

• Active Directory LDAP Services Check
• Active Directory RPC Services Check ......................... SERVER2 passed test Connectivity

Doing primary tests Testing server: Standardname-des-ersten-Standorts\SERVER2
Starting test: Replications

• Replications Check [Replications Check,SERVER2] A recent replication attempt failed: From SERVER1 to SERVER2

Naming Context: CN=Schema,CN=Configuration,DC=##############,DC=de
The replication generated an error (1908):
Der Domänencontroller für diese Domäne wurde nicht gefunden.
The failure occurred at 2009-04-07 09:58.19.
The last success occurred at 2009-03-12 10:47.58.
627 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,SERVER2] A recent replication attempt failed:
From SERVER1 to SERVER2
Naming Context: CN=Configuration,DC=##############,DC=de
The replication generated an error (1908):
Der Domänencontroller für diese Domäne wurde nicht gefunden.
The failure occurred at 2009-04-07 09:58.19.
The last success occurred at 2009-03-12 11:03.55.
627 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,SERVER2] A recent replication attempt failed: From SERVER1 to SERVER2
Naming Context: DC=##############,DC=de
The replication generated an error (1908):
Der Domänencontroller für diese Domäne wurde nicht gefunden.
The failure occurred at 2009-04-07 09:58.19.
The last success occurred at 2009-03-12 10:47.58.
627 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. ......................... SERVER2 passed test Replications
Test omitted by user request: Topology
Test omitted by user request: CutoffServers
Starting test: NCSecDesc

• Security Permissions Check for CN=Schema,CN=Configuration,DC=##############,DC=de
• Security Permissions Check for CN=Configuration,DC=##############,DC=de
• Security Permissions Check for DC=##############,DC=de ......................... SERVER2 passed test NCSecDesc

Starting test: NetLogons * Network Logons Privileges Check ......................... SERVER2 passed test NetLogons
Starting test: Advertising Warning: DsGetDcName returned information for \\server1.##############.de, when we were trying to reach SERVER2.
Server is not responding or is not considered suitable.
The DC SERVER2 is advertising itself as a DC and having a DS.
The DC SERVER2 is advertising as an LDAP server
The DC SERVER2 is advertising as having a writeable directory
The DC SERVER2 is advertising as a Key Distribution Center
Warning: SERVER2 is not advertising as a time server.
The DS SERVER2 is advertising as a GC. ......................... SERVER2 failed test Advertising
Starting test: KnowsOfRoleHolders
Role Schema Owner = CN=NTDS Settings,CN=SERVER2,CN=Servers,CN=Standardname-des-ersten-Standorts,CN=Sites,CN=Configuration,DC=##############,DC=de
Role Domain Owner = CN=NTDS Settings,CN=SERVER2,CN=Servers,CN=Standardname-des-ersten-Standorts,CN=Sites,CN=Configuration,DC=##############,DC=de
Role PDC Owner = CN=NTDS Settings,CN=SERVER1,CN=Servers,CN=Standardname-des-ersten-Standorts,CN=Sites,CN=Configuration,DC=##############,DC=de
Role Rid Owner = CN=NTDS Settings,CN=SERVER1,CN=Servers,CN=Standardname-des-ersten-Standorts,CN=Sites,CN=Configuration,DC=##############,DC=de
Role Infrastructure Update Owner = CN=NTDS Settings,CN=SERVER1,CN=Servers,CN=Standardname-des-ersten-Standorts,CN=Sites,CN=Configuration,DC=##############,DC=de ......................... SERVER2 passed test KnowsOfRoleHolders
Starting test: RidManager

• Available RID Pool for the Domain is 2605 to 1073741823
• server1.##############.de is the RID Master
• DsBind with RID Master was successful * rIDAllocationPool is 1605 to 2104
• rIDNextRID: 1631 * rIDPreviousAllocationPool is 1605 to 2104 ......................... SERVER2 passed test RidManager

Starting test: MachineAccount

• SPN found :LDAP/server2.##############.de/##############.de
• SPN found :LDAP/server2.##############.de
• SPN found :LDAP/SERVER2
• SPN found :LDAP/server2.##############.de/####1
• SPN found :LDAP/###########################._msdcs.##############.de
• SPN found :#######################/#######################/##############.de
• SPN found :HOST/server2.##############.de/##############.de
• SPN found :HOST/server2.##############.de
• SPN found :HOST/SERVER2
• SPN found :HOST/server2.##############.de/####1
• SPN found :GC/server2.##############.de/##############.de ......................... SERVER2 passed test MachineAccount

Starting test: Services

• Checking Service: Dnscache
• Checking Service: NtFrs
• Checking Service: IsmServ
• Checking Service: kdc
• Checking Service: SamSs
• Checking Service: LanmanServer
• Checking Service: LanmanWorkstation
• Checking Service: RpcSs
• Checking Service: RPCLOCATOR
• Checking Service: w32time w32time Service is stopped on [SERVER2]
• Checking Service: TrkWks
• Checking Service: TrkSvr
• Checking Service: NETLOGON ......................... SERVER2 failed test Services

Test omitted by user request: OutboundSecureChannels
Starting test: ObjectsReplicated
SERVER2 is in domain DC=##############,DC=de
Checking for CN=SERVER2,OU=Domain Controllers,DC=##############,DC=de in domain DC=##############,DC=de on 1 servers
Object is up-to-date on all servers.
Checking for CN=NTDS Settings,CN=SERVER2,CN=Servers,CN=Standardname-des-ersten-Standorts,CN=Sites,CN=Configuration,DC=##############,DC=de in domain CN=Configuration,DC=##############,DC=de on 1 servers Object is up-to-date on all servers. ......................... SERVER2 passed test ObjectsReplicated
Starting test: frssysvol

• The File Replication Service Event log test

Error: No record of File Replication System, SYSVOL started.
The Active Directory may be prevented from starting.
There are errors after the SYSVOL has been shared.
The SYSVOL can prevent the AD from starting.
An Warning Event occured. EventID: 0x800034FD
Time Generated: 04/06/2009 15:59:58 (Event String could not be retrieved)
An Warning Event occured. EventID: 0x800034C4
Time Generated: 04/06/2009 16:04:04 (Event String could not be retrieved) ......................... SERVER2 passed test frssysvol
Starting test: kccevent

• The KCC Event log test

Found no KCC errors in Directory Service Event log in the last 15 minutes. ......................... SERVER2 passed test kccevent
Starting test: systemlog

• The System Event log test

Found no errors in System Event log in the last 60 minutes. ......................... SERVER2 passed test systemlog Running enterprise tests on : ##############.de
Starting test: Intersite
Skipping site Standardname-des-ersten-Standorts, this site is outside the scope provided by the command line arguments provided. ......................... ##############.de 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.
PDC Name: \\server1.##############.de Locator Flags: 0xe00001bd
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. ......................... ##############.de failed test FsmoCheck -----------------------------------------------------------------------------------------------------------

Hier taucht wie gesagt immer wieder der Fehler auf, dass er den Domänencontroller nicht finden kann.

Ich bitte um Verständnis, dass ich mich nicht so perfekt auskenne. Das letzte mal, dass ich damit was zu tun hatte war auf meiner Technikerschule 2004. Und da haben wir auch nicht wirklich die Fehlersuche geübt.