TCP/IP-32 Client Cannot Obtain DHCP Lease

 Last reviewed: September 9, 1996
Article ID: Q125514
The information in this article applies to:
  • Microsoft Windows NT Server version 3.5
  • Microsoft TCP/IP-32 for Windows for Workgroups, version 3.11a
  • Microsoft Windows for Workgroups version 3.11

SUMMARY

A Microsoft Windows for Workgroups client using Microsoft TCP/IP-32 Dynamic Host Configuration Protocol (DHCP) on the same network segment as a Microsoft Windows NT 3.5 DHCP Server may not be able to obtain an IP address lease if the DHCP server is incorrectly configured.

MORE INFORMATION

If the DHCP server is assigned a Class B IP address, it must also have its DHCP scope configured for Class B addresses or it will not respond with an offer message when it receives a discover message from a DHCP client.

Example

A DHCP server is assigned a Class B IP address. However, it is configured to lease DHCP clients Class C IP addresses, that is, its DHCP scope is configured as Class C. Because the DHCP client is on the same segment, its discover message is not routed and thus the giaddr field is not modified by an RFC 1542 compliant router. Noticing that the giaddr field has not been modified, the server assumes the client is on the same subnet and uses its own IP information (IP address and subnet mask) for its DHCP offer message.

KBCategory: kbnetwork kbenv
KBSubcategory: nttcp ntconfig
Additional reference words: prodtcp32 prodtcp 3.11 wfw wfwg 3.50 TCP/IP
fail



THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: September 9, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.