Windows DHCP Superscope and Scope configuration

Hi Guys,
I'm looking for the correct Superscope/Scope configuration in a Windows Server 2012.

I have a Cisco 3750 Stack with the following vlan configuration.

Interface Vlan1
 ip address 10.10.70.1 255.255.255.0
 ip helper-address10.10.88.100
!
interface Vlan40
 ip address 10.10.40.1 255.255.255.0
 ip helper-address10.10.88.100
!
interface Vlan88
 ip address 10.10.88.1 255.255.255.0
!

I have a Windows Server 2012 running DHCP service connected to Vlan88 (10.10.88.100)
There is one Superscope ALLNETWORKS configured and originally only one scope under it (10.10.70.1/24), this one scope is working fine.

Now enter my new Vlan40 with completely different users that need a new DHCP Scope.
I'm going to use the same DHCP Server, so I went and created a second scope under the same Superscope ALLNETWORKS (10.10.40.1/24), turns out this second scope doesn't work.

In all honesty I don't know how exactly the Superscope works, so at this point I don't know if I need to create a brand new Superscope/scope combination for the new Vlan40 (10.10.40.1/24).

Can you please help me find the correct Superscope/scope configuration for my network?

Thanks.
cargexAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

cargexAuthor Commented:
0
Aaron TomoskySD-WAN SimplifiedCommented:
I don't think you need the super scope at all. Just have one scope per vlan subnet on the DHCP server. The rest looks correct.
0
cargexAuthor Commented:
The reason for the super scope is that in the beginning I created just the one scope  (10.10.70.1/24) on my DHCP Server (10.10.88.100 - Vlan88), and it didn't work.

So after reading a little my conclusion was that the Super scope is needed because the DHCP Server is no a different Vlan than the computers that need the IP addresses, I created the super scope and sure enough it works.

I think what I need to understand here is what is the role of the super scope, and why it looks like I need 2 different super scopes.

Can anyone please elaborate on the usefulness of the super scope and why do I seem to need one super scope per Vlan?
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Aaron TomoskySD-WAN SimplifiedCommented:
You can read all about super scopes anywhere, in telling you that your current setup doesn't need one. You have DHCP helper set in the switch and you just make normal scopes for each vlan/subnet. You can make a super scope with a scope in it for each vlan, it won't hurt anything, it just doesn't do anything.
0
cargexAuthor Commented:
Aaron,
But let's go back to the initial configuration I listed:

3 different vlan (1,40, and 88)
1 Single Cisco 3750 Stack with inter vlan routing

The Windows DHCP Server is physically connected to Vlan88 (10.10.88.100)
Initially I had all my client computers connected to Vlan1 (10.10.70.1/24) and I tried creating just 1 single scope in the DHCP server, it didn't work.
After many discussions the conclusion was that the server needed to have a Super Scope to handle the 10.10.70.1/24 IP range because it was physically connected to the Vlan88.
I did it and it worked, that's the way it is working currently.

So in order for you solution to work, first we need to find a solution for my initial problem, which is that when I create the (10.10.70.1/24) scope in the server (10.10.88.100 - Vlan88) it didn't work.

Is there a way to solve that issue which doesn't involve a super scope?
0
cargexAuthor Commented:
After reading about how Super Scopes work and why were they created, I have realized that I can't place my second scope (10.10.40.1/24) inside the same super scope that contains my current scope (10.10.70.1/24). This is because the super scope will not use any IPs from the second scope until the first one is full.

Knowing that, I think the solution is to create a second super scope for the new scope (10.10.40.1/24) and the DHCP Server will assign the IP according to the Vlan where the DHCP Client request comes from.

I will try this approach tomorrow and I'll let you know what happens.

Also if you have any input on this matter please do post your comment.

Thanks.
0
Aaron TomoskySD-WAN SimplifiedCommented:
Are those the actual ip helper-address commands copy and pasted? If so, you are probably missing a space. I'm not very familiar with specific Cisco commands, I thought it was DHCP helper but I could be wrong.

What I do know is that I have a ton of networks I've setup with vlans and ip helper and Windows DHCP server and never ever used a super scope. Ever.  No multiple NICS or trunk ports to the Windows DHCP server either. Just a single ip on an untagged port with multiple scopes.
0
kevinhsiehCommented:
You don't need super scopes. They are a special case.

On the Cisco switch:

Configure terminal
Interface vlan 1
ip helper-address 10.10.88.100
Interface vlan 40
ip helper-address 10.10.88.100

I do this on Cisco gear all the time. Multiple subnets with multiple local and remote DHCP servers. I have never needed a super scope.
0
cargexAuthor Commented:
Guys,
I don't know what to tell you.
I didn't even know what super scopes were until  I created a scope to give away IP addresses from an IP range different from the one the NIC card was connected to.

My case
DHCP Server IP: 10.10.88.100
IP Range scope: 10.10.70.1/24

I did everything and try all the possible configurations, until finally I found out about Super Scopes, created one, and voila it worked.

Now that I need to add a new (second) scope to the same DHCP Server, I read about how Super Scopes work and turns out that if I create the second IP Range (10.10.40.1/24) under the same Super Scope, the DHCP Server won't give away IP addresses until the first scope has been depleted (not what I want).

My solution in the end was to create a second Super Scope that contains only my new second scope with the IP Range (10.10.40.1/24). And this works!

I will give you points because you pointed my investigation in the correct way, so thanks guys!
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
cargexAuthor Commented:
The B grade is because you didn't point to any source of information to support the proposed solution.
I will give you points because you pointed my investigation in the correct way, so thanks guys!

The ip helper is also a good tip, I already had it configured but it was great to have a confirmation that the Cisco ip helper configuration was correct.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.