Active Directory DC Hangs when lmcompatibility is set 4
- From: Jay <Jay@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 12 Jun 2007 16:15:00 -0700
Hello,
I have this nagging issue regarding my two ADDC's. If I set the
lmcompatibility level (Network Security: Lan Manager authentication level) to
anything higher than 3, either in the registry or through group policy, the
ADDC hangs after reboot. The DC would hang at "Preparing Network Connections"
for about a good 45 minutes before a pop up windows appears saying that "...a
service failed to start."
I did more digging since I am able to replicate the problem after restoring
the system back to a setting of 3 and found the following in the event logs?
DIRECTORY SERVICE EVENT LOGS:
Event Type: Information
Event Source: NTDS General
Event Category: Service Control
Event ID: 1000
Date: 6/12/2007
Time: 8:32:50 AM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: DC03
Description:
Microsoft Active Directory startup complete, version 5.2.3790.1830
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Event Type: Error
Event Source: NTDS Backup
Event Category: Backup
Event ID: 1913
Date: 6/12/2007
Time: 8:35:50 AM
User: N/A
Computer: DC03
Description:
Internal error: The Active Directory backup and restore operation
encountered an unexpected error.
Backup or restore will not succeed until this is corrected.
Additional Data
Error value:
1062 The service has not been started.
Internal ID:
160200fa
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Event Type: Error
Event Source: NTDS General
Event Category: Global Catalog
Event ID: 1126
Date: 6/12/2007
Time: 8:47:50 AM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: DC03
Description:
Active Directory was unable to establish a connection with the global
catalog.
Additional Data
Error value:
1792 An attempt was made to logon, but the network logon service was not
started.
Internal ID:
3200cd1
User Action:
Make sure a global catalog is available in the forest, and is reachable from
this domain controller. You may use the nltest utility to diagnose this
problem.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Event Type: Information
Event Source: NTDS Replication
Event Category: Replication
Event ID: 1555
Date: 6/12/2007
Time: 9:03:20 AM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: DC03
Description:
The local domain controller will not be advertised by the domain controller
locator service as an available domain controller until it has completed an
initial synchronization of each writeable directory partition that it holds.
At this time, these initial synchronizations have not been completed.
The synchronizations will continue.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
DNS EVENT LOGS:
Event Type: Warning
Event Source: DNS
Event Category: None
Event ID: 4013
Date: 6/12/2007
Time: 8:07:04 AM
User: N/A
Computer: DC03
Description:
The DNS server was unable to open the Active Directory. This DNS server is
configured to use directory service information and can not operate without
access to the directory. The DNS server will wait for the directory to
start. If the DNS server is started but the appropriate event has not been
logged, then the DNS server is still waiting for the directory to start.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: f5 25 00 00 õ%..
SYSTEM EVENT LOGS:
Event Type: Error
Event Source: Distributed Link Tracking Server
Event Category: None
Event ID: 12502
Date: 6/12/2007
Time: 7:52:46 AM
User: N/A
Computer: PDC03
Description:
Service failed to start. Error = 80070862
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10010
Date: 6/12/2007
Time: 7:56:17 AM
User: N/A
Computer: DC03
Description:
The server {73E709EA-5D93-4B2E-BBB0-99B7938DA9E4} did not register with DCOM
within the required timeout.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
SECURITY EVENT LOGS:
Nothing in the security event logs to indicate any authentication issues.
.
- Prev by Date: Re: dcpromo failed
- Next by Date: Re: USERENV error - Group Policy
- Previous by thread: Re: Changing DNS entry in an AD Computer Account
- Next by thread: Import Groups into Active Directory
- Index(es):
Relevant Pages
|
