DHCP Seconds Field Limits Forwarding of Packets by Relay Agents

 Last reviewed: April 4, 1997
Article ID: Q130929
The information in this article applies to:
  • Microsoft Windows NT Workstation version 3.51
  • Microsoft Windows NT Server version 3.51
  • Microsoft Windows NT Server version 4.0
  • Microsoft Windows NT Workstation version 4.0

In Windows NT 3.51, Dynamic Host Configuration Protocol (DHCP) clients set the seconds field in the DHCP message to zero in the initial DHCP packet. This field is incremented for every subsequent DHCP packet retransmitted by the client.

The DHCP relay agents may be configured with a non-zero threshold value for the seconds field (a value of 4 is recommended). This prevents relay agents from forwarding all DHCP packets with the seconds field set to a value less than the threshold value. If there is a DHCP server in the local subnet that has an available address for lease, it will respond to the initial DHCP packet. The client then does not have to retransmit that DHCP packet with a higher number in the seconds field which will be forwarded by the relay agent. This considerably reduces the number of DHCP packets forwarded to other subnets by the relay agent.

Additional query words: prodnt prodnt wins tcpip
Keywords : kbnetwork NTSrvWkst nttcp
Version : 3.51 4.0
Platform : WINDOWS

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