DHCP Superscope

Hi guys,

I was briefly trying to find it in older topics so if there is already
answer dont crycify me.

Description:
Our network has XX subnets in XX locations (VPN, routers, ...) in star
topology.
We have configured one DHCP Superscope with scope for each subnet in central
location and DHCP relay on routers which is working fine (WINS also in
central location).

Problem:
Problem is when notebook user travels to different location and tries to
connect from there. He always get "old IP" from previous subnet.

Solution:
We tried to shorter IP adress lease time, clear DHCP/DNS/WINS clearing for
old IP but nothing helped.
Right now we see only option to configure all router as local DHCP server
and forget Superscoping but maybe there is another way.

Any ideas?

why are you forwarding dhcp requests thru your routers? That's a problem
why superscope instead of planning ahead and going to a higher class of
subnet?

Could you please explain it for me?



"Joshua Bolton" wrote:

> why are you forwarding dhcp requests thru your routers? That's a problem
> why superscope instead of planning ahead and going to a higher class of
> subnet?

Get rid of the SuperScope!!

They are for Multi-Netting and you are not Multi-Netting.

Create separate, distinct, independent Scopes. One for each subnet.

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


"Svatos, Jan" <(E-Mail Removed)> wrote in message
news:BD33D053-5F2D-446D-A79C-(E-Mail Removed)...
> Hi guys,
>
> I was briefly trying to find it in older topics so if there is already
> answer dont crycify me.
>
> Description:
> Our network has XX subnets in XX locations (VPN, routers, ...) in star
> topology.
> We have configured one DHCP Superscope with scope for each subnet in
> central
> location and DHCP relay on routers which is working fine (WINS also in
> central location).
>
> Problem:
> Problem is when notebook user travels to different location and tries to
> connect from there. He always get "old IP" from previous subnet.
>
> Solution:
> We tried to shorter IP adress lease time, clear DHCP/DNS/WINS clearing for
> old IP but nothing helped.
> Right now we see only option to configure all router as local DHCP server
> and forget Superscoping but maybe there is another way.
>
> Any ideas?
>

OK, I will try it but how to ensure that to devices on dhcp subnet will not
be assigned wrong ip?

"Phillip Windell" wrote:

> Get rid of the SuperScope!!
>
> They are for Multi-Netting and you are not Multi-Netting.
>
> Create separate, distinct, independent Scopes. One for each subnet.
>
> --
> 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.
> -----------------------------------------------------
>
>
> "Svatos, Jan" <(E-Mail Removed)> wrote in message
> news:BD33D053-5F2D-446D-A79C-(E-Mail Removed)...
> > Hi guys,
> >
> > I was briefly trying to find it in older topics so if there is already
> > answer dont crycify me.
> >
> > Description:
> > Our network has XX subnets in XX locations (VPN, routers, ...) in star
> > topology.
> > We have configured one DHCP Superscope with scope for each subnet in
> > central
> > location and DHCP relay on routers which is working fine (WINS also in
> > central location).
> >
> > Problem:
> > Problem is when notebook user travels to different location and tries to
> > connect from there. He always get "old IP" from previous subnet.
> >
> > Solution:
> > We tried to shorter IP adress lease time, clear DHCP/DNS/WINS clearing for
> > old IP but nothing helped.
> > Right now we see only option to configure all router as local DHCP server
> > and forget Superscoping but maybe there is another way.
> >
> > Any ideas?
> >
>
>
>

"Svatos, Jan" <(E-Mail Removed)> wrote in message
news741500A-B05C-4176-A099-(E-Mail Removed)...
> OK, I will try it but how to ensure that to devices on dhcp subnet will
> not
> be assigned wrong ip?

The DHCP Server will know what IP segment they came from because the Router
provides that information when it relays the DHCP Query. The DHCP will give
them an IP# from the Scope that matches the segment they came from.

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