Windows 2008 R2 DHCP for two scope on two interfaces

Question

I'm setting up a brand new DHCP Server over Windows 2008 R2 Standard edition server, and I'm planning to serv two differents lan with this one.

Here is my configuration:

1 AD/DNS/DHCP Server with following ETH setup:

ETH0 = PROD_SERVERS_LAN = VLAN100 = 10.30.0.0/24 Subnet.
ETH1 = PROD_CLIENTS_LAN = VLAN200 = 10.30.1.0/24 Subnet.

On the server I've set the following things:

AD = 1 Site with both subnets
DHCP = 2 scope

Now I wondering how can I be sure that my differents workstations/servers will ask and be answered by the correct scope?

I thought used the DHCP with NAP filtering but it seems to be buggy and heavy to manage. Do you already have perform this kind of things with Windows infrastructure?

I'm able to do this with Linux Server, but I want to learn to do this things with Windows now.

Solution

All DHCP servers (and DHCP Proxies) will only issue IPs that lie within the subnet of the interface on which they issue the IP. So if you have two NICs with two different subnets, only IPs that match the subnet for the NIC will be issued on that NIC.

(Some DHCP server software is configurable enough to override this functionality; but is not the default)

Comments

[joeqwerty]

Have you actually tested this yet? It seems to me that it should work "right out of the box".

[joeqwerty]

I have to say that I think you're wrong here. The DHPC service can bind to multiple adapters (multi-homed). That being said, if the DHCP server has scopes that encompasses the networks that it's NIC's are configured on then it should service DHCP clients from those scopes for those connected networks. This shouldn't be any different to having a single-homed DHCP server servicing DHCP clients on foreign subnets via a DHCP relay agent. The only difference is that the DHCPDiscover packets from each subnet will hit the DHCP server NIC directly instead of being forwarded by a relay.

[joeqwerty]

Glad to pipe in my 2 cents (again). :)

[Dr I]

My guess was that DHCP Server will be able to serv the correct lan with the correct scope because of the request incoming from ETH0 is incoming over a A network which (in any logical terms)should be serv by th A matching scope as explained it joeqwerty. OK many thanks to everyone, I'll gonna do some tests with my Virtual machines. Thanks again, efficient help on ServerFault, as usual ;).