DHCP, out of IP's on scope. How do i expand?

  • Thread starter Thread starter rduque41
  • Start date Start date
R

rduque41

I have a win2k sp4 server running dhcp with only 1 scope
10.0.0.100-10.0.0.250/24 (the first 100 ips are statically assigned).

i am running out of room so I have been reading up on superscopes and
resubnetting. but I cant figure out if I need to have a second nic on
the server? or if the superscope replaces that.

I went with just superscope, and I added a new scope of
10.0.1.0-10.0.1.250 and used the subnet mask 255.255.255.0(not sure if
this is correct) and activated it.

I placed this new scope along with the original one in a superscope.
The default gateway that i configured for the new scope to hand out is
10.0.0.1(which is our router and its the same gateway the original
scope hands out, the dns server is 10.0.0.2)

Everything is on the same network/wire, we only have 1 router and thats
for our internet. How can i get the dhcp server to distribute ips from
the new scope, and more importantly once these new ips are distributed
will the computers on the new scope be able to communicate with
computers / servers on the old scope.

I tried statically assigning an ip address from the new scope but I am
not able to get out to the internet or ping the gateway, or the dns
server...i used ip:10.0.1.2 sm: 255.255.255.0
gateway 10.0.0.1, dns 10.0.0.2. I think this should work right?

Also Is there a way to make computers pull ips from the new scope?

Please help, what am I doing wrong.

Thank you,
 
Add a new segment with a LAN Router between the segments. Ethernet
broadcasts will become an issue when you start going past 250-300 hosts per
segment. A /24 segment is the perfect size,..keep it that way.

See my reply to "Smart" with the subject "How to control broadcasting from
client machines?"

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

The views expressed are my own (as annoying as they are), and not those of
my employer or anyone else associated with me.
 
I have a win2k sp4 server running dhcp with only 1 scope
10.0.0.100-10.0.0.250/24 (the first 100 ips are statically assigned).
Click to expand...

The scope should be:
10.0.0.1 - 10.0.0.254
Exclusions 10.0.0.1 - 10.0.0.100

Always use the *full* ip range in a Scope and then use Exclusions to block
out the onse you want to use for Static. This way when you run low on
addresses you can check the Static machines and if you haven't allocated all
of them you can just trim off the Exclusions a little to add to the Dynamic
pool. So if you Static machine only actually go up to 10.0.0.84 you can
trim your Exclusions back to 10.0.0.1 - 10.0.0.90 and gain 10 dynamic
addresses and still have six more left in the Static pool.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

The views expressed are my own (as annoying as they are), and not those of
my employer or anyone else associated with me.
 
SuperScopes are for Multi-Netting,...there is no Multi-Netting going on
here. It is rarely done anymore because the invention of VLAN technology has
made it more or less obsolete.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

The views expressed are my own (as annoying as they are), and not those of
my employer or anyone else associated with me.
 
Ok this is what I did.

I created a new scope 10.0.1.1 - 10.0.2.254 with a subnet mask of
255.255.254.0
It allowed me to create this in 1 scope and when i statically configure
2 machines, one, with the 10.0.1.2 address and one with the 10.0.2.1
address i was able to ping back and forth..but i cannot ping my default
gateway which is 10.0.0.1...is this because the default gateway is on
the 255.255.255.0 subnet mask and on the original scope(
10.0.0.100-10.0.0.250)? i have a server on 10.0.0.15 with a subner of
255.255.254.0 but i cannot ping it from the 10.0.1.2 and 10.0.2.1
computers. any clues?
should i erase the first original dhcp scope of 10.0.0.100-10.0.0.250
and create one big scope of 10.0.0.0 - 10.0.1.254 with exlcusions in
10.0.0.0 - 10.0.0.100 and a subnet mask of 255.255.254.0?

thank you


Phillip said:
SuperScopes are for Multi-Netting,...there is no Multi-Netting going on
here. It is rarely done anymore because the invention of VLAN technology has
made it more or less obsolete.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

The views expressed are my own (as annoying as they are), and not those of
my employer or anyone else associated with me.



I went with just superscope, and I added a new scope of
10.0.1.0-10.0.1.250 and used the subnet mask 255.255.255.0(not sure if
this is correct) and activated it.

I placed this new scope along with the original one in a superscope.
The default gateway that i configured for the new scope to hand out is
10.0.0.1(which is our router and its the same gateway the original
scope hands out, the dns server is 10.0.0.2)
Click to expand...
Click to expand...
 
You have to change the mask on *everything*,...*everywhere*. Computers,
Hubs, Switches, Routers, Firewalls, Printers, Network "gizmos",...you name
it,..it has to be changed.
It is all or nothing.

