What's the benefit of using superscopes?
- From: Tim.Richardson1@xxxxxxxxx
- Date: 24 May 2005 00:53:12 -0700
Hi, first a bit of background...
We have a 192.168.2.0 / 255.255.255.0 scope which is depleted so i
intend to move to a 10.10.0.0 / 255.255.0.0 range, all the clients are
on the same physical network so we'll end up with a multinetted
environment.
I planned to achieve this by leaving the old 192.168.2.0 scope running
on "DHCP Server 1" whilst creating a 10.10.0.10 - 10.10.0.254 scope on
"DC1" and a 10.10.1.1 - 10.10.1.254 scope on "DC2".
Both DC1 and DC2 have static IPs on the 192.168.2.0 subnet and i
planned on adding nics with 10.10.0.0 address on which they could
service dhcp requests. I'd then give our internal firewalls'
192.168.2.2 NIC an additional IP of 10.10.0.1 and set up routing.
This all seemed fine until i started reading about superscopes. What
benefit would there be to creating a supercope on the existing dhcp
server that encompasses both scopes as opposed to the proposal above?
Would i still need to put one of it's nics on the 10.10.0.0 network?
Also, when the subnets are physically seperate how does the superscope
determine which IPs to assign to which subnet?
Thanks,
Tim.
.
- Follow-Ups:
- Re: What's the benefit of using superscopes?
- From: Tim . Richardson1
- Re: What's the benefit of using superscopes?
- Prev by Date: Winxp slow login to Win2003
- Next by Date: Event ID 3019 on Windows 2003 Server Std. SP1
- Previous by thread: Winxp slow login to Win2003
- Next by thread: Re: What's the benefit of using superscopes?
- Index(es):
Relevant Pages
|
