DHCP Scope Exceptions

Last reviewed: December 18, 1997
Article ID: Q133214

The information in this article applies to:

Microsoft Windows NT Workstation versions 3.5, 3.51, and 4.0
Microsoft Windows NT Server versions 3.5, 3.51, and 4.0

If a DHCP Client is unable to obtain a lease from a DHCP Server, verify that the scope defined for the server does not include 0 or 255 for the host ID portion of the address.

For example, if you are using 100.25.1.0 as your network ID, then the last octet would identify your hosts. So both of the following IP IP addresses would be invalid: 100.25.1.0 and 100.25.1.255.

These addresses are illegal and cause irregular behavior in an environment where they can be leased.

Additional query words: prodnt
Keywords : NTSrvWkst nttcp kbnetwork
Version : 3.5 3.51 4.0
Platform : winnt

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: December 18, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.