Re: dhcp only offers IP for one subnet

From: Terry G (tgowett_at_yahoo.com)
Date: 06/09/04 

Date: 8 Jun 2004 17:31:59 -0700

"Phillip Windell" <@.> wrote in message news:<untvx3WTEHA.3768@TK2MSFTNGP11.phx.gbl>...
> "Terry G" <tgowett@yahoo.com> wrote in message
> news:14e1823d.0406071531.770334b1@posting.google.com...
> > I set up a superscope with appropriate subnetting as below:
> > x.x.10.1-126 255.192
> > x.x.11.1-126 255.192
> > x.x.13.1-190 255.128
> > x.x.14.1-190 255.128
> > x.x.16.126-190 255.192
> > x.x.18.65-126 255.192
> > The problem: The DHCP server only gives out addresses for the
> > 53.1-126 range.
>
> Superscopes take all the addresses in all the child scopes and make them
> behave as on huge scope for one huge subnet. The solution is,...don't use
> Superscopes. Use a separate scope for each subnet and set the router that is
> between the subnets to forward DHCP request to the proper DHCP Server and
> all will be well. The router supplies information in the request it forwards
> so the DHCP server knows which subnet the request came from and grant a
> proper address for the proper subnet.
>
> I was fooled by the Superscope concept myself and also did it wrong the
> first time.
>
> Make sure the reghack is corrected.

I just tried it with no change. Scopes removed from superscope,
superscope deleted, ip helper-address set on the router (tried it as
forwarded to server address and to all interfaces), reghack appears to
have been removed when I set the specific gateways. Server does not
appear to make any offers. In past half hour server stats shows 70+
discovers, 0 offers, 5 requests, 0 acks, 1 nack, 2 declines, 0
releases. Addresses are available, but not in 13.x range. When I put
the current production dhcp on and have helper-address on router
pointed to the new (problem) dhcp server, the new makes no offers and
the production still hands out an IP address.

Relevant Pages

  • Re: Whats the benefit of using superscopes?
    ... A superscope is a collection of individual scopes that can be ... A superscope is actually a collection of individual scopes. ... Place DHCP clients from multiple network IDs on the same ... The superscope will allow the DHCP Server to answer requests from ...
    (microsoft.public.windows.server.networking)
  • Re: DHCP Migration
    ... You get the one configured the way you like but leave the scopes ... You would have a separate scope for each subnet. ... to the proper DHCP Server. ... configured and activated on the DHCP Server and the Router was forwarding ...
    (microsoft.public.windows.server.networking)
  • Re: DHCP relay, superscope and laptops
    ... each of which has it's own subnet. ... The Switch then acts as a DHCP relay, ... relaying DHCP requests to a central DHCP server, ... What we did as a workaround, was that we created one superscope for each ...
    (microsoft.public.windows.server.networking)
  • Re: DHCP Migration
    ... You would have a separate scope for each subnet. ... >> to the proper DHCP Server. ... When you are ready to active the scopes shut ... >> configured and activated on the DHCP Server and the Router was ...
    (microsoft.public.windows.server.networking)
  • Re: Vlan, DHCP and moving computers problem
    ... DHCP Server does not differentiate between the two member scopes. ... I see 3 examples of superscope. ... >> Chris Edson ... >>> clients gets an address from the wrong subnet and gets cut off on the ...
    (microsoft.public.win2000.networking)
Loading