Dynamic Host Configuration Protocol (DHCP) is a client-server protocol that automatically assigns an IP address to a host (such as a PC, laptop, or phone) upon request. The activity aims to let learners observe DHCP in action rather than just study the handshake theory. It also introduces some frustration by showing what happens when hosts fail to receive a DHCP IP address, helping learners understand packet movement and where delays may occur in ensuring DHCP functions properly.

Estimated time for completion: 60 minutes

Learning objectives

• Successfully deploy a DHCP solution using Windows on an enterprise network
• Capture and Observe DHCP packets using Wireshark
• Capture and Observe ARP packets using Wireshark
• Successfully add hosts to an enterprise network and receive IP addresses automatically

Prerequisites

• Adding a Virtual Machine to GNS3
• Create a Windows Server
• IPv4 Addressing

Deliverables

• 4 Screenshots:
  • Wireshark – DHCP Packets for PC1
  • Wireshark – DHCP Packets for PC2
  • GNS3 Workspace
  • Configuration of Windows Server

Resources

• Microsoft Learn | DhcpServer Module

Contributors and testers

• Mathew J. Heath Van Horn, PhD, ERAU-Prescott

Phase I -Build the Network Topology

The following steps are to create the baseline for completing the lab. It makes assumptions about the learner’s knowledge from completing previous labs. By the end of this lab, your network should look like the following:

1.   Open GNS3 and create a new project
2. Create the baseline network with an address space of 200.200.200.0/24

   NOTE: This example uses the same network topology created in the previous chapter: DHCP using Linux.

   1. Use two VPCS devices for PC1 and PC2
   2. Add an Ethernet switch
   3. Add a Windows Server VM and rename it to dhcp-server

      NOTE: This lab was tested on Windows Server 2016, but later versions should also work.

   4. Connect the server and PCs to the switch
   5. Label and organize your network as necessary
      

      

1. Start dhcp-server and log in
2. Press Win + R to open the Run dialog

   NOTE: Alternatively, right-click Start and select Run

3. Type ncpa.cpl and press Enter to open the Network Connections window in Control Panel
   

   

4. Right-click Ethernet, then select Properties
   

   

5. Uncheck Internet Protocol Version 6 (TCP/IPv6)
6. Highlight Internet Protocol Version 4 (TCP/IPv4) and click Properties
   

   

7. Select Use the following IP address, then enter the following settings:
   1. IP address: 200.200.200.254
   2. Subnet mask: 255.255.255.0
   3. Default gateway: Leave blank
8. Leave the Preferred DNS server and Alternate DNS server fields blank, since this lab does not use DNS
   

   

9. Click OK to apply these settings and Close to return to the Network Connections window
10. Open a Run dialog, type powershell.exe, then press Enter to start a PowerShell session
11. In PowerShell, verify that the static IP address was applied successfully

    Get-NetIPAddress -InterfaceAlias “Ethernet” | Format-Table IPAddress, PrefixLength

    NOTE: If your interface name is not “Ethernet”, adjust the command accordingly.

    

1. If Server Manager is not already open, open the Run dialog, type servermanager.exe, then press Enter
2. Select Manage in the upper-right corner, then select Add Roles and Features from the drop-down menu
   

   

3. The Add Roles and Features Wizard will open:
   1. Before you Begin – Click Next
   2. Installation Type – Select Role-Based or feature-based installation, then click Next
   3. Server Selection – Select the local machine (this should be the only option), then click Next
   4. Server Roles – Select DHCP Server
      

      

   5. Leave Include management tools selected, then click Add Features
      

      

   6. Features – Click Next
   7. DHCP Server – Click Next
   8. Confirmation – Click Install
4. Open the Post-Install Wizard by selecting Complete DHCP configuration
   

   

   1. Description – Click Commit
   2. Summary – Click Close
5. Return to the Add Rolls and Features Wizard and click Close

1. Launch DHCP Manager by clicking Tools in the upper-right corner, then selecting DHCP from the drop-down menu
   

   

2. In the DHCP console tree, expand the local server, right-click IPv4, then select New Scope
   

   

3. In the New Scope Wizard welcome page, click Next
4. On the Scope Name page, enter a name and optional description for the DHCP scope, then click Next
   

   

5. On the IP Address Range page, enter the following values:
   

   Description	IP Address
   Start IP address	200.200.200.20
   End IP address	200.200.200.200
   Length	24
   Subnet mask	255.255.255.255

   

6. Click Next
7. In Add Exclusions and Delay, click Next
8.  In Lease Duration, leave the default value at 8 days and click Next
9.  On the Configure DHCP Options page, select No, I will configure these options later, and click Next
   

   

10.  Click Finish to exit the New Scope Wizard
11. Under the IPv4 tree, right-click the new scope, and click Activate to enable it
    

    
12. Start a PowerShell session and use the following command to verify the scope is active

    Get-DhcpServerV4Scope -ScopeID “200.200.200.0” | Format-Table Name, State, StartRange, EndRange

    

1. Navigate back to GNS3
2. Start a Wireshark capture on the Server-Switch link
3. Start PC1, open its console, and request a new IP address

   > ip dhcp

4. Notice the four main DHCP packets being exchanged in Wireshark that were discussed in the previous chapter: Discover, Offer, Request, Accept
   

   

5. Repeat for PC2, so it also receives a new address
6. Ensure that PC1 is able to ping PC2 to demonstrate network connectivity

1. Set a static IP address
   $StaticIP = @{
   InterfaceAlias = ‘Ethernet’
   PrefixLength = 24
   IPAddress = ‘200.200.200.254’
   AddressFamily = ‘IPv4’
   }New-NetIPAddress @StaticIP
2. Install the DHCP Server role

   Install-WindowsFeature -Name DHCP -IncludeManagementTools

3. Check the status of the DHCP server

   Get-Service -Name DhcpServer

4. Update the registry to show the DHCP Server role is configured
   $RegUpdate = @{
   Path = ‘HKLM:\SOFTWARE\Microsoft\ServerManager\Roles\12’
   Name = ‘ConfigurationState’
   Value = 2
   }Set-ItemProperty @RegUpdate
5. Restart the service

   Restart-Service -Name DhcpServer

6. Create a new DHCP pool
   $DhcpScope = @{
   Name = ‘blue.net’
   StartRange    = ‘200.200.200.20’
   EndRange      = ‘200.200.200.200’
   SubnetMask    = ‘255.255.255.0’
   LeaseDuration = ‘0.8:00:00’
   State = ‘Active’
   }
7. Add-DhcpServerV4Scope @DhcpScope
8. Verify the pool is active

   Get-DhcpServerV4Scope -ScopeID ‘200.200.200.0’

Career Connection

Windows Server continues to be one of the most widely deployed platforms for enterprise infrastructure services. Systems administrators and network engineers routinely configure DHCP to automate IP address management, reduce administrative overhead, and ensure consistent network connectivity for users and devices. Equally important is the ability to validate service operation through packet analysis and troubleshooting. The skills developed in this chapter reflect common responsibilities in enterprise IT environments where Microsoft infrastructure and automated network services play a central role.

End of Lab