DHCP
Windows Server Forum Index Windows Server
Server discussion on Windows platform.
 
 FAQFAQ   MemberlistMemberlist     RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 
 
Google
 
Web winserverhelp.com
DHCP

 
Post new topic   Reply to topic    Windows Server Forum Index -> Networking
Author Message
Stephan
Guest





Posted: Wed Jan 19, 2005 10:01 pm    Post subject: DHCP Reply with quote

I need to create a new DHCP scope on our network. We currently use
192.168.0.x, but it's reaching capacity. I want to add a new scope on a new
subnet, 192.168.4.x.

Here's the dumb question, what do I need to do for a default gateway? I
can't use 192.168.0.1, it has to be on the same subnet, right? So I'd use
192.168.4.1. Do I need hardware for this, or can I somehow make it work with
the current gateway?

To summarize, I'd like to add a new subnet, but without the hassle of adding
hardware. Any help as to the best approach would be appeciated.
Back to top
Tony Su
Guest





Posted: Thu Jan 20, 2005 9:23 pm    Post subject: RE: DHCP Reply with quote

Hello Stephan,
I recommend just "extending" your network space by modifying your subnet
mask to "supernet" your existing scope.

By default the Class C subnet mask is 255.255.255.0 which means that the
first three octets (24 bits) is your network ID and everything else is what
is available for Host addresses.

The entire Class C private network space though is 192.168.x.y so you can
re-allocate some of those bits in the third octet from network to host ids
while still being within the private network space.

So, an example might be to change the third octet from 255 to 240 which at
the cost of a number of network ids (but you won't want to really support
more than a few thousand possible networks <G>, right?)you'll increase the
number of new hosts by several thousand.

HTH,
Tony


"Stephan" wrote:

Quote:
I need to create a new DHCP scope on our network. We currently use
192.168.0.x, but it's reaching capacity. I want to add a new scope on a new
subnet, 192.168.4.x.

Here's the dumb question, what do I need to do for a default gateway? I
can't use 192.168.0.1, it has to be on the same subnet, right? So I'd use
192.168.4.1. Do I need hardware for this, or can I somehow make it work with
the current gateway?

To summarize, I'd like to add a new subnet, but without the hassle of adding
hardware. Any help as to the best approach would be appeciated.
Back to top
Stephan
Guest





Posted: Fri Jan 21, 2005 12:49 am    Post subject: RE: DHCP Reply with quote

Thanks Tony, great idea! However, it seems like a lot of work, won't I have
to change the subnet mask on all nodes on the network? I'd rather not have to
switch that on routers, switches, etc. Plus most servers and printers which
are static IP's.

"Tony Su" wrote:

Quote:
Hello Stephan,
I recommend just "extending" your network space by modifying your subnet
mask to "supernet" your existing scope.

By default the Class C subnet mask is 255.255.255.0 which means that the
first three octets (24 bits) is your network ID and everything else is what
is available for Host addresses.

The entire Class C private network space though is 192.168.x.y so you can
re-allocate some of those bits in the third octet from network to host ids
while still being within the private network space.

So, an example might be to change the third octet from 255 to 240 which at
the cost of a number of network ids (but you won't want to really support
more than a few thousand possible networks <G>, right?)you'll increase the
number of new hosts by several thousand.

HTH,
Tony


"Stephan" wrote:

I need to create a new DHCP scope on our network. We currently use
192.168.0.x, but it's reaching capacity. I want to add a new scope on a new
subnet, 192.168.4.x.

Here's the dumb question, what do I need to do for a default gateway? I
can't use 192.168.0.1, it has to be on the same subnet, right? So I'd use
192.168.4.1. Do I need hardware for this, or can I somehow make it work with
the current gateway?

To summarize, I'd like to add a new subnet, but without the hassle of adding
hardware. Any help as to the best approach would be appeciated.
Back to top
Bill Grant
Guest





Posted: Fri Jan 21, 2005 6:47 am    Post subject: Re: DHCP Reply with quote

If you have routers, why is everything in one subnet? IP routers only
route between IP subnets.

If you set up a second subnet, you will have to change you LAN topology
anyway to get routing working between your two subnets. The default gateway
setting on the new subnet will need to be set to point to the router which
links the subnets.

"Stephan" <Stephan@discussions.microsoft.com> wrote in message
news:F1DB409C-D167-4008-8569-04779ABE5B32@microsoft.com...
Quote:
Thanks Tony, great idea! However, it seems like a lot of work, won't I
have
to change the subnet mask on all nodes on the network? I'd rather not have
to
switch that on routers, switches, etc. Plus most servers and printers
which
are static IP's.

"Tony Su" wrote:

Hello Stephan,
I recommend just "extending" your network space by modifying your subnet
mask to "supernet" your existing scope.

By default the Class C subnet mask is 255.255.255.0 which means that the
first three octets (24 bits) is your network ID and everything else is
what
is available for Host addresses.

The entire Class C private network space though is 192.168.x.y so you can
re-allocate some of those bits in the third octet from network to host
ids
while still being within the private network space.

So, an example might be to change the third octet from 255 to 240 which
at
the cost of a number of network ids (but you won't want to really support
more than a few thousand possible networks <G>, right?)you'll increase
the
number of new hosts by several thousand.

HTH,
Tony


"Stephan" wrote:

I need to create a new DHCP scope on our network. We currently use
192.168.0.x, but it's reaching capacity. I want to add a new scope on a
new
subnet, 192.168.4.x.

Here's the dumb question, what do I need to do for a default gateway? I
can't use 192.168.0.1, it has to be on the same subnet, right? So I'd
use
192.168.4.1. Do I need hardware for this, or can I somehow make it work
with
the current gateway?

To summarize, I'd like to add a new subnet, but without the hassle of
adding
hardware. Any help as to the best approach would be appeciated.
Back to top
 
Post new topic   Reply to topic    Windows Server Forum Index -> Networking All times are GMT
Page 1 of 1

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum




New Topics Powered by phpBB