PRB: DHCP May Fail When TCP/IP Is Bound First to RAS

 Last reviewed: March 26, 1997
Article ID: Q142311
The information in this article applies to: 

  - Microsoft Windows NT Server versions 3.5 and 3.51
  • Microsoft Windows NT Server version 4.0

    SYMPTOMS

    A DHCP server may fail to lease addresses or renew leases to DHCP clients after a period of time when TCP/IP is bound first to RAS.

    CAUSE

    When the binding order of "Microsoft DHCP Server" places the RAS binding (Remote Access WAN Wrapper) ahead of the NIC binding, and the RAS TCP/IP address is 0.0.0.0, network client DHCP packets intended for the DHCP server are ignored.

    In addition, the Event Viewer may log the the following system error: 

       Event ID 4281, Source WINS, Description:
   "The machine you are running the WINS server on does not have a valid
   address."
    When WINS requested the system for the address, it got 0.0.0.0 as the address.

    NOTE: WINS binds to the first adapter in a machine with more than one adapter bound to TCP/IP. Check the binding order of adapters and make sure the first one has a valid IP address for the WINS server.

    STATUS

    This behavior is by design.

    • Additional query words:
    Keywords : kbnetwork NTSrv nttcp
    Version : 3.5 3.51 4.0
    Platform : WinNT
    Issue type : kbprb

    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.