Experimental requirements:
You as the network administrator need to complete the following tasks:
- Prepare two Windows Server 2016 (assume the computer name is WS2016-01, assuming the addresses are 192.168.109.10 and WS2016-02).
- Install the DHCP service on WS2016-01, create a scope, assign the address range from 192.168.109.100 to 192.168.109.200, set the gateway and DNS, and exclude the address of 192.168.109.129.
- WS2016-02 is set to automatically obtain an IP address, and check whether the address can be obtained. At the same time, at least two methods need to be used to verify that the address is the address allocated on WS2016-01.
- Although WS2016-02 obtains the IP address automatically, due to business needs, it is required to assign the same address every time. Please complete the settings and verify.
- After completing the above experiments, please also deploy the DHCP service on WS2016-02, and set failover for WS2016-01 to complete the high reliability setting of DHCP.
Operation process:
Prepare two virtual machines and restore the virtual machines to the initial state
Modify the names of the two virtual machines to WS2016-01 and WS2016-02 respectively
Open VMware's network editor
find vmnet8
Close dhcp, and write down this network segment, 192.168.109.0/24
Modify the IP address of WS2016-01
Open server manager, install dhcp
Currently only DHCP is installed on WS2016-01, WS2016-02 is not installed first
On WS2016-01, open Server Manager--Tools--DHCP
Right click on IPV4 and select New Scope
random name
Enter address pool range
exclude 192.168.109.129
The default lease period is 8 days, which is too long to cause problems, so modify it to 11 hours and 59 minutes
Set default gateway
set default DNS
The wins server does not need to be set, just go to the next step
select activate now
The DHCP basic configuration is complete, open WS2016-02, select VMnet8 as the network connection mode, which is NAT, and set the IP to automatically obtain
Disable the network card on WS2016-02 and enable it again, or restart WS2016-02 directly
Then open the command line interface and enter ipconfig /all to view the IP
The IP address is 192.168.109.100, the setting is successful, and record the physical address at the same time
00-0C-29-E7-29-1F
In the DHCP on WS2016-01, open the address lease, you can see that 192.168.109.100 is online, this is the second method to prove that the IP address of WS2016-02 is allocated by WS2016-01, the first method is the above, WS2016-02 is set to automatically obtain, and at the same time, it is in the same network segment as WS2016-01, VMware's DHCP is turned off, and the address obtained by WS2016-02 is within the address range set by WS2016-01
Open the scope we just created in DHCP on WS2016-01, right-click reservation-new reservation
For the convenience of verification, we choose 192.168.109.102 as the reserved address, the name is random, and the MAC address is filled with the physical address of WS2016-02
After the configuration is complete, go to WS2016-02 to disable and enable the network card, and then enter ipconfig on the command line interface to view the ip
successfully set
Install DHCP on WS2016-02
Set the IP address of WS2016-02 to 192.168.109.20
Return to WS2016-01, right-click the newly created scope in DHCO, and select Configure Failover
Fill in the address of WS2016-02 in the partner server
Because there is no requirement in the topic, we use the default configuration. In the actual production environment, you can configure it according to your real needs.
Enter shared secret
At this time, open the DHCP of WS2016-02, and you can see the sic scope we created on WS2016-01, and the configuration is successful
