moved dhcp from w2k to w2k3-clients unable to connect to dhcp server

Hi,
We moved our DHCP service from a domain controller running Windows 2000
Server to another domain controller running Windows 2003 Server. We used
KB325473 as a guide. We have a W2k3 domain.

Now our PCs (clients) cannot obtain an IP address via DHCP. IPCONFIG /renew
returns: unable to cantact your dhcp server.
This affects all PCs using dhcp (XP and Vista)
When i look at DHCP on the server it appears to be OK but the statistics
indicates zero lease requests. I think that the PCs are still looking at
the old server for DHCP.
What do i need to do?
Thanks. TonyV

Hello Tony,

Is the server authorized in AD?

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

> Hi,
> We moved our DHCP service from a domain controller running Windows
> 2000
> Server to another domain controller running Windows 2003 Server. We
> used
> KB325473 as a guide. We have a W2k3 domain.
> Now our PCs (clients) cannot obtain an IP address via DHCP. IPCONFIG
> /renew
> returns: unable to cantact your dhcp server.
> This affects all PCs using dhcp (XP and Vista)
> When i look at DHCP on the server it appears to be OK but the
> statistics
> indicates zero lease requests. I think that the PCs are still looking
> at
> the old server for DHCP.
> What do i need to do?
> Thanks. TonyV

Unauthorize the DHCP Service on the old machine.
Then...
Uninstall the DHCP Service from the old machine.

Clients will always try the last DHCP they used. Then if that fails they
will "broadcast" to find another one.

Make sure the new DHCP Sever is Authorized
Make sure the Scopes on the new one are Activated


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

"Tony Villani" <(E-Mail Removed)> wrote in message
news:500DAEEB-C3CD-4A97-BAC1-(E-Mail Removed)...
> Hi,
> We moved our DHCP service from a domain controller running Windows 2000
> Server to another domain controller running Windows 2003 Server. We used
> KB325473 as a guide. We have a W2k3 domain.
>
> Now our PCs (clients) cannot obtain an IP address via DHCP. IPCONFIG
> /renew returns: unable to cantact your dhcp server.
> This affects all PCs using dhcp (XP and Vista)
> When i look at DHCP on the server it appears to be OK but the statistics
> indicates zero lease requests. I think that the PCs are still looking at
> the old server for DHCP.
> What do i need to do?
> Thanks. TonyV

Yes the server is authorized as confirmed in the DHCP snap-in
--
Tony Villani


"Meinolf Weber" wrote:

> Hello Tony,
>
> Is the server authorized in AD?
>
> 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
>
> > Hi,
> > We moved our DHCP service from a domain controller running Windows
> > 2000
> > Server to another domain controller running Windows 2003 Server. We
> > used
> > KB325473 as a guide. We have a W2k3 domain.
> > Now our PCs (clients) cannot obtain an IP address via DHCP. IPCONFIG
> > /renew
> > returns: unable to cantact your dhcp server.
> > This affects all PCs using dhcp (XP and Vista)
> > When i look at DHCP on the server it appears to be OK but the
> > statistics
> > indicates zero lease requests. I think that the PCs are still looking
> > at
> > the old server for DHCP.
> > What do i need to do?
> > Thanks. TonyV
>
>
>

Good suggestions. I had done most of this per KB325473 except that i had not
done an uninstall of DHCP but had Disabled the service.
I did the uninstall just now and restarted the old machine, to no avail.
I'm willing to try more ideas...
--
Tony Villani


"Phillip Windell" wrote:

> Unauthorize the DHCP Service on the old machine.
> Then...
> Uninstall the DHCP Service from the old machine.
>
> Clients will always try the last DHCP they used. Then if that fails they
> will "broadcast" to find another one.
>
> Make sure the new DHCP Sever is Authorized
> Make sure the Scopes on the new one are Activated
>
>
> --
> 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.
> -----------------------------------------------------
>
> "Tony Villani" <(E-Mail Removed)> wrote in message
> news:500DAEEB-C3CD-4A97-BAC1-(E-Mail Removed)...
> > Hi,
> > We moved our DHCP service from a domain controller running Windows 2000
> > Server to another domain controller running Windows 2003 Server. We used
> > KB325473 as a guide. We have a W2k3 domain.
> >
> > Now our PCs (clients) cannot obtain an IP address via DHCP. IPCONFIG
> > /renew returns: unable to cantact your dhcp server.
> > This affects all PCs using dhcp (XP and Vista)
> > When i look at DHCP on the server it appears to be OK but the statistics
> > indicates zero lease requests. I think that the PCs are still looking at
> > the old server for DHCP.
> > What do i need to do?
> > Thanks. TonyV
>
>
>

Disabling the Service should have worked. You just have to make sure that
there is nothing there to "answer" the Client which forces it to broadcast
for another DHCP.

I have heard of one other guy that had some problems like that and he had to
set the Client to a Static IP config first, and then set it back to DHCP.
Another thing to try is to right-click on the connection in Net'Places and
do a "repair" on the connection.

Those are just guesses, but it is all I can think of at the moment.

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


