DHCP server not issuing IP Addresses

I have setup a new W2K3 DC server with DHCP, WINS and DNS running. I tried
logging into the domain and an IP Address from the pool is not getting
assigned. A 169. address is getting assigned. Why is this? What do I need
to do to resolve this?

Hi,

Did you setup address reservations and an address pool in your scope? With
DHCP GUI?

CreateWindow
http://justpageprobe.com
The FREE Web page utility you always wanted.
Monitor your enterprise Web Servers.
Keep your router connected.
Email your IP to where you need it


"Rachel L Chipman" <(E-Mail Removed)> wrote in
message news:6B7D03DE-9FFB-4D8E-965B-(E-Mail Removed)...
>I have setup a new W2K3 DC server with DHCP, WINS and DNS running. I tried
> logging into the domain and an IP Address from the pool is not getting
> assigned. A 169. address is getting assigned. Why is this? What do I
> need
> to do to resolve this?

As well as activating the scope in DHCP you will need to authorize the
DHCP server in Active Directory if it is a DC.

"CreateWindow" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) ...
> Hi,
>
> Did you setup address reservations and an address pool in your scope? With
> DHCP GUI?
>
> CreateWindow
> http://justpageprobe.com
> The FREE Web page utility you always wanted.
> Monitor your enterprise Web Servers.
> Keep your router connected.
> Email your IP to where you need it
>
>
> "Rachel L Chipman" <(E-Mail Removed)> wrote in
> message news:6B7D03DE-9FFB-4D8E-965B-(E-Mail Removed)...
>>I have setup a new W2K3 DC server with DHCP, WINS and DNS running. I
>>tried
>> logging into the domain and an IP Address from the pool is not getting
>> assigned. A 169. address is getting assigned. Why is this? What do I
>> need
>> to do to resolve this?
>
>

Yes, an Address Pool was setup and the scope was activated/authorized.

"Bill Grant" wrote:

> As well as activating the scope in DHCP you will need to authorize the
> DHCP server in Active Directory if it is a DC.
>
> "CreateWindow" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed) ...
> > Hi,
> >
> > Did you setup address reservations and an address pool in your scope? With
> > DHCP GUI?
> >
> > CreateWindow
> > http://justpageprobe.com
> > The FREE Web page utility you always wanted.
> > Monitor your enterprise Web Servers.
> > Keep your router connected.
> > Email your IP to where you need it
> >
> >
> > "Rachel L Chipman" <(E-Mail Removed)> wrote in
> > message news:6B7D03DE-9FFB-4D8E-965B-(E-Mail Removed)...
> >>I have setup a new W2K3 DC server with DHCP, WINS and DNS running. I
> >>tried
> >> logging into the domain and an IP Address from the pool is not getting
> >> assigned. A 169. address is getting assigned. Why is this? What do I
> >> need
> >> to do to resolve this?
> >
> >
>
>
>

I was able to resolve this issue and wanted to post what the problem was.
As it turned out, the windows firewall was enabled and started on the
server. Once that was stopped and disabled, IP Address were being assigned.

"Rachel L Chipman" wrote:

> Yes, an Address Pool was setup and the scope was activated/authorized.
>
> "Bill Grant" wrote:
>
> > As well as activating the scope in DHCP you will need to authorize the
> > DHCP server in Active Directory if it is a DC.
> >
> > "CreateWindow" <(E-Mail Removed)> wrote in message
> > news:(E-Mail Removed) ...
> > > Hi,
> > >
> > > Did you setup address reservations and an address pool in your scope? With
> > > DHCP GUI?
> > >
> > > CreateWindow
> > > http://justpageprobe.com
> > > The FREE Web page utility you always wanted.
> > > Monitor your enterprise Web Servers.
> > > Keep your router connected.
> > > Email your IP to where you need it
> > >
> > >
> > > "Rachel L Chipman" <(E-Mail Removed)> wrote in
> > > message news:6B7D03DE-9FFB-4D8E-965B-(E-Mail Removed)...
> > >>I have setup a new W2K3 DC server with DHCP, WINS and DNS running. I
> > >>tried
> > >> logging into the domain and an IP Address from the pool is not getting
> > >> assigned. A 169. address is getting assigned. Why is this? What do I
> > >> need
> > >> to do to resolve this?
> > >
> > >
> >
> >
> >

Glad to hear you have sorted it out. Thanks for the update.

"Rachel L Chipman" <(E-Mail Removed)> wrote in
message news:8B248BFC-B454-4ECA-A3E3-(E-Mail Removed)...
>I was able to resolve this issue and wanted to post what the problem was.
> As it turned out, the windows firewall was enabled and started on the
> server. Once that was stopped and disabled, IP Address were being
> assigned.
>
> "Rachel L Chipman" wrote:
>
>> Yes, an Address Pool was setup and the scope was activated/authorized.
>>
>> "Bill Grant" wrote:
>>
>> > As well as activating the scope in DHCP you will need to authorize
>> > the
>> > DHCP server in Active Directory if it is a DC.
>> >
>> > "CreateWindow" <(E-Mail Removed)> wrote in message
>> > news:(E-Mail Removed) ...
>> > > Hi,
>> > >
>> > > Did you setup address reservations and an address pool in your scope?
>> > > With
>> > > DHCP GUI?
>> > >
>> > > CreateWindow
>> > > http://justpageprobe.com
>> > > The FREE Web page utility you always wanted.
>> > > Monitor your enterprise Web Servers.
>> > > Keep your router connected.
>> > > Email your IP to where you need it
>> > >
>> > >
>> > > "Rachel L Chipman" <(E-Mail Removed)> wrote
>> > > in
>> > > message news:6B7D03DE-9FFB-4D8E-965B-(E-Mail Removed)...
>> > >>I have setup a new W2K3 DC server with DHCP, WINS and DNS running. I
>> > >>tried
>> > >> logging into the domain and an IP Address from the pool is not
>> > >> getting
>> > >> assigned. A 169. address is getting assigned. Why is this? What
>> > >> do I
>> > >> need
>> > >> to do to resolve this?
>> > >
>> > >
>> >
>> >
>> >

The 169 address is APIPA meaning that the DHCP server can't be contacted by
the client. The APIPA address is assigned automatically by XP when it can't
find any DHCP server and it keeps retrying DHCP every few minutes.

"Rachel L Chipman" <(E-Mail Removed)> wrote in
message news:6B7D03DE-9FFB-4D8E-965B-(E-Mail Removed)...
>I have setup a new W2K3 DC server with DHCP, WINS and DNS running. I tried
> logging into the domain and an IP Address from the pool is not getting
> assigned. A 169. address is getting assigned. Why is this? What do I
> need
> to do to resolve this?