Article ID: 299363 - View products that this article applies to.
This article was previously published under Q299363
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/256986/EN-US/ )Description of the Microsoft Windows Registry
After you install Service Pack 2 (SP2) on either your Windows 2000-based Service Pack 1 (SP1) Remote Installation Services (RIS) server or on your stand-alone Dynamic Host Configuration Protocol (DHCP) server (that does not have RIS installed), you may receive the following event message when you restart the server:
Event ID: 1051
The DHCP/BINL service has determined that it is not authorized to service clients on this network for the Windows domain: Yourdomainname.com
This problem can occur because either the RIS or DHCP server is not authorized in your Active Directory.
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
To resolve this problem, re-authorize your Windows 2000-based RIS server in your Active Directory:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
With RIS servers, the event ID 1051 has only been observed when you update a Windows 2000-based RIS server with SP1.
For additional information about the DisableRogueDetection registry value with DHCP servers and Windows 2000 SP2, click the article number below to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/297847/EN-US/ )Dynamic Host Configuration Protocol Server Management Issues in Windows 2000