Client's Valid <x>.<x>.<x>.0 Host Address Is Disallowed on the Network (241657)

SYMPTOMS

When a Dynamic Host Control Protocol (DHCP) client is issued an x.x.x.0 address from a DHCP server on which the scope allows for a valid x.x.x.0 address (even though another address may be excluded) and receives the address successfully as an active DHCP client, the DHCP client's network connectivity may not function properly. Error messages may be generated when the DHCP client, or other network resources or services, attempt to establish a network connection.

You may see the following error message when other network resources or services try to communicate across the network with the DHCP client:

Destination specified is invalid

You may see the following error message when the DHCP client attempts to establish a connection with other network resources:

Request timed out

CAUSE

Although the DHCP client receives the address from the DHCP server, the address it receives is viewed as a "network address" instead of a client address on the network. The use of the x.x.x.0 address is disallowed as a client address even though it is a valid host address.

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:

http://www.microsoft.com/windows/servicepacks/ -or-
152734how 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/directory/overview.asp

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 How to Obtain the Latest Windows NT 4.0 Service Pack

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.

MORE INFORMATION

For additional information about DHCP, scopes, and TCP/IP addressing and subnetting, please refer to the following Request for Comment (RFC) documents:

950: Internet Standard Subnetting Procedure
1918: Address Allocation for Private Internets
2131: Dynamic Host Configuration Protocol
2151: A Primer on Internet and TCP/IP Tools and Utilities
1180: A TCP/IP Tutorial
1219: On the Assignment of Subnet Numbers

For information about obtaining RFCs, please see the following article in the Microsoft Knowledge Base:

185262How to Obtain Request for Comments Documents from the Internet