Share via

DHCP: The server should be bound to at least one IP address in the system

Applies To: Windows Server 2008 R2, Windows Server 2012

This topic is intended to address a specific issue identified by a Best Practices Analyzer scan. You should apply the information in this topic only to computers that have had the Dynamic Host Configuration Protocol Best Practices Analyzer run against them and are experiencing the issue addressed by this topic. For more information about best practices and scans, see Best Practices Analyzer (

Operating System

Windows Server® 2008 R2, Windows Server 2012


Dynamic Host Configuration Protocol (DHCP)






This DHCP server is not bound to an IP address.


A server that is not bound to an IP address cannot lease IP addresses, or any other network configuration, to DHCP clients.


Using the DHCP Management Console, add bindings to one or more IP addresses.

You may encounter this error if you don’t have a static IP address assigned to your DHCP server.

By default, the service bindings depend on whether the network connection is configured dynamically or statically for TCP/IP. Based on the method of configuration it uses, reflected by its current settings in Internet Protocol (TCP/IP) properties, the DHCP Server service performs default service bindings as follows:

  • If the first network connection uses a manually specified IP address, the connection is enabled in server bindings. For this to occur, a value for IP address must be configured and the Use the following IP address option selected in Internet Protocol (TCP/IP) properties. In this mode, the DHCP server listens for and provides service to DHCP clients.

  • If the first network connection uses an IP address configured dynamically, the connection is disabled in server bindings. This occurs when the Obtain an IP address automatically option is selected in Internet Protocol (TCP/IP) properties. For computers running Windows Server 2008 R2 operating systems, this is the default setting. In this mode, the DHCP server does not listen for and provide service to DHCP clients until a static IP address is configured.

  • The DHCP server will bind to the first static IP address configured on each adapter.


  • By design, DHCP server bindings are enabled and disabled on a per-connection, not per-address basis. All bindings are based on the first configured IP address for each connection appearing in the Network Connections folder. If additional static IP addresses (for example, as set in Advanced TCP/IP properties) are configured for the applicable connection, these addresses are never used by DHCP servers running Windows Server 2008 R2 and are inconsequential for server bindings.

  • DHCP servers running Windows Server 2008 R2 never bind to any of the NDISWAN or DHCP-enabled interfaces used on the server. These interfaces are not displayed in the DHCP console under the current server bindings list because they are never used for DHCP service. Only additional network connections that have a primary static IP address configured can appear in the server bindings list (or be selectively enabled or disabled there).

  • To perform these procedures, you must be a member of the Administrators group, or the DHCP Administrators group, or you must have been delegated the appropriate authority.

    To Add Bindings

    1. Click Start, click Administrative Tools, and then click DHCP.

    2. In the console tree, right-click the DHCP server to which you want to add bindings.

    3. Click Add/Remove Bindings in Server Binding Properties, select check boxes for any statically configured network connections that should be enabled for use with IPv4 at the applicable DHCP server, or click IPv6 to select check boxes for any statically configured network connections that should be enabled for use with IPv6.

    4. Click OK.

    Additional references

    For updated detailed IT pro information about DHCP and selectively enabling or disabling DHCP server bindings, see the Windows Server 2008 R2 documentation on the Microsoft TechNet Web site.