Typically, the reason for recording these error messages is that the NetLogon service does not receive a "Success" message from the DNS server that has a registered log area. The Netlogon service has not received the "Success" message with the following:
•
Domain Controller Configuration: The DNS server item in the Domain Controller Transfer Control Protocol / Internet Protocol (TCP / IP) property is not configured correctly.
•
Connection: This domain controller does not exist between the Internet Protocol (IP) Connection or Transmission Control Protocol / User Dataset Protocol (TCP / UDP) connection between the DNS server that has these records to register or unregistered in it.
•
DNS Server Configuration: As mentioned in the Request for Comments 2136 specification, the DNS server cannot accept dynamic updates or are not configured to accept dynamic updates. If the DNS server used by the domain controller does not have authority for the Netlogon service attempt to register or unregister, the DNS server must be able to provide an IP address of the affected area with the authoritative DNS server for the affected area. .
Netlogon 5774
When the NetLogon service on the domain controller cannot register a separate resource record, NetLogon 5774 error message will be recorded in the system event log. This event describes the name of the resource record and other DNS parameters used when trying to register, for example:
Event Type: ErroorEvent Source: Netlogonevent Category: NoneEvent ID: 5774DATE:
2/2/2000
Time: 8: 27: 03 PMuser: N / AComputer: Computer10Description: registration of the dns record 'corp.computer.com.
600 in
A 192.168.4.1 'Failed with The Following Error: DNS Server Unable to Interpret Format.data:0000: 29 23 00 00) # ..
Netlogon 5775
When the NetLogon service on the domain controller cannot unable to cancel the individual resource records, NetLogon 5775 error messages will be recorded in the system event log. The event description contains the name of the resource record and attempts to cancel the other DNS parameters used in registration, for example:
Event Type: ErroorEvent Source: Netlogonevent Category: NoneEvent ID: 5775Date:
3/2/2000
Time: 6: 13: 09 PMuser: N / Acomputer: Computer10Description: derec._msdcs.computer.com.
600 in
A 192.168.4.1 'Failed with the folowing error: DNS Bad key.data:0000: 39 23 00 00 9 # ..
For other troubleshooting steps, check the TCP / IP TROUBLESHOOTING (TCP / IP Troubleshooting) in Windows 2000 Online Resource Kit (TCP / IP Cry Networking Guide), location is: http: // www .microsoft.com / Windows2000 / TechInfo / Reskit / Samplechapters
Netlogon 5781
Netlogon 5781 error messages will be recorded in the system event log when Netlogon service on the domain controller cannot register or unregister multiple resource records. This event description does not contain the name of these resource records. In addition, this event description may also be a "NO DNS Servers Are Available", for example: Event Type: WarNingEvent Source: NetLogonevent Category: NoneEvent ID: 5781DATE:
3/2/2000
Time: 4: 29: 12 PMuser: N / Acomputer: Computer10Description: Dynamic Registration or derecords of one or more DNS RECORDS FAILED BECAUSE NO DNS Servers Are Available.Data:0000: B4 05 00 00 '...
WARNING: If you use improper use of the registry editor, you may need to reinstall the operating system. Microsoft does not guarantee that you can solve problems caused by improper use of registry editors. Use Registry Editor at your own risk. Note: Common causes of these errors are that the domain controller is a primary DNS server in its TCP / IP attribute. When the domain controller is activated using this configuration, the NetLogon service may start before the DNS service is started. Since the Netlogon service must register a record in DNS, the DNS service is not available, so an error may occur. In this case, you can safely ignore these errors because the Netlogon service will try to register these records again after approximately 5 minutes, and will be able to register successfully. However, in this case, there are two ways to avoid these errors:
•
Make sure the domain controller does not reference its own reference as a main DNS server in its TCP / IP property.
•
Configure Netlogon services to make it depend on DNS service. This will cause the Netlogon service to start after the DNS service is started. To do this, run the regedt32 and go to:
HKEY_LOCAL_MACHINE / SYSTEM / CURRENTCONTROLSET / SERVICES / NETLOGON
In the right pane, double-click the DependOndOnService value and add DNS to the next available blank line. Click OK to exit the Registry Editor. For additional information, click the article number below to see the article in the Microsoft Knowledge Base:
193888 How to postpone a specific service
