Re: Client configuration for multiple DHCP scope
- From: "Phillip Windell" <philwindell@xxxxxxxxxxx>
- Date: Thu, 13 Sep 2007 12:29:21 -0500
"Will" <westes-usc@xxxxxxxxxxxxxx> wrote in message
news:eNqdnQaMeMBU9HXbnZ2dnUVZ_v6rnZ2d@xxxxxxxxxxxxxxx
"Phillip Windell" <philwindell@xxxxxxxxxxx> wrote in message
news:uwrln1U9HHA.5164@xxxxxxxxxxxxxxxxxxxxxxx
In all the years I have been doing these group (around 6 or 7 years) I
have seen hundreds of people saying they were using a Superscope,...out
of those hundreds only one that I can [barely] remember was legitamently
using it for the correct reason in the correct topology design.
Legitimate use for supserscope would be two overlapping subnets on the
same physical ethernet?
Yes.
It still requires a Router to route between the logical segments and both
interfaces of the router would also be on the same "wire".
The Hosts would be "subnet agnostic" meaning the Hosts would not care what
subnet they randomly "landed on" after getting their config from the DHCP
Superscope.
If the Admin "cares" what subnet they land on, then he needs to stop using a
Multi-Net and Superscopes.
Since VLANs have been invented the reason for a Multi-Net to exist has
become almost non-existant. VLANs also [potentially] run over the same
physical wire but the VLAN technology separates the physical "wire" into
different "logical wires" so that the LAN behaves like a normal multiple
subnet LAN and uses normal DHCP without Superscopes. A LAN Router is still
required with VLANs but each interface is on a different "logical wire".
VLANs, for the most part, are the replacement for the old Multi-Net
technology and the Superscope feature of DHCP could potentially be dropped
as a feature in newer versions of DHCP and "life would go on".
--
Phillip Windell
www.wandtv.com
The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------
.
- References:
- Client configuration for multiple DHCP scope
- From: iammytan via WinServerKB.com
- Re: Client configuration for multiple DHCP scope
- From: Phillip Windell
- Re: Client configuration for multiple DHCP scope
- From: iammytan via WinServerKB.com
- Re: Client configuration for multiple DHCP scope
- From: Phillip Windell
- Re: Client configuration for multiple DHCP scope
- From: Will
- Client configuration for multiple DHCP scope
- Prev by Date: Re: IIS6 + NLB - the network location cannot be reached
- Next by Date: Re: WIndows Server IP Address resoloution... issue...
- Previous by thread: Re: Client configuration for multiple DHCP scope
- Next by thread: Re: Client configuration for multiple DHCP scope
- Index(es):
Relevant Pages
|