Thông báo lỗi như thế này: event 5774
"The dynamic registration of the DNS record '_ldap._tcp.pdc._msdcs.anthaifood.com.vn. 600 IN SRV 0 100 389 atf02.anthaifood.com.vn.' failed on the following DNS server:
DNS server IP address: 205.209.96.207
Returned Response Code (RCODE): 5
Returned Status Code: 9017
For computers and users to locate this domain controller, this record must be registered in DNS.
USER ACTION
Determine what might have caused this failure, resolve the problem, and initiate registration of the DNS records by the domain controller. To determine what might have caused this failure, run DCDiag.exe. You can find this program on the Windows Server 2003 installation CD in Support\Tools\support.cab. To learn more about DCDiag.exe, see Help and Support Center. To initiate registration of the DNS records by this domain controller, run 'nltest.exe /dsregdns' from the command prompt on the domain controller or restart Net Logon service. Nltest.exe is available in the Microsoft Windows Server Resource Kit CD.
Or, you can manually add this record to DNS, but it is not recommended.
ADDITIONAL DATA
Error Value: DNS bad key.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp."
Hỏi pa'c Bill thì pa'c trả lời như thế này: "A common cause for these errors is that a domain controller references itself as a primary DNS server in its TCP/IP properties. When the domain controller starts in this configuration, the Netlogon service may start before the DNS service starts. Because the Netlogon service must register records in DNS and the DNS service is not yet available, errors may occur. In this situation, you can safely ignore the errors because the Netlogon service will again try to register the records in approximately five minutes, at which time it will be successful."
Hiện tại thì server mình có chức năng như pa'c Bill đã nói và mình cũng làm theo hướng dẫn như thế này:
"However, there are two ways to avoid the errors in this scenario:
• Make sure that domain controllers do not reference themselves as a primary DNS server in their TCP/IP properties.
• Configure the Netlogon service to depend on the DNS service. This will cause the Netlogon service to start after the DNS service starts. To do this, run REGEDT32, and go to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Netlogon
In the right pane, double-click the value DependOnService and add DNS to the next available blank line. Click OK and exit Registry Editor."
Chưa giải quyết được theo cách 2
1 nhận xét:
nhận xétcũng bị tình trạng như bạn
Replykhác ip ko biết nguyên nhân do đâu