Problems moving DHCP client among subnets

I've had a long running problem with DHCP clients moving among different
subnets and being able to pickup a new ip at the new destination subnet.

We have our leases set at 8 days. Today I had a notebook that was in another
subnet yesteday and picked up an IP. Today, I powered it on and it was still
trying to get ahold of the old IP. Looking at the DHCP console, I still see
the old IP there. I can delete that IP, ipconfig /release and /renew and the
client still goes back to trying to get the old IP.

So we tried adding the Scope option 002 Microsoft Release DHCP Lease On
Shutdown Option. This doesn't work either. The only thing that works is to
statically assign an IP in the new subnet.

I'm thinking maybe I need to set the DHCP lease duration to maybe 1 day? Or
maybe it has to do with the fact that we have many of our DHCP scopes on one
server in a Superscope.

Has anyone grappled with this issue?
--
Sandy Wood
Orange County District Attorney

"Sandy Wood" <(E-Mail Removed)> wrote in message
news:16FB9466-088A-4805-B762-(E-Mail Removed)...
> maybe it has to do with the fact that we have many of our DHCP scopes on
> one
> server in a Superscope.

That is exactly why.
Get rid of the Superscope! That is not what they are for. Move your Scopes
out of the Superscope and leave them be as independent distinct Scopes. The
Superscope will dissapear after the last one is removed.

Superscopes are for Multi-Netting, at least that was the most practical use
of them....you are not Multi-Netting,...neither is 99% of anyone else.
Multi-Nets are a thing of the past and have mostly been made obsolete by the
invention of VLANs. MS could remove the superscope ability of the DHCP
Service and life would continue on.

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

Thanks for the info. I think we'll need to work on getting rid of the
SuperScopes to eliminate the problem.
--
Sandy Wood
Orange County District Attorney


"Phillip Windell" wrote:

>
> "Sandy Wood" <(E-Mail Removed)> wrote in message
> news:16FB9466-088A-4805-B762-(E-Mail Removed)...
> > maybe it has to do with the fact that we have many of our DHCP scopes on
> > one
> > server in a Superscope.
>
> That is exactly why.
> Get rid of the Superscope! That is not what they are for. Move your Scopes
> out of the Superscope and leave them be as independent distinct Scopes. The
> Superscope will dissapear after the last one is removed.
>
> Superscopes are for Multi-Netting, at least that was the most practical use
> of them....you are not Multi-Netting,...neither is 99% of anyone else.
> Multi-Nets are a thing of the past and have mostly been made obsolete by the
> invention of VLANs. MS could remove the superscope ability of the DHCP
> Service and life would continue on.
>
> --
> 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.
> -----------------------------------------------------
>
>
>