Re: dhcp-superscope-wifi-pocketpc

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Jesse Hottle (jesse_at_omnicity.net)
Date: 03/08/04 

Date: Mon, 8 Mar 2004 13:18:15 -0800

Can you tell me how to get the DHCP server to assign IP
from the superscope form all the scopes defined?

I have a CISCO switch with multiple subnets defined, but
the DHCP sever will not assigned IP unless the request is
detected from a directly connected subnet.

I have a (.252) subnet defined on the primary interface ,
and two class "c" blocks on the other interfaces. The dhco
is receiving the request from the gateway on the (.252)
block and therefore will not grant an IP request.

Any iodea or work arounds for this issue?

Thanks,

Jesse Hottle
Omnicity, Inc.
>-----Original Message-----
>I appreciate your response.
>
>I think I'm in big trouble because I created the
superscope to serve
>different subnets in branches in which I don't have a
server locally
>installed. The superscope is configured in one DHCP
server in our Main
>Office.
>
>We configured DHCP Relay in our Cisco router (IP Helper
Address) so IP
>leases could be routed through it. It works OK for
desktop PCs but, as I
>said, the problem comes when mobile devices change from
one scope to another
>(some of them connect to 2 or 3 different branches per
day).
>
>If I eliminate the superscope I won't be able to serve
different subnets.
>There is no plan to buy new servers nor licenses in short
term!
>
>Do you have any tip to help me work this out?
>
>
>
>
>"Michael Johnston [MSFT]" <michjohn@online.microsoft.com>
wrote in message
>news:1wOVpJ#9DHA.704@cpmsftngxa07.phx.gbl...
>> This is caused by the superscope. The superscope
allows the DHCP server
>to assign the clients an address from any of the
>> scopes within the superscope. Since the clients
already have a leave in a
>scope within the superscope, DHCP will assign the
>> client the previously used address. If this isn't
desired behavior, you
>need to get rid of the superscope.
>>
>> Thank you,
>> Mike Johnston
>> Microsoft Network Support
>> --
>>
>> This posting is provided "AS IS" with no warranties,
and confers no
>rights. Use of included script samples are subject to the
>> terms specified at
>> http://www.microsoft.com/info/cpyright.htm
>>
>> Note: For the benefit of the community-at-large, all
responses to this
>message are best directed to the newsgroup/thread from
>> which they originated.
>>
>>
>>
>
>
>.
>

Relevant Pages

  • Re: scope with dynamin NIC IP ?
    ... what it is is that the server is up running Monday to Friday. ... offices to use the LinkSys router by DHCP. ... While I was wrong in assuming a superscope would fix this.... ...
    (microsoft.public.windows.server.setup)
  • Re: scope with dynamin NIC IP ?
    ... what it is is that the server is up running Monday to Friday. ... offices to use the LinkSys router by DHCP. ... While I was wrong in assuming a superscope would fix this.... ...
    (microsoft.public.win2000.ras_routing)
  • Re: scope with dynamin NIC IP ?
    ... what it is is that the server is up running Monday to Friday. ... offices to use the LinkSys router by DHCP. ... While I was wrong in assuming a superscope would fix this.... ...
    (microsoft.public.windows.server.networking)
  • Re: scope with dynamin NIC IP ?
    ... what it is is that the server is up running Monday to Friday. ... offices to use the LinkSys router by DHCP. ... While I was wrong in assuming a superscope would fix this.... ...
    (microsoft.public.windows.server.general)
  • 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)