Implementing A Superscope

[ckosel]

I am making changes to a network in which I am running out of IP addresses. The subnet is currently 192.168.1.x and I would like to implement a Superscope. We would prefer not to change the IP addresses of the existing infrastructure. If I understand implementation correctly, an additional scope would have to be either a 192.168.2.x or 192.168.0.x. If I choose the latter, will the server hand out additional leases in the 192.168.0.x once the 192.168.1.x has exhausted it's remaining leases, or will it want to "flow" upward to the the next higher range of 192.168.2.0?

I ask this, because I am already using the 192.168.2.x range on another connected site that I'd prefer to leave as is. Any advice would be appreciated.

 

[ICTCity]

Actually I THINK that superscope should wait for 1.X to be exhausted before going to the next class.

Take a look here:
http://technet.microsoft.com/en-us/library/cc757614(WS.10).aspx

I'm still thinking at your question... I'm not sure.