Hi Troy. This is great. I was having issues when trying to ping the Ip address given by the DHCP server, but they could not ping to each other. Until I had to manually turn off the firewall from both client's PC's. I believe I now have to look at opening the ICMPv4 port on the firewall. I could do this on the server and forard this as a GPO for all connecting clients. Thanks
I'm curious how Reservations play with lease duration. In this video, the lease duration was set to 8 days. What happens at the end of 8 days to the PC that's on reservations list? Does the reservation gets automatically deleted at the end of 8 days or is the lease period ignored for PCs on reservations list?
Great question, Mikhail. Despite it having a reserved address, the DHCP client is still doing its usual DHCP lease renewal process -- that is, the client will attempt to renew its IP address lease with the DHCP server once 50% of the lease expires (called the T1 interval), and if for some reason it can't reach the DHCP server, the client will try again to renew at 87.5% of the lease period (called the T2 interval). The client doesn't know that it has a specially reserved address. It just keeps asking for DHCP renewal and keeps obtaining the same reserved address. On the server side though, if you reserve a specific address for a particular DHCP client, that reservation will stay in force until you manually remove the reservation from the server. In other words, the server will continue to hold that reserved address for that particular client until you tell it not to, and the server will not hand out that address to any other client regardless if the lease has expired or whether the server hears from the client ever again. You'd have to administratively purge the reservation to free up reserved address, even if happened to be months or years past the end of the lease period and the DHCP client is no longer on the network. Again, great question. Hope that clears it up.
It did! What I understood was that the client PC, among other things, gets an *IP address* from DHCP server along with *lease duration* information. Client knows to go back to DHCP server and ask for new IP address halfway through the leasing period. If all goes well, the DHCP server sees the *MAC address* of the client submitting request, knows that this client is on reservations list to receive specific IP address and, therefore, replies with that same, reserved IP address and lease period duration information. This loop continues for as long as client will be asking for IP address and the client will continue to receive the same IP for as long as the DHCP server has the IP address reservation for that client. Thank you, sir! I appreciate you taking your time to reply!
Hi Troy, This is awesome. For Security Reasons:How am I going to block Laptops and PC that does not belong to the domain but they can easily connected to the DHCP Server through network or Mobile that can easily also connected to the WIFI using DHCP. Can you create a video how can we restrict those unauthorized users so that they cannot connect easily to the network.
Such an amazing video!! It was challenging to find out a right one, but was this! easy to understand and follow. Learned a lot! Thanks very much!
Good explanation Troy . another good video about Dhcp
Thansks Premchand! Glad you found it helpful!
Thank you for this great work. I wish you continued success👍👍
Thanks, great video! Really appreciate it.
Hi Troy. This is great. I was having issues when trying to ping the Ip address given by the DHCP server, but they could not ping to each other. Until I had to manually turn off the firewall from both client's PC's. I believe I now have to look at opening the ICMPv4 port on the firewall. I could do this on the server and forard this as a GPO for all connecting clients. Thanks
Thanks ❤
Thanks, this very helpful
I'm curious how Reservations play with lease duration. In this video, the lease duration was set to 8 days. What happens at the end of 8 days to the PC that's on reservations list? Does the reservation gets automatically deleted at the end of 8 days or is the lease period ignored for PCs on reservations list?
Great question, Mikhail.
Despite it having a reserved address, the DHCP client is still doing its usual DHCP lease renewal process -- that is, the client will attempt to renew its IP address lease with the DHCP server once 50% of the lease expires (called the T1 interval), and if for some reason it can't reach the DHCP server, the client will try again to renew at 87.5% of the lease period (called the T2 interval). The client doesn't know that it has a specially reserved address. It just keeps asking for DHCP renewal and keeps obtaining the same reserved address.
On the server side though, if you reserve a specific address for a particular DHCP client, that reservation will stay in force until you manually remove the reservation from the server.
In other words, the server will continue to hold that reserved address for that particular client until you tell it not to, and the server will not hand out that address to any other client regardless if the lease has expired or whether the server hears from the client ever again. You'd have to administratively purge the reservation to free up reserved address, even if happened to be months or years past the end of the lease period and the DHCP client is no longer on the network.
Again, great question. Hope that clears it up.
It did! What I understood was that the client PC, among other things, gets an *IP address* from DHCP server along with *lease duration* information. Client knows to go back to DHCP server and ask for new IP address halfway through the leasing period. If all goes well, the DHCP server sees the *MAC address* of the client submitting request, knows that this client is on reservations list to receive specific IP address and, therefore, replies with that same, reserved IP address and lease period duration information.
This loop continues for as long as client will be asking for IP address and the client will continue to receive the same IP for as long as the DHCP server has the IP address reservation for that client.
Thank you, sir! I appreciate you taking your time to reply!
hello, could I setup in separate vm's dns, dhcp, secondary domain server with their own ip addresses? and is that best practice? thanks
Hi Troy, This is awesome. For Security Reasons:How am I going to block Laptops and PC that does not belong to the domain but they can easily connected to the DHCP Server through network or Mobile that can easily also connected to the WIFI using DHCP. Can you create a video how can we restrict those unauthorized users so that they cannot connect easily to the network.
Which software are you using for making of virtual machines?
The VMs in this video are created by and running in Windows Client Hyper-V using Windows Server evaluation licenses.