Article ID: 297847 - Last Review: October 11, 2007 - Revision: 4.4 Dynamic Host Configuration Protocol server management issues in Windows 2000 and in Windows Server 2003This article was previously published under Q297847 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:
256986
(http://support.microsoft.com/kb/256986/EN-US/
)
Description of the Microsoft Windows Registry
On This PageSYMPTOMS
The following problems are fixed in Microsoft Windows 2000 Service Pack 2 (SP2)and in Microsoft Windows Server 2003:
RESOLUTIONNo More Than Approximately 850 Dynamic Host Configuration Protocol Servers Can Be Authorized in Active DirectoryIn a Windows 2000 domain, DHCP servers must be authorized in Active Directory before those DHCP servers can service DHCP Clients. In versions of Windows 2000 that are earlier than Windows 2000 SP2, only approximately 850 DHCP servers can be authorized in Active Directory. This is a per-forest limitation. After the limit on the number of DHCP servers is reached, you may receive the following error message:
Administration limit for this request has exceeded
The Active Directory Query Interval Is Not ConfigurableWith versions of Windows 2000 that are earlier than Windows 2000 SP2, a DHCP server verifies authorization status with Active Directory when the DHCP server is started, and approximately every 60 minutes after that. If the server does not pass authentication, the server retries every five minutes. You can use the following steps to modify the DHCP Active Directory authorization check interval:
The DHCP Authorization Process Occurs Frequently or, in Some Cases, Occurs Too Often, Which Causes Server Performance ProblemsIn versions of Windows 2000 that are earlier than Windows 2000 SP2, the Active Directory querying process is inefficient. The Active Directory querying process can consume up to 1 megabyte (MB) of network bandwidth for each DHCP server if you have approximately 800 authorized DHCP servers. This process can consume most of the network bandwidth if you are connected over a slow wide area network (WAN) link.The Active Directory querying process has been optimized in Windows 2000 SP2, which results in about 10 packets for each authorized server regardless of the number of authorized DHCP servers. Also, a registry entry is added to disable the Rogue Detection feature. To disable the Rogue Detection feature:
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows 2000 Service Pack 2. APPLIES TO
| Article Translations
|
Back to the top
