W2K3 Servers getting IP address from DHCP?

Is there anywhere a 'best practice' document etc that says it's OK to assign
IP addresses to W2K3 servers from DHCP? I'm planning to reserve the addresses
by MAC-assignment, so that we get fixed IP addressing, but centrally managed
from the DHCP servers, and thereby saving us from having to manually enter
the IP address configuration by hand.

(When your servers have 4 NICs each and there are 1000 + servers, manually
setting up IP is a bit tiresesome....)

I know a DHCP server cannot be a DHCP client, and I can possibly accept an
argument that AD controllers, and maybe ISA servers might need static IP
setups but everything else surely should be assigned from DHCP reservations??



thanks....

Hello,

i would recommand long lease for servers (10 days ?) in case of DC failure.

You may get issue if both are true:
-DHCP server is down
-gateway can't be reached by ICMP

The DCHP client will think your server aren't on the network anymore, and
will put it back in 169X.X.X

Change in DHCP Client Behavior in Windows 2000
http://support.microsoft.com/default...b/255836/en-us
The Windows 2000-based DHCP client may use Automatic Private IP Addressing
(APIPA) for addressing if it is unable to reach a DHCP server and is also
unable to reach its default gateway

I don't know if it's the case with 2003.

The danger is there: if you get huge trouble, it may push you further down
by having Server going to Automatic Private IP Addressing (loosing it's dhcp
lease in clear)





--
Cordialement,
Mathieu CHATEAU
http://lordoftheping.blogspot.com


"Peter Moreton" <(E-Mail Removed)> wrote in message
news:46EB4C7D-CCDD-44DC-BC5B-(E-Mail Removed)...
> Is there anywhere a 'best practice' document etc that says it's OK to
> assign
> IP addresses to W2K3 servers from DHCP? I'm planning to reserve the
> addresses
> by MAC-assignment, so that we get fixed IP addressing, but centrally
> managed
> from the DHCP servers, and thereby saving us from having to manually enter
> the IP address configuration by hand.
>
> (When your servers have 4 NICs each and there are 1000 + servers, manually
> setting up IP is a bit tiresesome....)
>
> I know a DHCP server cannot be a DHCP client, and I can possibly accept an
> argument that AD controllers, and maybe ISA servers might need static IP
> setups but everything else surely should be assigned from DHCP
> reservations??
>
>
>
> thanks....
>

well,
the truth is somewhere on the middle, it depends the what type servers do
you have. On ip migrating on both you will have some problems.
Ussually i use static IP's on servers with exclusion on DHCP, but i dont
have so many servers on my lan.
On that number of servers with 4 nic's i think that the DHCP is the smallest
problem, because i think there it have to be more workstations, i think you
have to set more dhcp's , multiple subnets,etc.

if you set the dhcp option on servers check and alternate configuration on
ip config on them to avoid APIPA set.
--
Dragos CAMARA
MCSA Windows 2003 server


"Peter Moreton" wrote:

> Is there anywhere a 'best practice' document etc that says it's OK to assign
> IP addresses to W2K3 servers from DHCP? I'm planning to reserve the addresses
> by MAC-assignment, so that we get fixed IP addressing, but centrally managed
> from the DHCP servers, and thereby saving us from having to manually enter
> the IP address configuration by hand.
>
> (When your servers have 4 NICs each and there are 1000 + servers, manually
> setting up IP is a bit tiresesome....)
>
> I know a DHCP server cannot be a DHCP client, and I can possibly accept an
> argument that AD controllers, and maybe ISA servers might need static IP
> setups but everything else surely should be assigned from DHCP reservations??
>
>
>
> thanks....
>