Article ID: 219308 - View products that this article applies to.
This article was previously published under Q219308
This article has been archived. It is offered "as is" and will no longer be updated.
When you have a computer running Windows NT 4.0 Server using Dynamic Host Configuration Protocol (DHCP), computers on your network may not be able to obtain a lease.
In addition, computers configured as DHCP clients that have already obtained a lease may not function properly.
This behavior occurs when you create a DHCP scope using DHCP Manager, and specify a class D TCP/IP address (multicast group address). DHCP scopes cannot contain class D TCP/IP multicast addresses.
To resolve this problem, obtain the latest service pack for Windows NT 4.0. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/152734/EN-US/ )How to Obtainthe Latest Windows NT 4.0 Service Pack
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows NT 4.0 Service Pack 5.
In the TCP/IP address space, class D addresses are reserved for multicast groups. The address range is 184.108.40.206 to 220.127.116.11. Class D addresses are not segregated into network and host units. Some class D multicast groups are reserved.
For additional information about DHCP, scopes, and multicasting, please refer to the following Request for Comment (RFC) documents:
Dynamic RFC1541: Host Control Protocol
RFC1112: Host Extensions for IP MulticastingMicrosoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
Article ID: 219308 - Last Review: October 14, 2013 - Revision: 1.2