Adding a Second Scope to a DHCP Server

I think this is what you are after:

 Superscopes

Aside from a regular scope, you can also create a second type of scope known as a superscope. In a multinetted environment (one that has multiple logical IP subnets defined on a single physical network), superscopes allow a DHCP server to assign leases to clients on multiple subnets.

For example, a physical network is divided into two subnets, Subnet A and Subnet B, connected by a router. Subnet B contains two multinets. A single DHCP server is located on Subnet A. The DHCP server contains a single scope with a range of IP addresses to lease to clients on Subnet A. To have the DHCP server assign IP addresses to clients on Subnet B, you can create a superscope and add to it the IP address ranges for the multinets on Subnet B. The scope configuration on the DHCP server could be similar to the following:

Subnet A
   Scope 1: 192.168.1.2–192.168.1.254
Subnet B
   Superscope for Subnet B
      Scope 2: 192.168.2.2–192.168.2.254
      Scope 3: 192.168.3.2–192.168.3.254

One of the biggest advantages of creating superscopes is to ease administration of a multinetted environment. Identifying which scopes go with which networks can be a difficult administration task. Creating superscopes and grouping scopes in some logical manner can make them easier to administer; for example, grouping all the scopes from a single floor in a large office building into a superscope eases the administration process.

Superscopes are also used to support DHCP clients on a single physical network segment (such as a single Ethernet LAN segment) on which multiple logical IP networks are used. When more than one logical IP network is used on each physical subnet or network, such configurations are called multinets .
Creating a Superscope

To create a new superscope within the DHCP management console, follow these steps:

   1.

      Right-click the DHCP server and select the New Superscope option. The New Superscope Wizard opens. Keep in mind that the superscope option is available only if a regular scope already exists. Click Next.
   2.

      Type a descriptive name for the superscope (something that makes it easy to identify). Click Next.
   3.

      From the list of available scopes, select those to include in the superscope. You can only add active scopes. Click Next.
   4.

      Click Finish.

After the superscope has been created, it must be activated by right-clicking the scope and selecting the Activate option.


Hope this helps!
D

In addition....to not get a conflict added a scope of 172.19.19.x should work with a subnet mask of .252 as it is in a different subnet.

But dont do that. Lengthen your end range to .17.254.

dimante,

I was trying to set up a superscope when I ran into the conflict.  I want to use two DHCP servers.  I thought I could create a second scope 172.19.17.1-254 on the second server.

I read about this in "Windows & .net Magazine".  I could not find the article again.

So my solution is to just add the 172.19.17.1-254 to the first server and then let the second server handle a portion of that larger scope, excluding addresses as required so the two servers don't try to hand out the same IP addresses.

This "adding to the first scope" was suggested by  diggisaur.

Thanks Everyone

"In addition....to not get a conflict added a scope of 172.19.19.x should work with a subnet mask of .252 as it is in a different subnet."

Diggisaur, are you sure 172.19.19.x with a subnet mask of 255.255.252.0 is in a different subnet to 16.x and 17.x
I would say a subnet mask of .252.0 gives an address range of 16.1 -> 19.254 which puts 16-19 on the same subnet.
Correct me if I am wrong.
Regards