How to add the new IP range under the address pool in DHCP

Hi

We use windows 2008 as our DC  and DHCP server. We use class A IPv4 range and we have run out of IP addressed I had requested our firewall team for a new IP range and they have given me  the range.

I want to add  the new address range distribution on our DHCP server.
On the DHCP When I expand IPv4- Scope and click Address Pool

On the right hand side it shows the previous Address range for distribution configured.
10.x.x.x - 10.x.x.254

Please post me some tutorial as how to add the new IP range under the address pool
Thanks
lianne143Asked:
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.

Vaseem MohammedCommented:
You must have got a different range of IP address.
You can create a separate scope for new IP address set.
You just need to right click on IPv4 and create a new scope, and you can fill in the data as its not difficult.
0
SreRajCommented:
Please find the detailed steps in the following Microsoft Article.

http://technet.microsoft.com/en-us/library/cc754112(v=ws.10).aspx

The following article has images of wizard and is easy to follow thru.

http://www.wikihow.com/Create-a-New-Scope-in-DHCP
0
vivigattCommented:
You must have been doing something strange !
10.x.x.x (with the standard subnet mask for it, which is 8 bits, also noted 255.0.0.0) is a private class 1 subnet and allows for more than 16 millions of nodes! Don't tell me you have more than 16 millions of nodes. Check this page:
http://en.wikipedia.org/wiki/Private_network

Now, you may have used a bigger subnet mask, thus restricting your number of nodes. Maybe you used 10.x.x.x/24 (10.x.x.x/255.255.255.0), giving you a maximum of 254 nodes. This is not recommended even if perfectly valid. When you want to use a class C private subnet, it is recommended to use a 192.168.x.x network. However, since you have this set this way currently, we will try to help you figure out how to extend the scope or to add another scope (which means another subnet, and this may not be what you want...)

Can you tell us exactly what are the subnets/scopes you use and will use (along with subnet masks) ? This will allow us to help you best. Don't worry about security, private networks CANNOT be routed outside your own network(s), so even if you disclose the actual subnets and masks, there is nothing that can be done with that information to access your network(s) remotely.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

lianne143Author Commented:
Hi vivigatt

The scope specified on the DHCP at the moment is 10.14.112.1 - 10.14.115.254
Subnet mask is 255.255.252.0
So I think it is 10.14.112.0/22

Now the  new scope given by the firewall team  is 10.14.108.0/22

Thanks
0
vivigattCommented:
So your network is currently 10.14.112.0/22 and you have a maximum of 1022 hosts. Lets call it Subnet1 (and the associated scope will be called scope1)
The new subnet is 10.14.108.0/22. Lets call it Subnet2 (and scope 2). This new subnet is good for 1022 other hosts.
Now, having both subnets working together means that Subnet2 it is ANOTHER (sub)network and that you will have to route packets between Subnet1 and Subnet2 if you want the devices in each subnet to communicate one with another.
Assuming that this is the case, and that "the firewall team" handles the routing etc, you just have to create another scope on the DHCP server with the details:
start: 10.14.108.1
end: 10.14.111.254
Gateway: the GW that was given to you. Note that it MUST be on the same subnet so the scope is certainly not 10.14.108.1/10.14.111.254, but maybe 10.14.108.2/10.14.111.254 or 10.14.108.1/10.14.111.253, keeping the IP address of the GW outside of the scope. The same thing goes for the other subnet/scope. Unless you do not have any gateway, but then, it means that the devices can't "go to the Internet", even with a proxy...
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
lianne143Author Commented:
Hi  Vivigatt

Thanks for your reply!

With the existing IP Subnet 10.14.112.0/22 and the newly allocated IP Subnet was 10.14.108.0/22 I agree with you that routing and more configurations need to be established between two subnets for the devices on each subnet to communicate with each other. Now considering both subnets I will be getting a total of  1022+1022= 2044 IP address in total .

We may expand our network in the future. So as a future proof I feel if I request the Firewall team  10.14.112.0/20 and this will give me 4094 IP address, which will really suffice all our needs.

Please suggest, Is this a good idea ?  or do you have any other thoughts.
0
vivigattCommented:
Using 10.14.112.0/20 instead of two /22 subnets seems a good practice to me.
Subnetting without a real need to have 2 separate subnets is usually a bad idea. If all the hosts are legit to share the same subnet, I would go for a /20 subnet instead of four  /22   subnets
0
lianne143Author Commented:
Finally. I don't know how this configuration will be done on the router/firewall  by the FW team, because I don't have any access.
Do I need to ask the FW team anything specific for this new /20 subnet to be configured so that I can delete the existing scope (10.14.112.1 - 10.14.115.254 ) on my windows DHCP server and create a new scope 10.14.112.1 - 10.14.127.254.

So that all my PCs upon reboot will pick up the new IP Schema from the DHCP with the new subnet mask :255.255.240.0

Thanks  you so much your help !!
0
vivigattCommented:
I think that you may have to ask the FW team to allow the new subnet for your own network:
10.14.112.1/20
Depending on the FW configuration it may be needed for them to know that some larger range of IP addresses might access the FW from your side.
0
lianne143Author Commented:
Thanks Buddy!!
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
Active Directory

From novice to tech pro — start learning today.