DHCP server delay in coming up authorized

[Malcolm Hein]

Hi,

This is more DHCP than AD.

I have AD-enabled Win 2000 Server set up on a Dell
PowerEdge 600SC. When I access my DHCP snap-in, it takes
about seconds for DHCP to authorize and it receives an
automatic IP address (169.254...). As a server I have it
set for a static reserved IP address (which shows up
correctly everywhere (ipconfig, etc.).

My two questions are: If this machine has been running for
half an hour and I look at DHCP, shouldn't it already be
authorized (green arrow up instead of hourglass)? And why
is an automatic IP address appearing in parentheses next
to it?

I feel like rebuilding the server from scratch, but that
would be very intensive.

HELP!

Thank you,

Malcolm Hein

 

[Henrik Johansson]

169.254.x.y is APIPA and happens when a DHCP client can't get IP-settings
from a server.
Wrong way to try to let the DHCP-server lease IP-settings from itself.
The DHCP-server shall have static configured IP, and you nead to enter the
settings manual.

 

[Dale Wyman]

You should "statically assign" and IP-Address to your DHCP
server and simple exclude that IP Address from any scopes
you have created.

The fact that you are getting a 169.254.x.x address
indicates that APIPA is supplying your server with that
address (DISABLE APIPA)on your DHCP server!!

Dale