MikroTik DHCP Relay with Microsoft Windows DHCP Server

microtech dhcp relay with microsoft windows dhcp server so in this video microtech dhcp relay with microsoft windows dhcp server from our recent videos we have configured bridge vlan filtering and centralized dhcp server in microtic as well as dhcp server role in windows server 2012 r2 in this video we will attempt to combine what we have learned so far in some deployments dhcp service is usually placed when you have a full pledge server so for instance in a windows server as there are many advantages particularly in a domain environment you have also other features like dhcp failover or clustering so we will revise our centralized dhcp server demo in which this time we will have our windows server act as the central dhcp server for all our vlans so we will configure vlan in our microtic also our microtic will act as the dhep relay accommodating the egp requests and sending it to our windows dhtp server and then finally we will test if our clients that are connected to our micro tick in different vlans will be able to get ip address from our windows dhcp server so we have a microtech cloud hosted router that we have configured bridge vlan filtering so kindly check on our configure bridge vlan filtering video for more details we have vlan 100 for our communication between the dhcp server and the dhcp relay so our dhcp server will be addressed at one nine two one six eight hundred at one slash twenty four and our dhcp relay will be addressed at one nine two one six eight hundred two five four slash twenty four so vlan 100 is more like of a management vln we have also vlan pen and vlan 20 for our test clients we have a windows server 2012 r2 here that has a dhcp server role please check on our video on how to install and configure dhcp server in windows server 2012 r2 we have configured some dhep scopes here for our test vlans then finally we have our test clients one in vlan 10 and one in vlan 20 so they should get an iep address for example for vlan 10 192 168 10 that's something and for vlan 20 192 168 that's something so we have turned on our micro tick which act as our dhcp relay so first we have configured a bridge then we have added ports 2 3 and 4. so our ether 2 is connected to our windows dhcp server our ether 3 is connected to our vlan 10 test client and our ether 4 is connected to our vlan 20 test client our ether2 is configured on vlan 100 so if you go in the pvid value is 100 our ether 3 the pvid value is 10 so it's vlan 10 and finally our ether 4 is vlan 20. next on our vlans tab we have three vlans vlan 10 20 and 100 so for vlan id 10 so we have added those vlan ids so we have added vlan 10 and the configuration is the tag interface is the bridge interface and the untagged interface is ether3 so our connection to our test client on vlan 10. so for vlan 20 so we also add it so inside the tag interface is bridge and the untag interface is our ether 4 which is connected to our vlan 20 test client and finally on our vlan id number 100 so we have also added that one so our tag interface is the bridge 1 and our untag interface is ether2 our connection to our windows server 2012 r2 then of course we have enabled in our bridge interface so if we go inside and go to the vlan tab we have enabled vlan filtering so next we have created several vlan interfaces so let's close this bridge menu window we go to interfaces actually we click the plus sign and we go in and select vlan so we now have three vlans so we have vlan pen that is under the interface bridge and the vlan id is 10 we have also vlan 20 which has a vlan id of 20 and the interface is bridge 1 and finally our vlan 100 for our management interface so the vlan id is 100 and the interface is bridge 1. so next we have configured ip addresses for the vlan interfaces so let's close this interface window and we go to ip addresses so we have an ip address for our vlan 10 interface 192.168.10.254 24 we have our vlan 20 which is one nine two one six eight twenty that two five four slash twenty four and we have our vlan 100 management ip which is 192.168.100.254. so next is our dhcp relay configuration so i will close this one and we go to ip so first i want to show you ipdgp server there are no dhcp server configured here so let me close this one so i p dhcp relay so we have two relay because we have two vlan test clients or test vlans that we want to relay the dhcp requests so we have from vlan 10 okay so vlan 10 relay is the name the interface so it's not the ether 3 interface where in our vlan 10 are connected but it's the vlan 10 layer 3 interface next is the dhcp server so this is the ip of the windows server 2012 r2 which is one nine two one six eight hundred at one and the local address is one nine two one six eight ten that two five four so the local address so it should be one of the ip address here so in this case it should be the vlan 10 address okay so once the windows server 2012 r2 is boot up we will try to verify if we could reach via ping and ping the dhcp server address first before we will test our clients if they will be able to get ip address information so next is for our vlan 20 so let's close this one so we have one for vlan 20 as well so the name is vlan 20 dash relay or you name it to your liking so the interface so it's not the ether 4 but instead it should be the vlan 20 interface so the dhcp server remains the same the server ip19216 but this time the local address should match the interface ip for vlan 20. so in our case the local address should be 192.168.20.254 because if you take a look at ip addresses that is the ip for our vlan 20 interface okay so that's about it in our relay configuration so we should now turn on our windows server 2012 r2 and check first if we could reach it via our management interface so we have turned on our windows server 2012 r2 which is our dhcp server so currently there's already an ip address 192.168.1 so if you want to check if we have connectivity for our vlan 100 management so let's try to ping our micro dhep relay and the address for that relay is 192.168.100.254. so this should be connection to that particular microtic and yes there is a reply so we have now ipconnectivity to our dhcp relay so the dhcp server role is installed so if you take a look there's already a dhcp here wherein we can go in and open the dhcp manager so if we will expand the server ipv4 so now we have already configured scopes so we have our scope from our previous video one two one six eight hundred zero so for our vlan 100 but what's important here are our scopes for one nine two one six eight ten that's zero so we have our address pool which is this one 100 to 10 the 200. so we have also a scope for our vlan 20 which is 192.168.20 that's zero and the address pool is also the same 192.168.20 100 and one and twenty twenty the two hundred so important thing to note is the vlan 10 here is actually just a name of the scope so i could change it to a different name so it is not necessarily to be a name for the vlan id so i could put in like for example finance or this is a different department name so it doesn't matter it's just a scope name okay so one thing to note our scopes are already activated so it's important also once you create a scope you must activate it so the status is active for our three scopes also our address leases for our vlan 10 so to note there are no test clients that are yet to be given an ip address because our test clients are not yet turned on or we have disabled the interface that is also true with our vlan 20 there are no address given out yet so now we have our test vm so as of the moment it is disabled yet the ethernet or network adapter so let's just also note the hostname inq01 and now we will enable this one and see if it acquires an ip okay so let us double check that it has no static ip and yes there is no static ip that is configured and let's click the status and yes it acquires an ip from the list range 192.168.10 that hundred the dhcp server is our windows server 2012 r2 so if we double check if we could reach now our php server and yes and our relay which is our micro tick and yes it's reachable let's double check or verify in our windows server so we go to vlan 10 because that computer is a vlan 10 network so we go to address leases we refresh and yes there is now a computer that has been given out an ip address which is the correct or the matching ip address from our test client and also take note the host name is also reflected correctly here inq01 also we can verify here in our dhcp relay if there is really activity so ipdhcp relay and for this case it's vlan 10 relay and if you go to status you see that there are requests and there are indeed responses to these such requests okay so this is now done so the windows virtual machine did get an ip so one into one six eight ten that hundred in that case so now let's test the other test client on vlan 20. so currently the pc name is pc2 and let's configure it with a dhcp settings on its network adapter and there you go the discover offer requests acknowledge process is done and you see it acquires a vlan 20 ip address 192.168.20 that's 100. and for checking let's try to see if ipconnectivity or our microtic is available and yes it's reachable so we can verify in our windows server side so we go to vlan 20 address leases and refresh and yes so although the pc name seems to be off because that is a virtual simulator but it did reflect the correct ip address one into once you say 20 that hundred and finally here in our dhcp relay so we could see our dhcp relay in our vlan 20 relay status and indeed there is some request and the responses are given as a summary first we've shown the vlan configuration in our micro tick so i hope you see that for our dhcp server port it is not a tag interface but rather just an untagged or access port next we have shown the dhcp relay configuration important thing to note there is that the interface should be the vlan interfaces rather than the ether interface then for our dhcp server configuration we have scopes and in case you wonder if there is a vlan identifier in each of those scopes there is none lastly we have verified from our test clients in vlan 10 and vlan 20 that indeed our configuration is working because our clients are able to get ip address from their respective vlan subnet i hope you learned something from this video thank you for watching

Channel: Inquirinity

Views: 689

Keywords:

Id: QDD8MaeZphA

Length: 17min 28sec (1048 seconds)

Published: Tue Aug 03 2021