- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Receiving a dhcp from windows server for a new vlan on an MX
The main vlan10 is getting dhcp from my windows server 192.168.100.0/24. (Meraki option: do not respond to dhcp requests). I have made a new dhcp scope on my windows dhcp server, say 192.168.150.0.24. On the new vlan in Meraki - vlan20- would I put the option: relay dhcp to another server? (the windows dhcp server is 192.168.100.5) How will the workstations on vlan20 know which ip range to grab from the windows server?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Just configure the DHCP relay pointing to your Windows IP and everything will work fine.
For more details consult the documentation.
https://documentation.meraki.com/MX/DHCP/Configuring_DHCP_Relay
Please, if this post was useful, leave your kudos and mark it as solved.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thankyou, but what will prevent the client from receiving a .100 address (main scope) and not a .150 address (new scope)? I guess it gets it from the vlan interface IP when I created the vlan in the MX?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Tagging the correct VLAN on the switch port where the client is connected or on the SSID in the case of WiFi. Very simple. 😉
Please, if this post was useful, leave your kudos and mark it as solved.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It would be interesting for you to read the documentation and understand what a broadcast domain is.
Please, if this post was useful, leave your kudos and mark it as solved.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
When the switch forwards a DHCP packet it includes the layer 3 interface IP address where the original DHCP packet was received. This lets the DHCP server know which subnet it came from.