Add a new LAN segment and add a LAN Router between that and the old segment
like I said in the other post and you don't have to do any of those things.
Nothing even has to live on new segment until you are actually forced to
move something to it due to no more addresses. Just the cost of a LAN Router
and a little cable work and you are done, and you will reduce the negative
effect of broadcasts on the LAN and create new good security options in the
process.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

The views expressed are my own (as annoying as they are), and not those of
my employer or anyone else associated with me.





Ok this is what I did.

I created a new scope 10.0.1.1 - 10.0.2.254 with a subnet mask of
255.255.254.0
It allowed me to create this in 1 scope and when i statically configure
2 machines, one, with the 10.0.1.2 address and one with the 10.0.2.1
address i was able to ping back and forth..but i cannot ping my default
gateway which is 10.0.0.1...is this because the default gateway is on
the 255.255.255.0 subnet mask and on the original scope(
10.0.0.100-10.0.0.250)? i have a server on 10.0.0.15 with a subner of
255.255.254.0 but i cannot ping it from the 10.0.1.2 and 10.0.2.1
computers. any clues?
should i erase the first original dhcp scope of 10.0.0.100-10.0.0.250
and create one big scope of 10.0.0.0 - 10.0.1.254 with exlcusions in
10.0.0.0 - 10.0.0.100 and a subnet mask of 255.255.254.0?

thank you


Phillip said:
SuperScopes are for Multi-Netting,...there is no Multi-Netting going on
here. It is rarely done anymore because the invention of VLAN technology
has
made it more or less obsolete.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

The views expressed are my own (as annoying as they are), and not those
of
my employer or anyone else associated with me.



I went with just superscope, and I added a new scope of
10.0.1.0-10.0.1.250 and used the subnet mask 255.255.255.0(not sure if
this is correct) and activated it.

I placed this new scope along with the original one in a superscope.
The default gateway that i configured for the new scope to hand out is
10.0.0.1(which is our router and its the same gateway the original
scope hands out, the dns server is 10.0.0.2)
Click to expand...
Click to expand...
Click to expand...
 
Philip,

when you say at a lan router, which one do you recommend? and would the
dhcp for that segment of computers then come from taht router? how
would i configure the router to connect to connect to the dhcp server.

and even then do i have to create a new scope on the dhcp server, or
does the router take care of that? im sorry for the stupid questions im
just a bit confused.

Thank you,

Roy

Phillip said:
You have to change the mask on *everything*,...*everywhere*. Computers,
Hubs, Switches, Routers, Firewalls, Printers, Network "gizmos",...you name
it,..it has to be changed.
It is all or nothing.

Add a new LAN segment and add a LAN Router between that and the old segment
like I said in the other post and you don't have to do any of those things.
Nothing even has to live on new segment until you are actually forced to
move something to it due to no more addresses. Just the cost of a LAN Router
and a little cable work and you are done, and you will reduce the negative
effect of broadcasts on the LAN and create new good security options in the
process.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

The views expressed are my own (as annoying as they are), and not those of
my employer or anyone else associated with me.





Ok this is what I did.

I created a new scope 10.0.1.1 - 10.0.2.254 with a subnet mask of
255.255.254.0
It allowed me to create this in 1 scope and when i statically configure
2 machines, one, with the 10.0.1.2 address and one with the 10.0.2.1
address i was able to ping back and forth..but i cannot ping my default
gateway which is 10.0.0.1...is this because the default gateway is on
the 255.255.255.0 subnet mask and on the original scope(
10.0.0.100-10.0.0.250)? i have a server on 10.0.0.15 with a subner of
255.255.254.0 but i cannot ping it from the 10.0.1.2 and 10.0.2.1
computers. any clues?
should i erase the first original dhcp scope of 10.0.0.100-10.0.0.250
and create one big scope of 10.0.0.0 - 10.0.1.254 with exlcusions in
10.0.0.0 - 10.0.0.100 and a subnet mask of 255.255.254.0?

thank you


Phillip said:
SuperScopes are for Multi-Netting,...there is no Multi-Netting going on
here. It is rarely done anymore because the invention of VLAN technology
has
made it more or less obsolete.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

The views expressed are my own (as annoying as they are), and not those
of
my employer or anyone else associated with me.



I went with just superscope, and I added a new scope of
10.0.1.0-10.0.1.250 and used the subnet mask 255.255.255.0(not sure if
this is correct) and activated it.

