[2 days left] What’s wrong with your cloud strategy? Learn why multicloud solutions matter with Nimble Storage.Register Now


Trouble adding a second DHCP scope

Posted on 2011-09-20
Medium Priority
Last Modified: 2012-06-27
Using Windows 2003 active directory server. The network is Existing DHCP scope is Would like to add a second scope to support WIFI clients. Tried adding second scope of, but I keep getting a message saying it conflicts or something. How can I do this properly?
Question by:robw24
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 3

Expert Comment

ID: 36568388
What is the exact conflict message you are getting?
Are there any Static IP addresses assigned to the DHCP server that the range you are configuring conflicts with?
For example - the server IP address might be

Expert Comment

ID: 36568435
Additionally, instead of adding another scope, why not just increase the scope you have from the end IP address range being at to being at instead?

Hope this helps.

Author Comment

ID: 36568613
"The address range and scope conflicts with an existing scope.". I am actually trying to add just

I would consider expanding the original scope, but really would like to know why I can't add a second scope. And if I did expand the scope, how do I get just WIFI clients to use the 10.1.1.x range?
Does Powershell have you tied up in knots?

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


Accepted Solution

OctInv earned 1600 total points
ID: 36569415
To answer your first point in your last post:
The first scope you created has the potential of including the new range of IP addresses (even though it currently doesn't include them), and so therefore considers a new scope as the same as the one you are creating.
You could extend your scope to cover the available range and exclude multiple ranges that you don't want to give out.

To answer your second point:
DHCP doesn't care what kind of network adaptor asks for an IP address when it is on the same subnet, it will just simply supply one without prejudice; the exception of course is when you use reservations and that involves you finding out the MAC address of each wireless client machines network interface - something I'm sure that you don't want to have to do.

The only way I see of having your wireless clients picking up separate IP address is if you place the wireless controller on a separate subnet, say,, and place a router between the wireless controller and the DHCP server.  Route all requests from the wireless subnet to the DHCP on your current subnet.  Then you could create a new scope on the DHCP matching that of your new subnet.  Given that the wireless clients would be asking for an IP address from the 10.2.x.x range, they would get assigned that IP address from the DHCP server instead.

Hope this helps you.

Expert Comment

ID: 36569486
edit on that last post...
'and so therefore considers a new scope as the same as the one you are creating'
....should read:
'and so therefore considers a new scope as the same as the one you have already created'

Author Comment

ID: 36569553
Well that makes sense about the new scope being the same as the existing scope. Your partially right about DHCP not caring, however I was going to play around with optional DHCP parameters such as vendor class, which is supposed to make it discriminate.
The router is not a bad idea, but I think it will add too much complexity, especially since I will be adding multiple access points spread through the company.

What I am thinking of trying now is to setup an additional DHCP server on the Radius Server/IAS server box.. I will configure it with the 10.1.1.x scope that I want, and I will program the wireless access points to forward DHCP requests to only this server. Not sure if I will need/want to authorize it in active directory or not, as I don't want non-wireless clients to obtain ip addresses from it.

Expert Comment

ID: 36570005
Excellent news, I'm glad that my advice seems to have answered your question.

I don't know why I’m only partially right though as I think you might be mistaken about the use of vendor classes.  My understanding is that this is a method used for managing DHCP options assigned to clients identified by vendor type (i.e. operating system or hardware manufacturer) rather than what IP address they use - for example you might want a DHCP assigned Windows 2000 computer or a Cisco router to use another default gateway or use a different DNS server.  Assigning their IP address is not something that is done within DHCP options.  However - if you can put me right on this, then please let me know.

I'm also unsure on how you can forward DHCP requests as these requests are always broadcasted on the network - and broadcasts are received by everything on the same subnet.  If you have 2 DHCP servers on the same subnet (which is what you are proposing), then either server will respond to a DHCP request and provide an IP address.
Again, I might be wrong on this if you find a way round this, so if your proposed solution above works, I'd be really interested on how you achieved this.

All the best, and good luck.

Author Comment

ID: 36573318
You may indeed be right about the use of vendor class, I have not tinkered with that yet and I honestly don't remember some things like that learned years ago studying for MCSE.

As far as forwarding the DHCP requests, there is an option in the access point software to forward DHCP requests to whatever IP address I would like. So I imagine that instead of forwarding the DHCP broadcast from the wireless clients, the AP would drop it and forward/unicast it instead to a specific host.

I will let you know how it works out with the additional DHCP server.

Assisted Solution

Dusan_Bajic earned 400 total points
ID: 36574025

You have some good advices from Octlnv in previous posts, but really stable, by-the-book solution depends on what are you trying to achieve. Do you want your wi-fi clients to be in the same subnet and/or broadcast domain with your other devices? If you don't have any reason to separate them, just don't do it, you are only making things more complicated. If you do want to separate them, you usually have to go with VLANs (unless you have separate cabling for APs which is rarely the case)

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Microsoft Office 365 is a subscriptions based service which includes services like Exchange Online and Skype for business Online. These services integrate with Microsoft's online version of Active Directory called Azure Active Directory.
Wouldn't it be nice if objects in Active Directory automatically moved into the correct Organizational Units? This is what AutoAD aims to do and as a plus, it automatically creates Sites, Subnets, and Organizational Units.
This video shows how to use Hyena, from SystemTools Software, to bulk import 100 user accounts from an external text file. View in 1080p for best video quality.
Are you ready to implement Active Directory best practices without reading 300+ pages? You're in luck. In this webinar hosted by Skyport Systems, you gain insight into Microsoft's latest comprehensive guide, with tips on the best and easiest way…
Suggested Courses

649 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question