DHCP for multiple subnets

I may know the answer to this, but wanted to ask anyways:

I currently have 2 subnets/VLANs, 1 for Windows 2003 servers (10.100.60.0)
and 1 for Windows XP desktops (10.100.40.0). Currently, DHCP is servicing the
..60 subnet mainly for newly deployed devices (most devices will eventually be
assigned a static IP address).

If possible, I would like to create an additional DHCP scope (or add a 2nd
DHCP server) to service the .40 subnet, however this server would physically
reside in the .60 subnet. A Layer3 cisco switch would be configured for DHCP
relay to allow for this.

I guess the question is: Is it possible to add that 2nd scope or DHCP server
to ONLY service the client desktop subnet, and the existing DHCP
scope/server service ONLY the .60 subnet? Or is it mandatory that a DHCP
server exist in the .40 subnet in order to fulfill these requirements.

Thank you

It is simple:

1. Use the existing DHCP Server. It only takes one.
2. Create a correct Scope for the other subnet (no superscopes)
3. Configure the LAN Router between the subnets to forward DHCP Queries to
the DHCP Server
4. All done.

All "user" machines should be DHCP Clients with no Reservations or as few
Reservations as possible.

All Servers, Utility machines, and Network Devices should be specifically
Static (not reserved in DHCP,...not any DHCP at all). The Infrastucture
should never have to depend on the DHCP Server being "alive" in order for
the infrastucture to exist.

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

"Jorge Azcuy" <(E-Mail Removed)> wrote in message
news:87CC40A4-557A-4DB5-900C-(E-Mail Removed)...
>I may know the answer to this, but wanted to ask anyways:
>
> I currently have 2 subnets/VLANs, 1 for Windows 2003 servers (10.100.60.0)
> and 1 for Windows XP desktops (10.100.40.0). Currently, DHCP is servicing
> the
> .60 subnet mainly for newly deployed devices (most devices will eventually
> be
> assigned a static IP address).
>
> If possible, I would like to create an additional DHCP scope (or add a 2nd
> DHCP server) to service the .40 subnet, however this server would
> physically
> reside in the .60 subnet. A Layer3 cisco switch would be configured for
> DHCP
> relay to allow for this.
>
> I guess the question is: Is it possible to add that 2nd scope or DHCP
> server
> to ONLY service the client desktop subnet, and the existing DHCP
> scope/server service ONLY the .60 subnet? Or is it mandatory that a DHCP
> server exist in the .40 subnet in order to fulfill these requirements.
>
> Thank you

I understand the process you have outlined, however, my question was
specifically geared to the possibility of allowing both DHCP scopes to
coexist.

Having the 'server' subnet with DHCP functionality would be preferred so
that new nodes would immediatley have network connectivty. This is a remote
branch site and it would be a great convenience to have this functionality
enabled.

"Phillip Windell" wrote:

> It is simple:
>
> 1. Use the existing DHCP Server. It only takes one.
> 2. Create a correct Scope for the other subnet (no superscopes)
> 3. Configure the LAN Router between the subnets to forward DHCP Queries to
> the DHCP Server
> 4. All done.
>
> All "user" machines should be DHCP Clients with no Reservations or as few
> Reservations as possible.
>
> All Servers, Utility machines, and Network Devices should be specifically
> Static (not reserved in DHCP,...not any DHCP at all). The Infrastucture
> should never have to depend on the DHCP Server being "alive" in order for
> the infrastucture to exist.
>
> --
> 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.
> -----------------------------------------------------
>
> "Jorge Azcuy" <(E-Mail Removed)> wrote in message
> news:87CC40A4-557A-4DB5-900C-(E-Mail Removed)...
> >I may know the answer to this, but wanted to ask anyways:
> >
> > I currently have 2 subnets/VLANs, 1 for Windows 2003 servers (10.100.60.0)
> > and 1 for Windows XP desktops (10.100.40.0). Currently, DHCP is servicing
> > the
> > .60 subnet mainly for newly deployed devices (most devices will eventually
> > be
> > assigned a static IP address).
> >
> > If possible, I would like to create an additional DHCP scope (or add a 2nd
> > DHCP server) to service the .40 subnet, however this server would
> > physically
> > reside in the .60 subnet. A Layer3 cisco switch would be configured for
> > DHCP
> > relay to allow for this.
> >
> > I guess the question is: Is it possible to add that 2nd scope or DHCP
> > server
> > to ONLY service the client desktop subnet, and the existing DHCP
> > scope/server service ONLY the .60 subnet? Or is it mandatory that a DHCP
> > server exist in the .40 subnet in order to fulfill these requirements.
> >
> > Thank you
>
>
>

