Select the product you need help with

Overloaded DHCP Server Stops Functioning with Limited Queue Size

Article ID: 241223

This article was previously published under Q241223

SYMPTOMS

When you are running the Microsoft Dynamic Host Configuration Protocol (DHCP) server service on a computer running Windows NT 4.0, and your DHCP server experiences high network traffic levels, or the DHCP reservation database becomes too large, the DHCP service may not function properly and the computer may stop responding (hang).

Back to the top | Give Feedback

CAUSE

This behavior can occur because there is no queue limit size in Windows NT 4.0 Server. When the DHCP server reaches a critical section timeout, the service stops responding to DHCP packets.

Back to the top | Give Feedback

RESOLUTION

Windows NT Server or Workstation 4.0

To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:

Windows Service Pack Center
(http://windows.microsoft.com/en-US/windows/downloads/service-packs)
-or-
152734
(http://support.microsoft.com/kb/152734/EN-US/ )
how to obtain the latest windows nt 4.0 service pack

For information on obtaining the individual software update, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

(http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS)

Windows NT Server 4.0, Terminal Server Edition

To resolve this problem, obtain the latest service pack for Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

152734

(http://support.microsoft.com/kb/152734/EN-US/ )

How to Obtain the Latest Windows NT 4.0 Service Pack

Back to the top | Give Feedback

STATUS

Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition.

This problem was first corrected in Windows NT Server 4.0 Service Pack 6 and Windows NT Server 4.0, Terminal Server Edition Service Pack 6.

Back to the top | Give Feedback