Geography is meaningless, the DHCP setup doesn't care if they are 500 miles
away or 50 feet away in the next room.
However the system would be better off with a DHCP at each location that
serves the particular subnets at that location. You don't want a WAN link
to go down because someone forty miles away cut a line with a backhoe and
leave the remote machines "helpless" without a DHCP to get their network
configuration from. Remote networks need to be designed so they are at least
semi-independent and can at least function to a certain degree even if they
are cut off from the outside world.
--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
"morgan" <(E-Mail Removed)> wrote in message
news:2428AA44-EB89-4366-B79A-(E-Mail Removed)...
> Phillip,
>
> even though these are physically remote location?
>
>
>
> "Phillip Windell" wrote:
>
> > Get rid of the Superscope. Run a separate scope for each subnet. Do
some
> > research on the purpose of a Superscope and you will find they are not
for
> > what you are doing. They make all the scopes within them behave as a
single
> > scope. I believe they are also used when multiple subnets run on the
same
> > logical "wire" although I am not that familiar with doing it that way
and
> > consider it a bad idea in the first place.
> >
> > --
> >
> > Phillip Windell [MCP, MVP, CCNA]
> > www.wandtv.com
> >
> >
> > "Morgan" <(E-Mail Removed)> wrote in message
> > news:B1ED7B2C-8DB2-4DFF-876A-(E-Mail Removed)...
> > > I have a Win2k server running DHCP configured for a superscope for
four
> > > different subnets.
> > >
> > > DHCP work over the router at every location no problem.
> > > But for the remote user after go from one location to another
> > > DHCP will not release it keep the same address from the previous
location
> > > even after doing an Ipconfig /release and /renew , same IP coms up.
> > >
> > > please advise
> >
> >
> >