| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
DHCP Overview of Client and Server Responsibilities (Page 1 of 2) DHCP is the newest and most current TCP/IP host configuration protocol. However, as we saw in its overview, it wasn't built from scratchit was designed as an extension of the Boot Protocol. In many ways, DHCP is like BOOTP with more, and this can be seen in the basic setup of the protocol and how it works. Both BOOTP and DHCP are designed based on the common TCP/IP model of client/server operation. In any interaction, one device plays the role of client and the other server. Each has specific responsibilities and must send and receive messages following the protocol described in the DHCP standard. The difference is that where BOOTP involves relatively little work for servers and clients and uses a simple single-message exchange for communication, DHCP requires that both servers and clients do more, and uses several types of message exchanges. A DHCP server is a network device that has been programmed to provide DHCP services to clients. The server plays a central role in DHCP because DHCP's main function is host configuration, and the server is what configures hosts (clients) that communicate with it. On smaller networks there may be only a single server to support many clients, while larger networks may use multiple servers; regardless of the number of servers, each will usually service many clients. The following are the key responsibilities of servers in making DHCP work:
Home - Table Of Contents - Contact Us The TCP/IP Guide (http://www.TCPIPGuide.com) Version 3.0 - Version Date: September 20, 2005 © Copyright 2001-2005 Charles M. Kozierok. All Rights Reserved. Not responsible for any loss resulting from the use of this site. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||