Lab 09 ‐ Module 01 ‐ DHCP is Down! - Isaiah-River/SYS-255-02-SYSAdmin GitHub Wiki
Main Lab
Overview
My DHCP server has been stolen! This module focuses on resolving this issue and moving my DHCP server to my Windows fs01-isaiah VM.
Objectives:
- Deploy DHCP on a Windows member server that works EXACTLY the same as the old server did.
Part 01 - Temporarily Assign Static IP to wks02-isaiah
When I opened up my wks02-isaiah VM I was greeted with a lack of internet as seen below.
I started my fix by reassigning a Static IP to WKS02 so that it is able to communicate with the web and server. In order to do so I went into my IPv4 properties and changed them back to static settings similar to what I had prior to setting up DHCP.
I then set up a new A record in DNS manager pointing to to the new IP for wks02-isaiah.
After this I was greeted with a working internet connection.
Part 02 - Installing the DHCP server on fs01-isaiah
Now that I've resolved the lack of internet temporarily on wks02-isaiah, it was time to install and configure my Windows DHCP Server. In order to install it I used the command PowerShell to open up PowerShell on fs01-isaiah, after this I ran the command Install-WindowsFeature DHCP -IncludeManagementTools to install DHCP services.
Part 03 - Authorize the DHCP server in Active Directory
After this I needed to authorize my DHCP server in Active Directory. In order to do this I went to Server Manager on ad02-isaiah, and went to the DHCP tab, and right clicked fs01-isaiah and went to DHCP Manager.
I then went to manage authorized servers where I authorized fs01-isaiah.
Part 04 - Creating and configuring a scope
After authorizing my fs01-isaiah VM I went to DHCP manager, and under IPv4 right clicked and hit New Scope...
I then went through the wizard configuring each of the fields properly, giving it a name and description (wksScope, A scope for Workstation computers), a start and end of the scope (10.0.5.150 - 10.0.5.175), a subnet mask (255.255.255.0), a lease duration (1 day, the CentOS default length), default gateway (10.0.5.2), and finally a DNS server (10.0.5.6). After finishing through the wizard I had a new Scope folder created for my wksScope
With my scope created, it was time to set my wks02-isaiah back to using DHCP.
Part 05 - Configuring wks02-isaiah with DHCP... Again...
Once again I went back to my IPv4 configuration and set my configuration to automatically assign an address and DNS server.
I then found my lease sent out to wks02-isaiah under Scope [10.0.5.0] > Address Leases.
After this I went back and removed my A and PTR records from DNS manager, and then went to the properties for my new scope. Here I went to my DNS settings and enabled DNS to update both A and PTR records.
After this I once again had internet, and an IP address automatically assigned through DHCP.