"Jorge Azcuy" <(E-Mail Removed)> wrote in message
news:48759953-93EC-448C-8978-(E-Mail Removed)...
>I understand the process you have outlined, however, my question was
> specifically geared to the possibility of allowing both DHCP scopes to
> coexist.

That is what I said:
2 Scopes -- 2 subnets -- 1 DHCP Server sitting on one of the subnets

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

"All Servers, Utility machines, and Network Devices should be specifically
Static (not reserved in DHCP,...not any DHCP at all). "

This misses the point of what I'm tryin to do. I want both subnets to be
able to recieve their initial settings via DHCP.

"Phillip Windell" wrote:

> "Jorge Azcuy" <(E-Mail Removed)> wrote in message
> news:48759953-93EC-448C-8978-(E-Mail Removed)...
> >I understand the process you have outlined, however, my question was
> > specifically geared to the possibility of allowing both DHCP scopes to
> > coexist.
>
> That is what I said:
> 2 Scopes -- 2 subnets -- 1 DHCP Server sitting on one of the subnets
>
> --
> 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.
> -----------------------------------------------------
>
>
>

"Jorge Azcuy" <(E-Mail Removed)> wrote in message
news:6B34C8D8-AF49-4119-A419-(E-Mail Removed)...
> "All Servers, Utility machines, and Network Devices should be specifically
> Static (not reserved in DHCP,...not any DHCP at all). "
>
> This misses the point of what I'm tryin to do. I want both subnets to be
> able to recieve their initial settings via DHCP.

That is a very *bad* thing to want. You need to change your mind about
that. Loosing the DHCP Service would take down the whole network. You
would be hanging by a thread.

The network infrastructure needs to stand independently on its own and not
be dependent on a DHCP Server for it to exist. DHCP is a *convienence* tool
for auto configuring *clients*,...that is what it was designed for.

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

Please reread my original post. I clearly stated that my intention is NOT for
the servers to rely on DHCP on an ongoing basis. They will soon be assigned
static addresses after they are deployed. I want DHCP available for INITIAL
network access so that if:

- A new device (printer, UPS, Tape Library) is introduced into the
environment, it can immediatelt recieve a network address that can be used
for management.
- A server is deployed (we are using Virtual Servers), it can immediately
join the domain and access Windows Updates

Once these 2 criteria are met, they will be assigned a static address.

"Phillip Windell" wrote:

> "Jorge Azcuy" <(E-Mail Removed)> wrote in message
> news:6B34C8D8-AF49-4119-A419-(E-Mail Removed)...
> > "All Servers, Utility machines, and Network Devices should be specifically
> > Static (not reserved in DHCP,...not any DHCP at all). "
> >
> > This misses the point of what I'm tryin to do. I want both subnets to be
> > able to recieve their initial settings via DHCP.
>
> That is a very *bad* thing to want. You need to change your mind about
> that. Loosing the DHCP Service would take down the whole network. You
> would be hanging by a thread.
>
> The network infrastructure needs to stand independently on its own and not
> be dependent on a DHCP Server for it to exist. DHCP is a *convienence* tool
> for auto configuring *clients*,...that is what it was designed for.
>
> --
> 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.
> -----------------------------------------------------
>
>
>

"Jorge Azcuy" <(E-Mail Removed)> wrote in message
news:A8337C55-55F6-4A70-81C0-(E-Mail Removed)...
> - A new device (printer, UPS, Tape Library) is introduced into the
> environment, it can immediatelt recieve a network address that can be used
> for management.
> - A server is deployed (we are using Virtual Servers), it can immediately
> join the domain and access Windows Updates
>
> Once these 2 criteria are met, they will be assigned a static address.

Ok.
Then just set it up like I said in my very first post.
It will work.

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