|
Question : Domain Controller Issues at boot up however network is operating correct after boot
|
|
I have two domain controller svr-01 and svr-03 and I am having various error occuring on reboot of svr-01. Once the machine are running there does not seem to be any problems. Below are some of the errors:
Event Type: Error Event Source: DfsSvc Event Category: None Event ID: 14523 Date: 13/04/2006 Time: 7:33:48 a.m. User: N/A Computer: SVR-01 Description: DFS could not contact any DC for Domain DFS operations. This operation will be retried periodically.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. -------------------------------------------------------------------------------------------------------------------------------------------- Event Type: Error Event Source: NetBT Event Category: None Event ID: 4321 Date: 13/04/2006 Time: 7:33:52 a.m. User: N/A Computer: SVR-01 Description: The name "KEYLOGIX :1d" could not be registered on the Interface with IP address 10.1.1.1. The machine with the IP address 10.1.1.3 did not allow the name to be claimed by this machine.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 00 00 00 00 04 00 56 00 ......V. 0008: 00 00 00 00 e1 10 00 c0 ....á..À 0010: 01 01 00 00 01 00 00 c0 .......À 0018: 00 00 00 00 00 00 00 00 ........ 0020: 00 00 00 00 00 00 00 00 ........ -------------------------------------------------------------------------------------------------------------------------------------------- Event Type: Error Event Source: CertSvc Event Category: None Event ID: 44 Date: 13/04/2006 Time: 7:34:18 a.m. User: N/A Computer: SVR-01 Description: The "Windows default" Policy Module "Initialize" method returned an error. The specified domain either does not exist or could not be contacted. The returned status code is 0x8007054b (1355). The Active Directory containing the Certification Authority could not be contacted.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. -------------------------------------------------------------------------------------------------------------------------------------------- Event Type: Warning Event Source: NTDS Replication Event Category: DS RPC Client Event ID: 2088 Date: 13/04/2006 Time: 7:34:54 a.m. User: NT AUTHORITY\ANONYMOUS LOGON Computer: SVR-01 Description: Active Directory could not use DNS to resolve the IP address of the source domain controller listed below. To maintain the consistency of Security groups, group policy, users and computers and their passwords, Active Directory successfully replicated using the NetBIOS or fully qualified computer name of the source domain controller.
Invalid DNS configuration may be affecting other essential operations on member computers, domain controllers or application servers in this Active Directory forest, including logon authentication or access to network resources.
You should immediately resolve this DNS configuration error so that this domain controller can resolve the IP address of the source domain controller using DNS.
Alternate server name: svr-03 Failing DNS host name: 8a6a6d58-8dfc-4940-90ba-51f8f2cb2467._msdcs.keylogix.local
NOTE: By default, only up to 10 DNS failures are shown for any given 12 hour period, even if more than 10 failures occur. To log all individual failure events, set the following diagnostics registry value to 1:
Registry Path: HKLM\System\CurrentControlSet\Services\NTDS\Diagnostics\22 DS RPC Client
User Action:
1) If the source domain controller is no longer functioning or its operating system has been reinstalled with a different computer name or NTDSDSA object GUID, remove the source domain controller's metadata with ntdsutil.exe, using the steps outlined in MSKB article 216498.
2) Confirm that the source domain controller is running Active directory and is accessible on the network by typing "net view \\
|
|
Answer : Domain Controller Issues at boot up however network is operating correct after boot
|
|
I understand.
The DHCP error is not an error at all - so you can ignore that.
The KDC error is normally fixed by the installation of KB812499, but that's for 2000 and thus why I asked if this was an upgrade. If that key is available, you may want to test the value out.
If domain functionality is good, then monitor it for awhile to see what else may show itself during normal use. Perhaps, save the logs (if you need them) and clear them out so you can watch things better. Do this after the reboot and things settle down.
|
|
|
|