Re: DHCP relay, superscope and laptops

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

>
> "Pall Bjornsson" <palli@xxxxxxx> wrote in message
> news:%23d2p7CNUFHA.2304@xxxxxxxxxxxxxxxxxxxxxxx
> > > Superscopes are only needed when the DHCP server offers
> > > addresses to a MULTINET.
> >
> > In my case I have a L3 Switch that splits my network in a few distinct
> VLANs
>
> Same here, we use an HP 5300XL
>
> > I was under the impression that if you had such a setup, you MUST have
> > superscope(s) set up, right ?
>
> No. No Superscopes. VLANs don't change anything, L3 Switches don't
change
> anything.


What Philip said -- just think of the routing (L3) between
different VLANS as passing through a router.

If effectively creates separate segments/cables -- the advantage it
you the admin get to define these logical segments/cables.

Once done, it is just like a segment with subnet on each one.


You would only need a superscope if you had multiple subnets
on a single segment/VLAN (that is called a "multinet".) You
need a superscope if the DHCP server will hand out addresses
to multiple subnets on such a Multinet.




.

Relevant Pages

  • Re: DHCP relay, superscope and laptops
    ... > In my case I have a L3 Switch that splits my network in a few distinct ... If you only use one IP Subnet range on each VLAN, ... you don't have multi-nets and thus don't need Superscopes. ... > relaying DHCP requests to a central DHCP server, ...
    (microsoft.public.windows.server.networking)
  • Re: Problems assigning IP addresses from DHCP superscopes in VLANs
    ... I agree you shouldn't use superscopes in this way... ... The other way you could do it is create seperate scopes on your DHCP server ... > Eliminate the Superscope, use regular Scopes,...one for each Segment. ...
    (microsoft.public.windows.server.networking)
  • Re: DHCP HELP
    ... Are you implementing superscopes on the DHCP server? ... How many IP addresses and NIC cards are on the server? ... Microsoft Technical Support ...
    (microsoft.public.win2000.networking)