How to limit DHCP server address assignment to a single network card?

Summary:
I would like to be able to limit the interface that a DHCP server on a multi
homed machine listens on to just one of the multiple adapters.

After much Googling, I'm still looking for a solution to this.

More detailed:
I have a multi homed computer on several subnets. I only want the DHCP
server running on the box to listen for and respond to DHCP requests on a
single network card. Any requests on other network cards should be ignored.
The DHCP service should only be bound to the one network card.

Greatful for any help.

It will only give out addresses on the Nic that is in the same subnet as the
scope. Whether is listens on other nics is completely irrelevant if there is no
matching scope. The exception to that is when you use DHCP Relay on a LAN
Router,...but then the Router includes information in the relay so that the DHCP
Server knows what subnet the query is based on. However it still won't return
anything unless there is a matching scope for the target subnet.

Anyway, what you are looking for is in the DHCP MMC,

Right-click on the Servername
Choose Properties
Choose Advanced Tab
Choose the Bindings Button
Select active interfaces


--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft, or
anyone else associated with me, including my cats.
-----------------------------------------------------

"Eric Long" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Summary:
> I would like to be able to limit the interface that a DHCP server on a multi
> homed machine listens on to just one of the multiple adapters.
>
> After much Googling, I'm still looking for a solution to this.
>
> More detailed:
> I have a multi homed computer on several subnets. I only want the DHCP server
> running on the box to listen for and respond to DHCP requests on a single
> network card. Any requests on other network cards should be ignored. The DHCP
> service should only be bound to the one network card.
>
> Greatful for any help.
>
>
>

"Phillip Windell" <(E-Mail Removed)> wrote in
news:(E-Mail Removed):

> It will only give out addresses on the Nic that is in the same subnet
> as the scope. Whether is listens on other nics is completely
> irrelevant if there is no matching scope. The exception to that is
> when you use DHCP Relay on a LAN Router,...but then the Router
> includes information in the relay so that the DHCP Server knows what
> subnet the query is based on. However it still won't return anything
> unless there is a matching scope for the target subnet.
>
> Anyway, what you are looking for is in the DHCP MMC,
>
> Right-click on the Servername
> Choose Properties
> Choose Advanced Tab
> Choose the Bindings Button
> Select active interfaces
>
>

This is an awesome answer by Phillip and I want to amplify and clarify one
point.

Let's say you have three NICs to different LAN segments in 10.0.0.X,
192.168.1.X, and 192.168.2.X.

In DHCP let's say you have created one scope of 10.0.0.X

In DHCP, even if you have not set bindings and the server is listening on
all three NICs, it won't provide IP addresses to the 192 subnets because
you have not created 192 scopes. When it receives a DHCP discover on the 10
subnet though it will respond and lease an IP from the scope.

HTH

"FenderAxe" <(E-Mail Removed)> wrote in message
news:Xns99167754ED3F9faaxecom@198.186.190.165...
> This is an awesome answer by Phillip and I want to amplify and clarify one
> point.
>
> Let's say you have three NICs to different LAN segments in 10.0.0.X,
> 192.168.1.X, and 192.168.2.X.
>
> In DHCP let's say you have created one scope of 10.0.0.X
>
> In DHCP, even if you have not set bindings and the server is listening on
> all three NICs, it won't provide IP addresses to the 192 subnets because
> you have not created 192 scopes. When it receives a DHCP discover on the 10
> subnet though it will respond and lease an IP from the scope.

Thank you Sir!

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft, or
anyone else associated with me, including my cats.
-----------------------------------------------------