Microsoft KB Archive/177824

= DHCP Client Is Assigned Subnet Broadcast Address =

Article ID: 177824

Article Last Modified on 10/31/2006

-

APPLIES TO


 * Microsoft Windows NT Workstation 4.0 Developer Edition
 * Microsoft Windows NT Server 4.0 Standard Edition

-



This article was previously published under Q177824



SYMPTOMS
One or more of your Dynamic Host Control Protocol (DHCP) clients may experience problems communicating on the network using TCP/IP. These problems may include one or more of the following:


 * The inability to successfully ping other TCP/IP hosts.

-or-
 * The inability to resolve NetBIOS or Host names of other TCP/IP hosts.



CAUSE
Your DHCP server may have assigned the client a subnet broadcast address instead of a valid IP address.



RESOLUTION
To resolve this issue, use one of the following:


 * When creating scopes, do not include the subnet broadcast address. For example:

Creating a scope of 192.168.1.1-255 with Mask 255.255.255.0 may result in a DHCP client being offered the 192.168.1.255 address, which is the subnet broadcast address. Instead, you should create the scope 192.168.1.1-254 with Mask 255.255.255.0.

-or-
 * To modify an existing scope, create an exclusion for the subnet broadcast address.

For additional information, please see the following article in the Microsoft Knowledge Base:

ARTICLE-ID: 164015

TITLE : Understanding TCP/IP Addressing and Subnetting Basics



STATUS
Microsoft has confirmed this to be a problem in Windows NT version 4.0. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Keywords: kbbug kbinterop kbnetwork KB177824

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.