DHCP Clients Unable to Log On After Changing IP Address Class

 Last reviewed: March 26, 1997
Article ID: Q139276
The information in this article applies to:
  • Microsoft Windows NT Server version 3.51
  • Microsoft Windows NT Server version 4.0

SYMPTOMS

If you deactivate the current DHCP scope, add a new scope of a different IP address class, and the DHCP-enabled clients use only the TCP/IP protocol, client computers such as the following are unable to obtain IP addresses and log on to the network:

  • Windows for Workgroups 3.11
  • Microsoft Network Client for MS-DOS, version 3.0
  • LAN Manager 2.2c are

WORKAROUND

To resolve this problem, install the fix mentioned below.

To work around this problem, delete the current DHCP scope in DHCP Manager before you add a new scope.

STATUS

Microsoft has confirmed this to be a problem in Windows NT Server versions 3.5, 3.51, and 4.0. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available. This problem was corrected in the latest U.S. Service Pack for Windows NT Workstation or Server version 3.51. For information on obtaining this update, query on the following word in the Microsoft Knowledge Base (without the spaces): 

   S E R V P A C K  00

Keywords : kbnetwork nttcp
Version : 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: March 26, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.