ازمحضرجناب google لازم نبود استفاده کنید، ازمحضرجناب Microsoft استفاده میکردید
کد:
http://support.microsoft.com/kb/311354/en-us
This issue can be caused by stale entries in the DNS zone for the old domain that the domain controller belonged to. DNS Event 4007 indicates a DNS configuration problem. The DNS server service uses Active Directory to store DNS data, and it encountered a Lightweight Directory Access Protocol (LDAP) error that is associated with this zone. This problem can appear for zones that have a registry reference but that are not stored in the ForestDnsZones or the DomainDnsZones application partition of the new domain.
To resolve this issue:
- Stop the Netlogon service.
- Rename the Netlogon.dns file to Netlogon.old, and then rename the Netlogon.dnb file to Netlogon.old2.
Note Netlogon.dns and Netlogon.dnb are located in the Windows\System32\Config folder. - Start the Netlogon service or restart your computer.
To prevent the DNS Event 4007 errors from occurring, perform one of the following steps:
- If they exist, manually remove forward lookup zones that still appear in DNS manager that are not associated with the current Active Directory domain, and then restart DNS.
- In most cases, Event ID 4007 is resolved by removing from the registry the DNS zone that is indicated in the error when it no longer exists in Active Directory. The zone information is usually left in the registry when the DC previously hosted another zone, was demoted, and then was re-promoted to host a new zone. The location in the registry to remove the problem zone when it does not exist in AD is as follows: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\DNS Server\Zones
During the demotion of the domain controller, Dcpromo.exe might not be able to de-register all of the Netlogon service records at the DNS server, which hosts the domain controller's domain.
LinkBack URL
About LinkBacks
نوشته اصلی توسط patris1
