Windows 2003 dhcp do not give ip to routers and switches

I'm using dhcp (windows 2003 SP1) on our DC. In dhcp all adresses are
excluded we only using reservations. Our routers and switches (cisco and
3com) do not obtain addresses from reservation but PC and printers are able
to obtain configuration from dhcp. Any ideas why ?

Hello lukaszjg,

Routers and switches used fixed ip configuration internal. Or what do you
mean?

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> I'm using dhcp (windows 2003 SP1) on our DC. In dhcp all adresses are
> excluded we only using reservations. Our routers and switches (cisco
> and 3com) do not obtain addresses from reservation but PC and printers
> are able to obtain configuration from dhcp. Any ideas why ?
>

Hi Meinolf

Routers and switches are configure to obtain IP address from our local dhcp
server so they are setup as a dhcp clients similar to our PC's and printers.
In our local network we are running windows 2003 server with dhcp this is as
well our domain controler.

In Windows 2003 server dhcp all addresses in our local network are excluded
from distribution and we crate reservation for our clients.

My scope settings are similar to following:
172.16.0.1 172.16.15.254 address range for distribution
172.16.0.1 172.16.15.254 IP addresses excluded from distribution

All our dhcp clients has got corresponding reservation in our dhcp server.
I have reservation for our switches,routers,pc,printers.

All addresses are excluded form distribution because we want to have strict
control of our IP assignment. We want that our dhcp clients will always have
the same IP settings given from dhcp.

For some reason this does not seems to work for routers and switches. PC and
printers are getting IP address from dhcp without any problems.

Kind regards
Lukasz

"Meinolf Weber" wrote:

> Hello lukaszjg,
>
> Routers and switches used fixed ip configuration internal. Or what do you
> mean?
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
> > I'm using dhcp (windows 2003 SP1) on our DC. In dhcp all adresses are
> > excluded we only using reservations. Our routers and switches (cisco
> > and 3com) do not obtain addresses from reservation but PC and printers
> > are able to obtain configuration from dhcp. Any ideas why ?
> >
>
>
>

Statically assign the addresses and forget it. DHCP is serving no usefull
purpose if you are going to just make everything a Reservation. That is
more work than just statically assigning the addresses in the first place.

Do *not* make your LAN infrastucture equipment dependent on the "life" of a
DHCP Server. The LAN infrastructure needs to survive even if there is not
one single PC left running on the LAN.


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


"lukaszjg" <(E-Mail Removed)> wrote in message
newsD331C55-05D9-4E9A-AEAE-(E-Mail Removed)...
> Hi Meinolf
>
> Routers and switches are configure to obtain IP address from our local
> dhcp
> server so they are setup as a dhcp clients similar to our PC's and
> printers.
> In our local network we are running windows 2003 server with dhcp this is
> as
> well our domain controler.
>
> In Windows 2003 server dhcp all addresses in our local network are
> excluded
> from distribution and we crate reservation for our clients.
>
> My scope settings are similar to following:
> 172.16.0.1 172.16.15.254 address range for distribution
> 172.16.0.1 172.16.15.254 IP addresses excluded from distribution
>
> All our dhcp clients has got corresponding reservation in our dhcp server.
> I have reservation for our switches,routers,pc,printers.
>
> All addresses are excluded form distribution because we want to have
> strict
> control of our IP assignment. We want that our dhcp clients will always
> have
> the same IP settings given from dhcp.
>
> For some reason this does not seems to work for routers and switches. PC
> and
> printers are getting IP address from dhcp without any problems.
>
> Kind regards
> Lukasz
>
> "Meinolf Weber" wrote:
>
>> Hello lukaszjg,
>>
>> Routers and switches used fixed ip configuration internal. Or what do you
>> mean?
>>
>> Best regards
>>
>> Meinolf Weber
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers
>> no rights.
>> ** Please do NOT email, only reply to Newsgroups
>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>
>> > I'm using dhcp (windows 2003 SP1) on our DC. In dhcp all adresses are
>> > excluded we only using reservations. Our routers and switches (cisco
>> > and 3com) do not obtain addresses from reservation but PC and printers
>> > are able to obtain configuration from dhcp. Any ideas why ?
>> >
>>
>>
>>

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

