Run out of IP addresses

The subject says it all.

I have five Windows 2003 servers, each running various business apps
including a Manufacturing Systems, Exchange Server 2003, a separate SQL
Server 2005 box.

I have roughly 200 hosts, with a variety of print servers, wireless access
points etc. I have one ADSL connection, which is the default gateway on all
machines.

I am running Active Directory on all servers with the DHCP scope ranging
192.168.50.1 thru 192.168.50.254 with a subnet of 255.255.255.0

Print servers, wireless access points and the router all have reservations
in the DHCP scope.

The problem.

I need more IP addresses.

I am looking for a step by step guide to adding another subnet to the
network so that all hosts on the new subnet can speak to the existing
servers and share the ADSL connection.

Thanks in advance

Maurice

"Maurice Bishop" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) et...
> The subject says it all.
>
> I have five Windows 2003 servers, each running various business apps
> including a Manufacturing Systems, Exchange Server 2003, a separate SQL
> Server 2005 box.
>
> I have roughly 200 hosts, with a variety of print servers, wireless access
> points etc. I have one ADSL connection, which is the default gateway on
> all
> machines.
>
> I am running Active Directory on all servers with the DHCP scope ranging
> 192.168.50.1 thru 192.168.50.254 with a subnet of 255.255.255.0
>
> Print servers, wireless access points and the router all have reservations
> in the DHCP scope.
>
> The problem.
>
> I need more IP addresses.
>
> I am looking for a step by step guide to adding another subnet to the
> network so that all hosts on the new subnet can speak to the existing
> servers and share the ADSL connection.
>
> Thanks in advance
>
> Maurice
>
>
>
>

Just change your mask to 255.255.0.0 and widen you scope from 192.168.50.1
thru 192.168.50.254 to 192.168.50.1 thru 192.168.51.254.

Frank

No.
Ethernet degrades after 250-300 host
Masks should never go below /24 bits (255.255.255.0) unless it is a backbone
where multiple subnets are "superneted" over the high-speed backbone.


--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

"Frankster" <(E-Mail Removed)> wrote in message
news:6-(E-Mail Removed)...
>
> "Maurice Bishop" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed) et...
>> The subject says it all.
>>
>> I have five Windows 2003 servers, each running various business apps
>> including a Manufacturing Systems, Exchange Server 2003, a separate SQL
>> Server 2005 box.
>>
>> I have roughly 200 hosts, with a variety of print servers, wireless
>> access
>> points etc. I have one ADSL connection, which is the default gateway on
>> all
>> machines.
>>
>> I am running Active Directory on all servers with the DHCP scope ranging
>> 192.168.50.1 thru 192.168.50.254 with a subnet of 255.255.255.0
>>
>> Print servers, wireless access points and the router all have
>> reservations
>> in the DHCP scope.
>>
>> The problem.
>>
>> I need more IP addresses.
>>
>> I am looking for a step by step guide to adding another subnet to the
>> network so that all hosts on the new subnet can speak to the existing
>> servers and share the ADSL connection.
>>
>> Thanks in advance
>>
>> Maurice
>>
>>
>>
>>
>
> Just change your mask to 255.255.0.0 and widen you scope from 192.168.50.1
> thru 192.168.50.254 to 192.168.50.1 thru 192.168.51.254.
>
> Frank

Buy a LAN Router or a Layer3 Switch (Switch and Router built into same
device).

Insert the Router into the LAN by simply pluging it into one of the existing
Switches.

Make the LAN Router the Default Gateway of all hosts on the network.
Make the Firewall Device the Default Gateway of the LAN Router.

The Firewall Device will keep its Default Gateway that is currently pointing
to the ISP
The Firewall Device needs any new Subnet IP Ranges added to it so that it
knows that they are "internal".
The Firewall Device needs a Static Route that tells it to use the LAN Router
as the "path" to all the LAN Subnets

Add a new Standard Scope to the DHCP Server for the new Subnet (no
Superscopes!)
Configure the LAN Router to forward DHCP Queries to the DHCP Server.

Here are some suggestions for the Static Route and IP Range on the Firewall
Device.

Subnet #1 = 192.168.50.0
Subnet #2 = 192.168.51.0

Internal Range 192.168.0.0 - 192.168.255.255
[This covers the whole RFC Range for future expansion]
Static Route
Net 192.168.0.0 Mask 255.255.0.0 Gateway <LAN Router IP#>
[This is "Superneted" to cover the whole RFC Range for future
expansion]

If there are unexpected conflicts then you will have to use a more specific
Range and more specific Static Route. But as long as there are no conflicts
you can continue to add more subnets in the future (192.168.?.?) and will
not have to adjust the Firewall. You would just add more interfaces or
virtual interfaces (VLANs) to the LAN Router and you would be done.

Once the structure is all in place you can move devices/hosts over to the
new subnet at your liesure.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------




"Maurice Bishop" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) et...
> The subject says it all.
>
> I have five Windows 2003 servers, each running various business apps
> including a Manufacturing Systems, Exchange Server 2003, a separate SQL
> Server 2005 box.
>
> I have roughly 200 hosts, with a variety of print servers, wireless access
> points etc. I have one ADSL connection, which is the default gateway on
> all
> machines.
>
> I am running Active Directory on all servers with the DHCP scope ranging
> 192.168.50.1 thru 192.168.50.254 with a subnet of 255.255.255.0
>
> Print servers, wireless access points and the router all have reservations
> in the DHCP scope.
>
> The problem.
>
> I need more IP addresses.
>
> I am looking for a step by step guide to adding another subnet to the
> network so that all hosts on the new subnet can speak to the existing
> servers and share the ADSL connection.
>
> Thanks in advance
>
> Maurice
>
>
>
>

