TCP/IP-32 3.11b Client Fails to Obtain Reserved DHCP Address

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

SYMPTOMS

Your computer running Windows for Workgroups 3.11 with TCP/IP-32 for Windows for Workgroups version 3.11b installed fails to obtain a reserved DHCP address from the Windows NT DHCP server. Instead, it obtains a dynamic DHCP address.

This problem occurs on a token ring network.

Windows for Workgroups clients do not experience this problem if they are running the following configuration:

  • The client has TCP/IP-32 3.11a installed and is on a token ring network.
  • The client has TCP/IP-32 3.11b installed and is on an ethernet network.

RESOLUTION

To resolve this problem, upgrade the server to Windows NT 3.51.

Windows NT 3.51 DHCP server works properly with TCP/IP-32 3.11a and 3.11b clients.

KBCategory: kbnetwork
KBSubcategory: nttcp NTSrvWkst
Additional reference words: prodnt 3.11 3.11b 3.50 dchp token-ring
tokenring

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 5, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.