DHCP on a branch office server?

I want to setup DHCP on a branch office server to give out addresses to the
workstations in the branch office (obviously). Will this have any
implications on the main offices DHCP server? Will they conflict? The main
office is on 192.168.1.10 netwrok and the branch is on a 192.168.10.1 network.

Thanks!

No, DHCP is broadcast on the local network only, unless you specifically
forward it,
Anthony, http://www.airdesk.com


"WetBehindEars" <(E-Mail Removed)> wrote in message
news:21399529-A562-4102-AC3F-(E-Mail Removed)...
>I want to setup DHCP on a branch office server to give out addresses to the
> workstations in the branch office (obviously). Will this have any
> implications on the main offices DHCP server? Will they conflict? The
> main
> office is on 192.168.1.10 netwrok and the branch is on a 192.168.10.1
> network.
>
> Thanks!

You must configure the two DHCP servers with separate scopes that do not
overlap. Ensure that neither server can give out an address applies to
the network serviced by the other.

That said, you can also provide yourself a little redundancy by taking
advantage of the fact that when a client receives offers from multiple
DHCP servers, it generally chooses the address from the offer that
arrived first - presumably the local box.

On DHCP server A, serving subnet A, create a scope A that has the 80% of
the addresses for that subnet. On DHCP server B, create a scope A that
has the other 20% of the addresses for subnet B. That way, if for some
reason DHCP server A goes down, B can service requests until A is back
up.

At the same time, configure DHCP server B with a scope for subnet B that
contains 80% of the addresses for subnet B. Then configure DHCP server
A with a scope for B that contains the other 20% of the addresses.

For example, split a typical class C (like 192.168.1.XXX) into:
Scope on server A for subnet 192.168.1.0/24:
192.168.1.1 - 192.168.1.200
Scope on server B for subnet 192.168.1.0/24:
192.168.1.201 - 192.168.1.254

I hope this helps!

--
Thanks,
Dave Bishop [MSFT]


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

> No, DHCP is broadcast on the local network only, unless you
> specifically forward it,
> Anthony, http://www.airdesk.com
>
>
> "WetBehindEars" <(E-Mail Removed)> wrote in
> message news:21399529-A562-4102-AC3F-(E-Mail Removed)...
>>I want to setup DHCP on a branch office server to give out addresses
>>to the
>> workstations in the branch office (obviously). Will this have any
>> implications on the main offices DHCP server? Will they conflict?
>> The main
>> office is on 192.168.1.10 netwrok and the branch is on a 192.168.10.1
>> network.
>>
>> Thanks!
>
>

They will not conflict.

--
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.
-----------------------------------------------------

"WetBehindEars" <(E-Mail Removed)> wrote in message
news:21399529-A562-4102-AC3F-(E-Mail Removed)...
>I want to setup DHCP on a branch office server to give out addresses to the
> workstations in the branch office (obviously). Will this have any
> implications on the main offices DHCP server? Will they conflict? The
> main
> office is on 192.168.1.10 netwrok and the branch is on a 192.168.10.1
> network.
>
> Thanks!

I did that with a 50% split and the reservations copied between the
two.. It has come in handy more than once..

---
Jeffrey Randow
(E-Mail Removed)
Windows Networking MVP 2001-2006
http://www.networkblog.net

On Wed, 17 Oct 2007 13:58:13 -0700, "Dave Bishop [MSFT]"
<(E-Mail Removed)> wrote:

>You must configure the two DHCP servers with separate scopes that do not
>overlap. Ensure that neither server can give out an address applies to
>the network serviced by the other.
>
>That said, you can also provide yourself a little redundancy by taking
>advantage of the fact that when a client receives offers from multiple
>DHCP servers, it generally chooses the address from the offer that
>arrived first - presumably the local box.
>
>On DHCP server A, serving subnet A, create a scope A that has the 80% of
>the addresses for that subnet. On DHCP server B, create a scope A that
>has the other 20% of the addresses for subnet B. That way, if for some
>reason DHCP server A goes down, B can service requests until A is back
>up.
>
>At the same time, configure DHCP server B with a scope for subnet B that
>contains 80% of the addresses for subnet B. Then configure DHCP server
>A with a scope for B that contains the other 20% of the addresses.
>
>For example, split a typical class C (like 192.168.1.XXX) into:
> Scope on server A for subnet 192.168.1.0/24:
> 192.168.1.1 - 192.168.1.200
> Scope on server B for subnet 192.168.1.0/24:
> 192.168.1.201 - 192.168.1.254
>
>I hope this helps!