"Tony Villani" <(E-Mail Removed)> wrote in message
news4627DA1-7296-424E-B49B-(E-Mail Removed)...
> Good suggestions. I had done most of this per KB325473 except that i had
> not
> done an uninstall of DHCP but had Disabled the service.
> I did the uninstall just now and restarted the old machine, to no avail.
> I'm willing to try more ideas...
> --
> Tony Villani
>
>
> "Phillip Windell" wrote:
>
>> Unauthorize the DHCP Service on the old machine.
>> Then...
>> Uninstall the DHCP Service from the old machine.
>>
>> Clients will always try the last DHCP they used. Then if that fails they
>> will "broadcast" to find another one.
>>
>> Make sure the new DHCP Sever is Authorized
>> Make sure the Scopes on the new one are Activated
>>
>>
>> --
>> 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.
>> -----------------------------------------------------
>>
>> "Tony Villani" <(E-Mail Removed)> wrote in message
>> news:500DAEEB-C3CD-4A97-BAC1-(E-Mail Removed)...
>> > Hi,
>> > We moved our DHCP service from a domain controller running Windows 2000
>> > Server to another domain controller running Windows 2003 Server. We
>> > used
>> > KB325473 as a guide. We have a W2k3 domain.
>> >
>> > Now our PCs (clients) cannot obtain an IP address via DHCP. IPCONFIG
>> > /renew returns: unable to cantact your dhcp server.
>> > This affects all PCs using dhcp (XP and Vista)
>> > When i look at DHCP on the server it appears to be OK but the
>> > statistics
>> > indicates zero lease requests. I think that the PCs are still looking
>> > at
>> > the old server for DHCP.
>> > What do i need to do?
>> > Thanks. TonyV
>>
>>
>>

Those are great ideas as well unfortuntaely I have tried them all and the
problem persists.
I'm thinking that we might have a corrupt database??? Does anyone know if
you can recreate a scope without wreaking havoc on the network???
Thanks.
--
Tony Villani


"Phillip Windell" wrote:

> Disabling the Service should have worked. You just have to make sure that
> there is nothing there to "answer" the Client which forces it to broadcast
> for another DHCP.
>
> I have heard of one other guy that had some problems like that and he had to
> set the Client to a Static IP config first, and then set it back to DHCP.
> Another thing to try is to right-click on the connection in Net'Places and
> do a "repair" on the connection.
>
> Those are just guesses, but it is all I can think of at the moment.
>
> --
> 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.
> -----------------------------------------------------
>
>
> "Tony Villani" <(E-Mail Removed)> wrote in message
> news4627DA1-7296-424E-B49B-(E-Mail Removed)...
> > Good suggestions. I had done most of this per KB325473 except that i had
> > not
> > done an uninstall of DHCP but had Disabled the service.
> > I did the uninstall just now and restarted the old machine, to no avail.
> > I'm willing to try more ideas...
> > --
> > Tony Villani
> >
> >
> > "Phillip Windell" wrote:
> >
> >> Unauthorize the DHCP Service on the old machine.
> >> Then...
> >> Uninstall the DHCP Service from the old machine.
> >>
> >> Clients will always try the last DHCP they used. Then if that fails they
> >> will "broadcast" to find another one.
> >>
> >> Make sure the new DHCP Sever is Authorized
> >> Make sure the Scopes on the new one are Activated
> >>
> >>
> >> --
> >> 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.
> >> -----------------------------------------------------
> >>
> >> "Tony Villani" <(E-Mail Removed)> wrote in message
> >> news:500DAEEB-C3CD-4A97-BAC1-(E-Mail Removed)...
> >> > Hi,
> >> > We moved our DHCP service from a domain controller running Windows 2000
> >> > Server to another domain controller running Windows 2003 Server. We
> >> > used
> >> > KB325473 as a guide. We have a W2k3 domain.
> >> >
> >> > Now our PCs (clients) cannot obtain an IP address via DHCP. IPCONFIG
> >> > /renew returns: unable to cantact your dhcp server.
> >> > This affects all PCs using dhcp (XP and Vista)
> >> > When i look at DHCP on the server it appears to be OK but the
> >> > statistics
> >> > indicates zero lease requests. I think that the PCs are still looking
> >> > at
> >> > the old server for DHCP.
> >> > What do i need to do?
> >> > Thanks. TonyV
> >>
> >>
> >>
>
>
>

"Tony Villani" <(E-Mail Removed)> wrote in message
news:270A1E76-2F1E-47B5-BED3-(E-Mail Removed)...
> Those are great ideas as well unfortuntaely I have tried them all and the
> problem persists.
> I'm thinking that we might have a corrupt database??? Does anyone know if
> you can recreate a scope without wreaking havoc on the network???

Others might have other ideas, but I wouldn't be afraid to do that. Clients
always ask for the same IP# everytime, and they almost always get it. So
that keeps the chance of IP conficts fairly low. The problem is only the
ones that are turned off for a long period of time (days, weeks) during
which other "new" machines were added that "stole" the address while they
were turned off. This forces them to get a new config when they are turned
back on.

You might want to wait for a second opinion.

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

We identified a potential conflict with dhcp running on a server that acts as
an Ardence server. We built another W2K3 server, ran netsh to import the
scope and now dhcp work as expected. Thank you to all for your time and
suggestions.
Tony Villani
--
Tony Villani


"Phillip Windell" wrote:

> "Tony Villani" <(E-Mail Removed)> wrote in message
> news:270A1E76-2F1E-47B5-BED3-(E-Mail Removed)...
> > Those are great ideas as well unfortuntaely I have tried them all and the
> > problem persists.
> > I'm thinking that we might have a corrupt database??? Does anyone know if
> > you can recreate a scope without wreaking havoc on the network???
>
> Others might have other ideas, but I wouldn't be afraid to do that. Clients
> always ask for the same IP# everytime, and they almost always get it. So
> that keeps the chance of IP conficts fairly low. The problem is only the
> ones that are turned off for a long period of time (days, weeks) during
> which other "new" machines were added that "stole" the address while they
> were turned off. This forces them to get a new config when they are turned
> back on.
>
> You might want to wait for a second opinion.
>
> --
> 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.
> -----------------------------------------------------
>
>
>