I placed this new scope along with the original one in a superscope.
The default gateway that i configured for the new scope to hand out is
10.0.0.1(which is our router and its the same gateway the original
scope hands out, the dns server is 10.0.0.2)
Click to expand...
Click to expand...
Click to expand...
 
The simplest is to buy a Layer3 Switch. They are a Normal Switch and a LAN
Router both built into the same hardware device. Prices vary,...but HP
Procurves are a good buy for the money and that is what we use. Just make
sure it is Layer3. They are almost always fully VLAN capable as well.

1. For two segments you create an additional VLAN in the Switch (one is
already there by default), then assign half the switch ports to one and half
the switch ports to the other. So whatever ports you plug something
into,..that is the segment it will be part of. So your existing LAN segment
plugs into the first set of ports,...the new segment plugs into the second
set of ports. You can then branch other Switches off from there. No rocket
science, just straight forward cabling. Your original segment remains
*undesturbed* at this point. You can add or move machines to the new segment
whenever you get around to it.

2. Make all machines (both segments) use the LAN Router as the Default
Gateway.

3. Use your Internet Device as the Default Gateway of the LAN Router.

4. In the Internet Device, configure a Static Route that tells it to use the
LAN Router as the path to you LAN's segments


DHCP is very simple.
1. Create a new independent Scope for the new segment.
(that's it,..all done,..nothing else on the DHCP box)
2. On the LAN Router configure the DHCP Relay feature to forward DHCP
Queries to the DHCP Server. Usually it is a no-brainer,...turn the feature
on,...give it the IP# of the DHCP Server,...done.

If in the future you need another subnet, just repeat the process.
1. Create a 3rd VLAN, reasign the switch ports accordingly.
2. Run cables off those ports for the 3rd segment
3. Add a Scope for the Segment to the DHCP Server
4. Adjust Static Route on the Internet device to include new segment.

....Piece of cake...


--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

The views expressed are my own (as annoying as they are), and not those of
my employer or anyone else associated with me.




Philip,

when you say at a lan router, which one do you recommend? and would the
dhcp for that segment of computers then come from taht router? how
would i configure the router to connect to connect to the dhcp server.

and even then do i have to create a new scope on the dhcp server, or
does the router take care of that? im sorry for the stupid questions im
just a bit confused.

Thank you,

Roy

Phillip said:
You have to change the mask on *everything*,...*everywhere*. Computers,
Hubs, Switches, Routers, Firewalls, Printers, Network "gizmos",...you
name
it,..it has to be changed.
It is all or nothing.

Add a new LAN segment and add a LAN Router between that and the old
segment
like I said in the other post and you don't have to do any of those
things.
Nothing even has to live on new segment until you are actually forced to
move something to it due to no more addresses. Just the cost of a LAN
Router
and a little cable work and you are done, and you will reduce the
negative
effect of broadcasts on the LAN and create new good security options in
the
process.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

The views expressed are my own (as annoying as they are), and not those
of
my employer or anyone else associated with me.





Ok this is what I did.

I created a new scope 10.0.1.1 - 10.0.2.254 with a subnet mask of
255.255.254.0
It allowed me to create this in 1 scope and when i statically configure
2 machines, one, with the 10.0.1.2 address and one with the 10.0.2.1
address i was able to ping back and forth..but i cannot ping my default
gateway which is 10.0.0.1...is this because the default gateway is on
the 255.255.255.0 subnet mask and on the original scope(
10.0.0.100-10.0.0.250)? i have a server on 10.0.0.15 with a subner of
255.255.254.0 but i cannot ping it from the 10.0.1.2 and 10.0.2.1
computers. any clues?
should i erase the first original dhcp scope of 10.0.0.100-10.0.0.250
and create one big scope of 10.0.0.0 - 10.0.1.254 with exlcusions in
10.0.0.0 - 10.0.0.100 and a subnet mask of 255.255.254.0?

thank you


Phillip Windell wrote:
SuperScopes are for Multi-Netting,...there is no Multi-Netting going
on
here. It is rarely done anymore because the invention of VLAN
technology
has
made it more or less obsolete.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

The views expressed are my own (as annoying as they are), and not
those
of
my employer or anyone else associated with me.



I went with just superscope, and I added a new scope of
10.0.1.0-10.0.1.250 and used the subnet mask 255.255.255.0(not sure
if
this is correct) and activated it.

I placed this new scope along with the original one in a superscope.
The default gateway that i configured for the new scope to hand out
is
10.0.0.1(which is our router and its the same gateway the original
scope hands out, the dns server is 10.0.0.2)
Click to expand...
Click to expand...
Click to expand...
 
Back
Top