DHCP fix Setup Notes - Oliver-Mustoe/Oliver-Mustoe-Tech-Journal GitHub Wiki

In this page I detail how I added a DHCP service to a Windows server core VM.

Notes

FIRST I GAVE THE WORKSTATION I WAS WORKING ON A STATIC IP, IF A DHCP SERVICE IS ALREADY RUNNING YOU DO NOT NEED TO DO THIS STEP.

BELOW ARE THE SPECIFICATIONS I USED:

IP ADDRESS: 10.0.5.100
SUBNET MASK: 255.255.255.0
GATEWAY: 10.0.5.2
DNS: 10.0.5.5

I went into server manager, on a workstation that already had it setup, and clicked Manage > then Add Roles and features.

In the menu that pops up I followed along pressing next, until the server destination screen where I made sure to selected AD2-firstname. I kept continuing with the default settings then on the "Select server roles" screen selecting the "DHCP Server" role and continuing. Finally A confirmation screen would appear where I would check the box to restart the server automatically if need be, I also reviewed my options and made sure they were correct. I then pressed install and waited till it was finished.

Once it is finished I saw an option to "Complete DHCP configuration", I clicked it and followed along the steps. Such as authorizing my user and watching the status of configuration steps.

After this in server I went into the newly created DHCP section, right clicked AD2, and selected "DHCP Manager" (NOTE: from here Windows will instruct you in how to setup properly, use that as well as this as a reference.) This pulled up a setup wizard where I set the following:

  • Name & Description: This section does not matter too much, set that will remind you what it is used for.

  • Start IP address: 10.0.5.100

  • End IP address: 10.0.5.150

  • Subnet mask: 255.255.255.0 (Or length: 24)

  • I did not set any exclusions, if the start/end ip range was smaller this may be required.

  • Lease duration: As long as wanted.

When asked to configure DHCP options for this scope I pressed yes then next. Where I set the following:

  • Router: Added "10.0.5.2" to the list.

  • The parent domain and IP were set, but if not I would have set them to "firstname.local" and "10.0.5.5" respectively.

  • I left WINS section blank and continued to the end.

After the configuration my scope was not activated, so I selected "IPv4" and clicked "Action" > then clicked "Activate".

To test that this was working I changed back to dynamic IP address (if needed) and pinged around the network, google.com, and checked "ipconfig /all" after a /release and /renew.

SOURCES:
https://www.c-sharpcorner.com/article/dhcp-role-on-windows-2019-core/
https://www.dtonias.com/authorize-dhcp-server-2016/
https://activedirectorypro.com/configure-dhcp-server/