19 Dynamic Host Configuration Protocol – Windows

Dynamic Host Configuration Protocol (DHCP) is an interacting client-server protocol that automatically provides a host (PC, Laptop, Phone, etc) with an Internet Protocol (IP) address upon request.  The purpose of this activity is for learners to see DHCP in action instead of just reading about the DHCP handshake theory.  A secondary purpose is for learners to experience frustration when hosts do not get a DHCP IP address.  Learners can see how the packets move and where they may get hung up while working on making DHCP function correctly on their network.  Finally, learners will be able to see Address Resolution Protocol (ARP) in action.  While DHCP occurs when a host requests an IP address for an existing MAC address, ARP is when a host has an IP address, but is unsure what MAC address it belongs to.

Estimated time for completion: 20 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

• Chapter 6 – Adding a Virtual Machine to GNS3
• Chapter 8 – Create a Windows Server
• Chapter 17 – IPv4 Addressing

Deliverables

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

Resources

• NOTE: Each source will referenced with its corresponding number in superscript (EX: ¹  ) at the end of a step
• 1. MSFT WebCast. “Basic Configuration Tasks in Windows Server 2019.” YouTube, January 25, 2019. https://www.youtube.com/watch?v=1nxYJSV7-u8&list=PLUZTRmXEpBy32NP6z_qvVBOTWUzdTZVHt&index=5.
• 2. MSFT WebCast. “Install and Configure DHCP Server in Windows Server 2019 Step by Step Guide.” YouTube, February 3, 2019. https://www.youtube.com/watch?v=fUK6d3s1Im4&t=414s.

Contributors and testers

• Mathew J. Heath Van Horn, PhD, ERAU-Prescott
• Julian Romano, Cybersecurity Student, ERAU-Prescott
• Dante Rocca, Cybersecurity Student, ERAU-Prescott
• Jacob M. Christensen, Cybersecurity Student, ERAU-Prescott

Phase I -Build the Network Topology

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

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

   NOTE: This example uses the same network topology that was 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: Ensure that the Allow GNS3 to use any configured VirtualBox adapter check box is selected for all VMs added to GNS3. Refer to  step 6.2 in Chapter 11 for more information.

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

      

1. Start the server and login
2. Focus on the Server Manager dashboard window ¹
   

   

   NOTE: If the Server Manager does not start on boot, can open it via the Windows Start menu.

3. On the left side of the page, select the Local Server option
4. Assign the IP address 200.200.200.254 to the local ethernet interface
   1.  Under the PROPERTIES table, left-click on the Ethernet option (Figure 4) ¹

      NOTE: This is located beneath NIC Teaming and above Operating system version.

   2. Right-click on the network interface you want to use (e.g. “Ethernet”) and select Properties in the context menu (Figure 5) ¹
   3. A new sub-window labeled Ethernet Properties should appear
      1. Uncheck Internet Protocol Version 6 (TCP/IPv6) ¹
      2. Check and highlight the Internet Protocol Version 4 (TCP/IPv4) option ¹
      3. On the bottom right corner, click on Properties (Figure 6) ¹
   4. A new sub-window labeled Internet Protocol Version 4 (TCP/IPv4) Properties should appear (Figure 7) ¹
      1. Select Use the following IP address
         1. Enter 200.200.200.254 as the IP address ¹
         2. Enter 255.255.255.0 as the Subnet mask ¹
         3. Enter 200.200.200.1 as the Default gateway ¹
      2. Select Use the following DNS server addresses
         1. Enter 200.200.200.254 as the Preferred DNS server ¹
         2. Leave the Alternate DNS server blank ¹
      3. Click OK to apply these settings ¹
      4. Click Close to return to the Network Connections window
   5. Close the Network Connections window
5. Restart Windows Server

1. Focus on the Server Manager dashboard window ²
2. In the top right-hand corner of the screen, select Manage  ²
3. Select Add Roles and Features from the context menu  ²
4. A popup window labeled Add Roles and Features Wizard will open (Figure 8)
   1. Before you Begin – Click Next  ²
   2. Installation Type – Select the Role-Based option – then click Next (Figure 9) ²
   3. Server Selection – Select your local server (this should be the only option) then click Next (Figure 10) ²
   4. Server Roles – select DHCP Server  ²
      1. POP-UP – Add Features – Select Add Features towards the bottom of the new screen (Figure 11) ²
      2. Return back to Server Roles – Click Next  ²
   5. Features – Click Next  ²
   6. DHCP Server – Click Next  ²
   7. Confirmation – Click Install  ²
   8. Once installation is complete click on the blue text that states Complete DHCP Configuration (Figure 12) ²
5. POP-UP – DHCP Post-Install Configuration Wizard
   1. Description – Click Next  ²
   2.  Authorization – Click Commit  ²

      NOTE: The default authorization should be set to use Administrator credentials.  If it doesn’t, you’ve done something wrong and need to restart.

   3. Summary – Click Close  ²
6. Return to Rolls and Features Wizard
   1. Results – Click Close  ²
7. Restart Windows Server

1. Focus on the Server Manager dashboard window
2. In the top right-hand corner of the screen, select Tools  ²
3. From the drop-down menu, select DHCP  ²
4. A new sub-window labeled DHCP should appear
   1. Expand the local computer forest (Figure 13) ²
   2. Right-click on the IPv4 option and select New Scope from the context menu (Figure 14) ²
5. The New Scope Wizard window will open
   1. Scope Wizard Welcome – Click Next (Figure 15) ²
   2. Scope Name (Figure 16)
      1. Add a name such as Scope1 ²
      2. The description field can be left blank
      3. Click Next  ²
   3. IP Address Range (Figure 17) ²
      1. Start IP address – 200.200.200.20
      2. End IP address – 200.200.200.250
      3. Length – 24 ²
      4. Subnet mask – 255.255.255.0 ²
      5. Click Next
   4. Add Exclusion and Delay – Click Next  ²
   5. Lease Duration (Figure 18) ²
      1. Limited to 8 hours ²
      2. Click Next
   6. Configure DHCP ²
      1. Select Yes
      2. Click Next
   7. Router (Default Gateway) (Figure 19) ²
      1. IP address – 200.200.200.1
      2. Click Add
      3. Click Next
   8. Domain Name and DNS Servers – Click Next  ²
   9. WINS Servers – Click Next  ²
   10. Activate Scope
       1. Click Yes  ²
       2. Click Next  ²
   11. Click Finish
6. Notice that Scope now appears under the DHCP>machine_name>IPv4 tree (Figure 20)
7. Close the DHCP window

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

      > ip dhcp

   2. Notice the four main DHCP packets being exchanged in Wireshark that were discussed in the previous chapter: Discover, Offer, Request, Accept
4. Start PC2 and open its console
   1. Request a new IP address

      > ip dhcp

5. Ensure that PC1 is able to ping PC2
6. Congratulations! You now know how to configure a basic DHCP server on both Linux and Windows machines

End of Lab

Figures for Printed Version