> Do *not* make your LAN infrastucture equipment dependent on the "life" of
> a DHCP Server. The LAN infrastructure needs to survive even if there is
> not one single PC left running on the LAN.

Excellent point, Phillip. The infrastructure backbone MUST be able to run in
order to get the rest of it back up during an emergency.

Ace

Because e.g 3com switches 4500 are by default dhcp clients is very useful to
assign them ip address through dhcp because then we can access them through
web interface or telnet and there is no need to access them via console cable.
So you can put device in network cabinet, assign them ip address via dhcp
server and configure over network.

Problem with ip assignment for routers and switches have arisen since we
migrate our dhcp server from red hat 3 enterprise to windows 2003, and only
happen when we have reservation for routers and switches. If there is no
reservation, and you have some ip addresses for distribution routers/switches
are able to get ip address, with reservation for them setup windows 2003 dhcp
server do not respond for their discoveries messages.



"Ace Fekay [MVP Directory Services]" wrote:

>
> "Phillip Windell" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>
> > Do *not* make your LAN infrastucture equipment dependent on the "life" of
> > a DHCP Server. The LAN infrastructure needs to survive even if there is
> > not one single PC left running on the LAN.
>
> Excellent point, Phillip. The infrastructure backbone MUST be able to run in
> order to get the rest of it back up during an emergency.
>
> Ace
>
>
>

"lukaszjg" <(E-Mail Removed)> wrote in message
news:F55F7791-0934-4E3A-A1A7-(E-Mail Removed)...
> Because e.g 3com switches 4500 are by default dhcp clients is very useful
> to
> assign them ip address through dhcp because then we can access them
> through
> web interface or telnet and there is no need to access them via console
> cable.
> So you can put device in network cabinet, assign them ip address via dhcp
> server and configure over network.

Switches are somewhat irrelevant since they will still work without an IP#
at all.
Routers should never ever ever use DHCP so that the Routing Scheme of the
LAN is not destroyed when DHCP Problems arise. How is a router going to be a
"gateway" for a certain subnet or set of subnets if the IP# suddenly changes
due to a DHCP screwup?

The reason for these things to be set for DHCP "out of the box" is so you
can connect to them the *first* time,...and then while you are connected the
first time,....change the IP Config to something static.

> Problem with ip assignment for routers and switches have arisen since we
> migrate our dhcp server from red hat 3 enterprise to windows 2003, and
> only
> happen when we have reservation for routers and switches.

That kind of makes my point.

Guess how many times I have had problems similar to this with routers &
switches over the last ten years,.....zero. I statically assign them and
keep documentation records.

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

"lukaszjg" <(E-Mail Removed)> wrote in message
news:F55F7791-0934-4E3A-A1A7-(E-Mail Removed)...
> Because e.g 3com switches 4500 are by default dhcp clients is very useful
> to
> assign them ip address through dhcp because then we can access them
> through
> web interface or telnet and there is no need to access them via console
> cable.
> So you can put device in network cabinet, assign them ip address via dhcp
> server and configure over network.

I don't understand. You mean you can't access them via a web interface or
telnet if they don't have a DHCP assigned address? Maybe I'm missing
something, but in my opinion, it honestly doesn't make sense.

A router is a fixed device part of the network infrastructure. It should
always have a statically assigned address.

For what it's worth, I have honestly never seen in my 20+ years in the
field, not counting my mainframe experience prior to that, a router assigned
a DHCP address on the LAN side, reservation or not. I would view it as akin
to a DNS server having a DHCP assigned address.

For all intents and purposes, I would suggest and recommend to statically
assign both the router and switches. It's an industry "best practice."


>
> Problem with ip assignment for routers and switches have arisen since we
> migrate our dhcp server from red hat 3 enterprise to windows 2003, and
> only
> happen when we have reservation for routers and switches.

Maybe the Windows DHCP service is trying to tell you subtly that it should
be done?

> If there is no
> reservation, and you have some ip addresses for distribution
> routers/switches
> are able to get ip address, with reservation for them setup windows 2003
> dhcp
> server do not respond for their discoveries messages.
>

Possibly on a different port or using a different method? YOu would need to
check the router's documentation.



Ace