This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them. Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Summary

The Windows® 2000 Server operating system network includes an
enhanced implementation of Dynamic Host Configuration Protocol (DHCP), an
open, industry standard that reduces the complexity of administering networks based
on TCP/IP. This white paper discusses integrating DHCP with domain
name system (DNS), enhanced monitoring and statistical reporting for
DHCP servers, new vendor-specific options and user-class support, multicast address
allocation, and rogue DHCP server detection--benefits that free administrators up from having to
configure all the computers by hand.

TCP/IP is the global network protocol of choice,
especially for corporate
intranets adopting Internet technology, and each TCP/IP network must be
assigned a unique IP address. However, configuring and administering
TCP/IP network clients has traditionally been time-consuming and costly.
This is why Microsoft, as a member of the Internet Engineering Task Force
(IETF), was an early advocate for having dynamic IP addressing technology
and worked closely with other IETF members to create the Dynamic Host
Configuration Protocol (DHCP) solution, which frees network administrators
from having to configure all of the computers by hand.

DHCP is open and standards-based, as defined by IETF Requests for Comments
(RFCs) 2131 and 2132. DHCP can automatically configure a host while it is
booting on a TCP/IP network, as well as change settings while the host is
attached. This lets all available IP addresses be stored in a central
database along with associated configuration information, such as the
subnet mask, gateways, and address of DNS servers.

DHCP makes life easier for
network administrators--especially on large networks. Without dynamic address assignment,
clients have to be configured one by one. IP addresses must be managed to
avoid duplicate use. Changes must be applied to clients by hand.
Configuration information is not centralized; and it is difficult to get a
view of all client configurations.