Windows Server TechCenter> Windows Server 2003 Technical Library> Windows Server 2003: Technical Reference>
Windows Server 2003 Technical Reference> Technologies Collections> Networking Collection>
Network Configuration Technologies> DHCP Technical Reference
DHCP provides an automated way to distribute and update IP addresses and other configuration information on a network. A DHCP server provides this information to a DHCP client through the exchange of a series of messages, known as the DHCP conversation or the DHCP transaction. If the DHCP server and DHCP clients are located on different subnets, a DHCP relay agent is used to facilitate the conversation.
A DHCP client is any network-enabled device that supports the ability to communicate with a DHCP server in compliance with RFC 2131, for the purpose of obtaining dynamic leased IP configuration and related optional information.
\u2022DHCP Processes and Interactions
\u2022Windows NT version 4.0
DHCP supports Automatic Private IP Addressing (APIPA), which enables computers running Windows 2000,
Windows XP, and Windows Server 2003 to configure an IP address and subnet mask if a DHCP server is
unavailable at system startup and the Automatic private IP address Alternate Configuration setting is selected.
This feature is useful for clients on small private networks, such as a small-business office or a home office.
If the DHCP client obtained a lease from a DHCP server on a previous occasion, and the lease is still valid (not expired) at system startup, the client tries to renew its lease. If, during the renewal attempt, the client fails to locate any DHCP server, it attempts to ping the default gateway listed in the lease, and proceeds in one of the following ways:
Windows Server 2003 DHCP supports local storage, which allows clients to store DHCP information on their own hard disks. Local storage is useful because it enables the client to store its last leased IP address, so that when the client starts it first attempts to renew the lease of its previous IP address. Local storage also enables a client to be shut down and restarted and it will use its previously leased address and configuration, even if the DHCP server is unreachable or offline at the time that the client computer is restarted.
\u2022Windows Server 2003
\u2022Windows Millennium Edition
If Automatic private IP address is selected, the DHCP client auto-configures its IP address and subnet
mask by using a selected address from the Microsoft-reserved Class B network, 169.254.0.0, with the
subnet mask 255.255.0.0. The DHCP client tests for an address conflict to ensure that the IP address is not
in use on the network. If a conflict is found, the client selects another IP address. The client retries auto-
configuration up to 10 times.
If User Configured is selected, the DHCP client configures a static IP address configuration. The DHCP client tests for an address conflict to ensure that the IP address is not already in use on the network. If a conflict is found, the DHCP client indicates the error condition to the user.
3. When the DHCP client succeeds in self-selecting an address, it configures its network interface with the IP
address. The client then continues to check for a DHCP server in the background every five minutes. If a
DHCP server responds, the DHCP client abandons its self-selected IP address and uses the address offered
by the DHCP server (and any other DHCP option information that the server provides) to update its IP
\u2022If the ping is successful, the DHCP client assumes that it is still located on the same network where it
obtained its current lease, and continues to use the lease as long as the lease is still valid. By default the
client then attempts, in the background, to renew its lease when 50 percent of its assigned lease time has
A scope must be properly defined and activated before DHCP clients can use the DHCP server for automatic
TCP/IP configuration. A DHCP scope is an administrative collection of IP addresses and TCP/IP configuration
parameters that are available for lease to DHCP clients of a specific subnet. The network administrator creates a
scope for each subnet.
When a scope is created, the lease duration is set to eight days by default. However there are situations when the administrator might want to change the lease duration. The following are examples of adjusting the lease duration due to individual network consideration:
For example, consider the ratio between connected computers and available IP addresses. If 40 computers share
254 available addresses, the demand for reusing addresses is low. A long lease time, such as a few months, might
be appropriate in such a situation. However, if 230 computers must share the same address pool, demand for
available addresses is greater, and a shorter lease time, for example a few days, is more appropriate.
When you create a new scope, immediately exclude the addresses of existing statically configured computers from
the scope. By using exclusion ranges, you can exclude specific IP address ranges within a scope so that those
addresses are not offered to clients. Assign IP addresses within exclusion ranges to computers or devices that
\u2022A scope name, assigned when the scope is created.
\u2022A range of possible IP addresses from which to include or exclude addresses used in DHCP lease offers.
\u2022A unique subnet mask, which determines the network ID for an IP address in the scope.
\u2022Lease duration values.
\u2022An organization has a large number of IP addresses available and configurations that rarely change. The administrator increases the lease duration to reduce the frequency of lease renewal exchanges between clients and the DHCP server. Because the DHCP clients are renewing their leases less frequently, DHCP- related network traffic is reduced.
caution. Even relatively stable environments have a certain amount of client turnover. At a minimum,
computers might be added and removed, moved from one office to another, or network adapters might be
replaced. If a client with an infinite lease is removed from the network without releasing its lease, the DHCP
server is not notified, and the IP address is not automatically reused. Also, when using an infinite lease,
options set on the DHCP server are not automatically updated on the DHCP client, because the client is
never required to renew its lease and obtain the new options. It is recommended that reservations be used
rather than infinite lease durations.
This action might not be possible to undo. Are you sure you want to continue?