DHCP is Down - rune-seregina/sys-255-fa24 GitHub Wiki

Objective
In this lab, I resolved a help ticket in which my DHCP server went down and I had to configure my FS01 machine to act as DHCP to provide the same services in the same format as my initial DHCP server.

Resources used:

IP Assignments:

  • WAN IP (synonymous with fw interface 1/em0): 10.0.17.112/24
  • LAN IP (synonymous with fw interface 2/em1): 10.0.5.2/24
  • wks02-rune IP: 10.0.5.150/24 (or as assigned by DHCP)
  • wks02/ad02/dhcp02/fs01 default gateway: 10.0.5.2/24
  • wks02/dhcp02/fs01 dns: 10.0.5.6
  • ad02-rune ip: 10.0.5.6/24
  • dhcp02-rune ip: 10.0.5.4/24 (R.I.P)
  • fs01-rune ip: 10.0.5.8/24

Accounts:

  • ad02-rune: rune\Administrator (password A)
  • rune.local: rune.seregina (password A)
  • rune.local: rune.seregina-adm (password A)
  • rune.local: alice (password A)
  • rune.local: bob (password A)
  • fs01-rune: Administrator (password B)

Installing and Configuring DHCP

  • Here is a good reference: https://learn.microsoft.com/en-us/windows-server/networking/technologies/dhcp/quickstart-install-configure-dhcp-server?tabs=powershell Installation
  • In ADDS, I added the DHCP Server Role and DHCP Server Tools features.
    • Add Roles and Features Wizard > Select Server (FS01+AD02) > Server Roles > DHCP Server
    • {9AEA637A-5ECE-403A-8FD8-4CD5A780650D}
    • Add Roles and Features Wizard > Select Server (FS01+AD02) > Features > Remote Server Administration Tools > Role Administration Tools > DHCP Server Tools
    • {0BFE711D-D4A5-470F-B470-AAFF64791B92}
  • Configuration Wizard (post-deployment configuration for DHCP post-install)
    • Commit Admin Credentials
    • {A96CCA00-9503-45CF-A5C8-E733FE0D8C07} Authorize in Active Directory
  • Run Powershell as Administrator
  • Run command: Install-WindowsFeature DHCP -IncludeManagementTools
  • Run command: Add-DhcpServerInDc -DnsName FS01-RUNE.rune.local IPAddress 10.0.5.8 (in this case, its already authorized)
  • Double-check, run command: Get-DhcpServerInDc
  • {EEB36135-4C16-4238-8C08-CCFA1BA95609} Configure scope
  • Server Manager > DHCP > FS01-RUNE > Right Click > DHCP Manager > FS01-RUNE.rune.local > IPv4 > New Scope
  • Enter name, Start IP address, End IP address, Subnet Mask, lease time, Configure default gateway and DNS server, Active Scope!!!
  • on WKS02, run ipconfig /release, run ipconfig /renew and ipconfig /all. make sure everything is correct (IP address, DHCP server, DNS server, Default gateway)
  • {D8FDE2C4-0B7F-40C8-9685-2B855970C040}
  • On DHCP Manager, check for address leases under the created scope to check for wks02

Troubleshooting

  • Had trouble running the "Add-DhcpServerInDc -DnsName FS01-RUNE.rune.local IPAddress 10.0.5.8" command, as FS01 was being super finicky. Eventually I was able to figure out that I could do it on AD01 but only if I ran PowerShell as Administrator.
  • At first, Default Gateway wasn't configured correctly for wks02. Realized I had not hit the "Add" button so I remade my scope correctly.
  • {B7792B7E-4041-48E1-BB36-6074A3BFA791} < ADD!!!!

Reflection
This was definitely one of the harder assignments, it almost felt like a full lab on its own. It made me build upon my preexisting knowledge of configuring DHCP but in a completely new way that made me do a lot of research and trial and error before finding the solution.

⚠️ **GitHub.com Fallback** ⚠️