DHCP scope

Microsoft Windows server 2003 enterprise
May 18, 2010 at 22:53:34
Specs: Server, 1G
Running out of DHCP ips, do I just create another scope? will the clients be able to get an ip from the server.
subnet 255.255.252.0
DHCP is 192.168.1.0-255
Another scopt for 192.168.2-255?
HOw will the clients know which one to get?
Thanks

See More: DHCP scope

Report •

#1
May 19, 2010 at 07:34:57
If you have so many clients you're running out of IP's in one subnet then yes, you'll have to start another subnet.

What kind of network do you have? Are you using managed switches and VLAN's? Do you have a router that can route between subnets?


Report •

#2
May 19, 2010 at 08:21:26
"Another scopt for 192.168.2-255?
HOw will the clients know which one to get?"

Another scope alone will not work. Like said above you will need another Subnet. Then you will need to setup routing between the subnets. You could simply connect them with a router. You will also need another DHCP server setup on this new subnet. You could probably use the Router for this because most have DHCP built in.


Report •

#3
May 19, 2010 at 08:39:49
Or you can bypass all of that and supernet. No router required.

192.160.2.0 /23 gives you 510 hosts
192.160.2.0 - 192.160.3.255

Though I find your posted ip/subnet interesting. What were you trying to accomplish with subnet mask 255.255.252.0 or was that just a mistype?


Report •

Related Solutions

#4
May 19, 2010 at 19:16:08
Basical our network is wired via switches to our broadband modem, it's just done in a standard star topology. We have 1 DHCP server setup with scope 192.168.1.1-254, At the moment the clients are setup with fix ips 192.168.0.1-254 and others are using DHCP which gets 192.168.1-1-254, all are set to subnet 255.255.252.0 with a gateway 192.168.0.1, we are both running out of internal fix and dhcp ips. I think I could just setup more machines with fix ips starting with 192.168.2.1-254 to solve this but I wanted to use DHCP.

Report •

#5
May 19, 2010 at 20:05:09
With that subnet you have 1022 hosts. You certainly are not running out of ips. You could make your dhcp scope 192.168.1.1 <-> 192.168.3.254 /22

Report •

#6
May 20, 2010 at 06:01:38
Oh good, I just need to change the scope, if not then just add another one, the client should be able to get them, I think I need to also add to the DNS also.

Report •

#7
May 20, 2010 at 06:45:58
set dhcp to autoupdate dns and you don't have to manually do anything. so who set this subnet mask 255.255.252.0 to begin with?

Report •

#8
May 20, 2010 at 07:02:14
3rd party IT solution company, they suggested setting the subnet from 255.255.255.0 to 255.255.252.0 because we needed more than 256 IP address, is this not how it's done?

Report •

#9
May 20, 2010 at 07:09:26
They came in and did network and configure it for us, don't I need to also add to our DNS server the reverse lookup zone 2.168.192.in-addr.arpa, if I am going to use the 192.168.2.1-255 for DHCP?

Report •

#10
May 20, 2010 at 10:38:10
192.168.2.X Subnet in reverse lookup zone
You should have 192.168.1.X Subnet in the reverse lookup zone already.
You would add 192.168.3.X Subnet when you decide to further expand.

Each contains the PTR workstation entry for the host(s) in that subnet.


Report •

#11
May 25, 2010 at 07:37:00
yes, I did change the scope to 192.168.1.x-192.168.2.x and added reverse lookup in DNS, seems to be working, thanks

Report •

#12
May 25, 2010 at 08:23:30
glad to hear it and thanks for posting back.

Report •

Ask Question