Node Type And Scope ID Not Updated Upon Lease Renewal

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

SYMPTOMS

When the DHCP lease of your Windows 95 or Windows for Workgroups 3.11 computer is released and renewed, the node type and scope ID are not updated. For example, when you release the lease, make changes to the Node Type and Scope ID information and renew the lease with the IPCONFIG /RENEW (or WINIPCFG /RENEW for Windows 95) command, the new lease does not include the updated Node Type and Scope ID.

RESOLUTION

To work around this problem, reboot your Windows 95 or Windows for Workgroups 3.11 computer.

STATUS

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

KBCategory: kbnetwork
KBSubcategory: ntinterop nttcp
Additional reference words: prodtcp32 3.11 95 TCP/IP wfw win95



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.