PDA

View Full Version : DHCP and remote Laptops

Roger Crawford
I have a client who has 10 locations and we have a Superscope running on
DHCP for the 10 locations. If a laptop comes into the main store and aquires
a IP from the server when they go back to there remote location that laptop
will not aquire a IP from the IP Range it is in for that store but will try
to use the one it aquired in the main store. This is a Windows 2000 Server
that is the DC with 9 NT 4.0 BDC's

We have did a ipconfig /release when the laptop is taken off the main domain
and also have went into DHCP and deleted the IP from there and the laptop
still tries to use the one it aquired in the first place. Any thoughts on
what I need to look at here as the only cure is to statically set the IP on
the laptop when it is at that remote location? All sites are connected by
Frame Connections and Routers between the sites. Thanks

Roger Crawford
HTS


Marc Reynolds [MSFT]
You don't want to use a Superscope for your 10 locations, instead you should
have individual scopes for each subnet and configure your routers to use
bootp or DHCP relay.

DHCP Superscoping is used when you need to assign non-supernetted or
non-consecutive IP address subnets to the same physical segment. For
example, if you needed to assign 199.1.1.x and 201.2.2.x addresses to the
same physical network, you could use superscopes or if you needed to assign
199.1.0.x and 199.1.1.x and did not want to change the subnet mask to
support supernetting.

--

Thanks,
Marc Reynolds
Microsoft Technical Support

This posting is provided "AS IS" with no warranties, and confers no rights.


"Roger Crawford" wrote in message
news:eAAbKYC6DHA.2412@TK2MSFTNGP11.phx.gbl...
> I have a client who has 10 locations and we have a Superscope running on
> DHCP for the 10 locations. If a laptop comes into the main store and
aquires
> a IP from the server when they go back to there remote location that
laptop
> will not aquire a IP from the IP Range it is in for that store but will
try
> to use the one it aquired in the main store. This is a Windows 2000 Server
> that is the DC with 9 NT 4.0 BDC's
>
> We have did a ipconfig /release when the laptop is taken off the main
domain
> and also have went into DHCP and deleted the IP from there and the laptop
> still tries to use the one it aquired in the first place. Any thoughts on
> what I need to look at here as the only cure is to statically set the IP
on
> the laptop when it is at that remote location? All sites are connected by
> Frame Connections and Routers between the sites. Thanks
>
> Roger Crawford
> HTS
>
>


Roger Crawford
Ok let me rephrase this and see if it makes a difference or not but they had
10 Different scopes defined on the Server 10.32.x.x and 10.33.x.x and so on
and then I upgraded it to Windows 2000 from NT 4 and then I just left the
individually defined scopes as they where and put them all in a Superscope
on the advice of one of our other techs in-house. Same answer? I am just
trying to figure out why workstation in those separate locations get IP
renewals fine but the laptops do not when moved from location to location.
Thanks for any help. I have been after the people who manage the routers and
Frames to turn on DHCP Relay but so far they have been dragging there feet.

Roger Crawford
HTS

"Marc Reynolds [MSFT]" wrote in message
news:OUGQoVD6DHA.2064@TK2MSFTNGP11.phx.gbl...
> You don't want to use a Superscope for your 10 locations, instead you
should
> have individual scopes for each subnet and configure your routers to use
> bootp or DHCP relay.
>
> DHCP Superscoping is used when you need to assign non-supernetted or
> non-consecutive IP address subnets to the same physical segment. For
> example, if you needed to assign 199.1.1.x and 201.2.2.x addresses to the
> same physical network, you could use superscopes or if you needed to
assign
> 199.1.0.x and 199.1.1.x and did not want to change the subnet mask to
> support supernetting.
>
> --
>
> Thanks,
> Marc Reynolds
> Microsoft Technical Support
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
>
> "Roger Crawford" wrote in message
> news:eAAbKYC6DHA.2412@TK2MSFTNGP11.phx.gbl...
> > I have a client who has 10 locations and we have a Superscope running on
> > DHCP for the 10 locations. If a laptop comes into the main store and
> aquires
> > a IP from the server when they go back to there remote location that
> laptop
> > will not aquire a IP from the IP Range it is in for that store but will
> try
> > to use the one it aquired in the main store. This is a Windows 2000
Server
> > that is the DC with 9 NT 4.0 BDC's
> >
> > We have did a ipconfig /release when the laptop is taken off the main
> domain
> > and also have went into DHCP and deleted the IP from there and the
laptop
> > still tries to use the one it aquired in the first place. Any thoughts
on
> > what I need to look at here as the only cure is to statically set the IP
> on
> > the laptop when it is at that remote location? All sites are connected
by
> > Frame Connections and Routers between the sites. Thanks
> >
> > Roger Crawford
> > HTS
> >
> >
>
>