Agreed, but... I don't think moving from 200 hosts to 201 hosts would make
any difference to his current performance (which he seems to be satisfied
with). Of course, he didn't really say how far he would expand. Just that he
ran out of IPs.

-Frank

"Phillip Windell" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
>
> No.
> Ethernet degrades after 250-300 host
> Masks should never go below /24 bits (255.255.255.0) unless it is a
> backbone where multiple subnets are "superneted" over the high-speed
> backbone.
>
>
> --
> Phillip Windell
> www.wandtv.com
>
> The views expressed, are my own and not those of my employer, or
> Microsoft,
> or anyone else associated with me, including my cats.
> -----------------------------------------------------
>
> "Frankster" <(E-Mail Removed)> wrote in message
> news:6-(E-Mail Removed)...
>>
>> "Maurice Bishop" <(E-Mail Removed)> wrote in
>> message news:(E-Mail Removed) et...
>>> The subject says it all.
>>>
>>> I have five Windows 2003 servers, each running various business apps
>>> including a Manufacturing Systems, Exchange Server 2003, a separate SQL
>>> Server 2005 box.
>>>
>>> I have roughly 200 hosts, with a variety of print servers, wireless
>>> access
>>> points etc. I have one ADSL connection, which is the default gateway on
>>> all
>>> machines.
>>>
>>> I am running Active Directory on all servers with the DHCP scope ranging
>>> 192.168.50.1 thru 192.168.50.254 with a subnet of 255.255.255.0
>>>
>>> Print servers, wireless access points and the router all have
>>> reservations
>>> in the DHCP scope.
>>>
>>> The problem.
>>>
>>> I need more IP addresses.
>>>
>>> I am looking for a step by step guide to adding another subnet to the
>>> network so that all hosts on the new subnet can speak to the existing
>>> servers and share the ADSL connection.
>>>
>>> Thanks in advance
>>>
>>> Maurice
>>>
>>>
>>>
>>>
>>
>> Just change your mask to 255.255.0.0 and widen you scope from
>> 192.168.50.1 thru 192.168.50.254 to 192.168.50.1 thru 192.168.51.254.
>>
>> Frank
>
>

That's true. Heck you could probably go to maybe 400+ machines on a segment
if it is a situation where they aren't all turned on at the same time,
especially if it is fully Switched and runs over gigabit.

But I don't believe in creating a Topology that gives you the easy abiltiy
to do something you should not do, that is, create a situation that
encourages a bad practice. It's like the phrase "give'em enough rope and
they'll hang themselves". Also once you create a Topology like that and
machines are placed on those addresses that "spill over" into the addresses
beyond what the /24 mask would have given,...it can become complicated to
"fix" that and redesign the Topology back to what it should be. It is
always easier to expand a segment than it is to shrink it back to what it
should be after it is grown out of proportion.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

"Frankster" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) ...
> Agreed, but... I don't think moving from 200 hosts to 201 hosts would make
> any difference to his current performance (which he seems to be satisfied
> with). Of course, he didn't really say how far he would expand. Just that
> he ran out of IPs.
>
> -Frank
>
> "Phillip Windell" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
>>
>> No.
>> Ethernet degrades after 250-300 host
>> Masks should never go below /24 bits (255.255.255.0) unless it is a
>> backbone where multiple subnets are "superneted" over the high-speed
>> backbone.
>>
>>
>> --
>> Phillip Windell
>> www.wandtv.com
>>
>> The views expressed, are my own and not those of my employer, or
>> Microsoft,
>> or anyone else associated with me, including my cats.
>> -----------------------------------------------------
>>
>> "Frankster" <(E-Mail Removed)> wrote in message
>> news:6-(E-Mail Removed)...
>>>
>>> "Maurice Bishop" <(E-Mail Removed)> wrote in
>>> message news:(E-Mail Removed) et...
>>>> The subject says it all.
>>>>
>>>> I have five Windows 2003 servers, each running various business apps
>>>> including a Manufacturing Systems, Exchange Server 2003, a separate SQL
>>>> Server 2005 box.
>>>>
>>>> I have roughly 200 hosts, with a variety of print servers, wireless
>>>> access
>>>> points etc. I have one ADSL connection, which is the default gateway on
>>>> all
>>>> machines.
>>>>
>>>> I am running Active Directory on all servers with the DHCP scope
>>>> ranging
>>>> 192.168.50.1 thru 192.168.50.254 with a subnet of 255.255.255.0
>>>>
>>>> Print servers, wireless access points and the router all have
>>>> reservations
>>>> in the DHCP scope.
>>>>
>>>> The problem.
>>>>
>>>> I need more IP addresses.
>>>>
>>>> I am looking for a step by step guide to adding another subnet to the
>>>> network so that all hosts on the new subnet can speak to the existing
>>>> servers and share the ADSL connection.
>>>>
>>>> Thanks in advance
>>>>
>>>> Maurice
>>>>
>>>>
>>>>
>>>>
>>>
>>> Just change your mask to 255.255.0.0 and widen you scope from
>>> 192.168.50.1 thru 192.168.50.254 to 192.168.50.1 thru 192.168.51.254.
>>>
>>> Frank
>>
>>
>