Skip to main content This browser is no longer supported. Show
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. DHCP (Dynamic Host Configuration Protocol) Basics
In this articleDynamic Host Configuration Protocol (DHCP) is a standard protocol defined by RFC 1541 (which is superseded by RFC 2131) that allows a server to dynamically distribute IP addressing and configuration information to clients. Normally the DHCP server provides the client with at least this basic information:
More InformationThe following Microsoft products provide DHCP client functionality:
Different DHCP clients support different options that they can receive from the DHCP server. The following Microsoft server operating systems provide DHCP server functionality:
When a client is initialized for the first time after it is configured to receive DHCP information, it initiates a conversation with the server. Below is a summary table of the conversation between client and server, which is followed by a packet-level description of the process:
The detailed conversation between DHCP client and DHCP server is as follows: DHCPDISCOVERThe client sends a DHCPDISCOVER packet. The following is an excerpt from a network monitor capture showing the IP and DHCP portions of a DHCPDISCOVER packet. In the IP section, you can see the Destination address is 255.255.255.255 and the Source address is 0.0.0.0. The DHCP section identifies the packet as a Discover packet and identifies the client in two places using the physical address of the network card. Note the values in the CHADDR field and the DHCP: Client Identifier field are identical.
DHCPOFFERThe DHCP server responds by sending a DHCPOFFER packet. In the IP section of the capture excerpt below, the Source address is now the DHCP server IP address, and the Destination address is the broadcast address 255.255.255.255. The DHCP section identifies the packet as an Offer. The YIADDR field is populated with the IP address the server is offering the client. Note the CHADDR field still contains the physical address of the requesting client. Also, we see in the DHCP Option Field section the various options being sent by the server along with the IP address. In this case the server is sending the Subnet Mask, Default Gateway (Router), Lease Time, WINS server address (NetBIOS Name Service), and the NetBIOS Node Type.
DHCPREQUESTThe client responds to the DHCPOFFER by sending a DHCPREQUEST. In the IP section of the capture below, the Source address of the client is still 0.0.0.0 and the Destination for the packet is still 255.255.255.255. The client retains 0.0.0.0 because the client hasn't received verification from the server that it's okay to start using the address offered. The Destination is still broadcast, because more than one DHCP server may have responded and may be holding a reservation for an Offer made to the client. This lets those other DHCP servers know they can release their offered addresses and return them to their available pools. The DHCP section identifies the packet as a Request and verifies the offered address using the DHCP: Requested Address field. The DHCP: Server Identifier field shows the IP address of the DHCP server offering the lease.
DHCPACKThe DHCP server responds to the DHCPREQUEST with a DHCPACK, thus completing the initialization cycle. The Source address is the DHCP server IP address, and the Destination address is still 255.255.255.255. The YIADDR field contains the client's address, and the CHADDR and DHCP: Client Identifier fields are the physical address of the network card in the requesting client. The DHCP Option section identifies the packet as an ACK.
If the client has previously had a DHCP assigned IP address and it is restarted, the client will specifically request the previously leased IP address in a special DHCPREQUEST packet. The Source address is 0.0.0.0 and the Destination is the broadcast address 255.255.255.255. Microsoft clients will populate the DHCP Option Field DHCP: Requested Address with the previously assigned address. Strictly RFC compliant clients will populate the CIADDR Field with the address requested. The Microsoft DHCP server will accept either.
At this point, the server may or may not respond. The behavior of the Windows NT DHCP server depends on the version of the operating system being used as well as other factors such as superscoping. If the server determines that the client can still use the address, it will either remain silent or ACK the DHCPREQUEST. If the server determines that the client cannot have the address, it will send a NACK.
The client will then begin the discover process, but the DHCPDISCOVER packet will still attempt to lease the same address. In many instances, the client will get the same address but may not.
DHCP information obtained by the client from a DHCP server will have a lease time associated with it. The lease time defines how long the client can use the DHCP-assigned information. When the lease reaches certain milestones, the client will attempt to renew its DHCP information. To view IP information on a Windows or Windows for Workgroups client, use the IPCONFIG utility. If the client is Windows 95, use WINIPCFG. ReferencesFor more information about DHCP, see RFC1541 and RFC2131. RFCs may be obtained via the Internet at numerous sites, for example: http://www.rfc-editor.org/ and http://www.tech-nic.qc.ca/ FeedbackSubmit and view feedback for Which of the following messages is not used during a successful DHCP address assignment?D. Correct: The DHCPINFORM message type is not used during an IP address assignment.
Which of the following DHCP message types in the order in which a successful IP address assignment procedure uses them is correct?Explanation. Assuming all went well with the DHCP discovery process, the correct sequence of DHCP messages exchanged between the server and client is: DHCPDISCOVER -> DHCPOFFER -> DHCPREQUEST -> DHCPACK. A client sends a DHCPDISCOVER message with a source address of 0.0.
Which of the following network components are typically capable of functioning as a DHCP relay agent?Which of the following network components are typically capable of functioning as DHCP relay agents? B. Most IP routers have DHCP relay agent capabilities built into them. If the routers connecting your subnets are so equipped, you can use them as relay agents, eliminating the need for a DHCP server on each subnet.
Which options are methods of providing the DHCP service quizlet?What are the three DHCP allocation methods? a scope for a specified length of time. computer from a scope. Automatic allocation is essentially dynamic allocation with an indefinite lease.
|