maximum devices

I took over a network where the IP scheme was 192.0.0.1  - 192.0.0.254 all with subnet of 255.255.255.0 . We are getting close to using up all of the IP addresses from 1-254, what would be the best way to expand the range of addresses? It's all windows 2000 based and we are in 1 location.
BeksterAsked:
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.

pseudocyberCommented:
In my opinion, the best way to expand would be to change the subnet mask only - change it to 255.255.253.0 and this will give you 510 addresses in the range of 192.0.0.1-192.0.1.254.

If you need more, change it to 255.255.252.0 and this would give you 1022 addresses:  192.0.0.1-192.0.3.254.
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
neteducationCommented:
Use subnet 255.255.254.0 and your range goes from 192.0.0.1 to 192.0.1.254

However 192.0.0.x is a bad network to choose, as those are offcial adresses. 192.168.x.x are the offical internal one... or now that you have a little bigger network you may as well go for 172.16.0.0 and use a netmask of 255.255.0.0 like this you have 65534 hosts and this is also an official intranet-range
0
pseudocyberCommented:
For a little more detail:

IP Address       : 192.0.0.0
Address Class    : Classless /23
Network Address  : 192.0.0.0

Subnet Address   : 192.0.0.0
Subnet Mask      : 255.255.254.0
Subnet bit mask  : nnnnnnnn.nnnnnnnn.nnnnnnnh.hhhhhhhh
Subnet Bits      : 23
Host Bits        : 9
Possible Number of Subnets : 1
Hosts per Subnet : 510

OR

IP Address       : 192.0.0.0
Address Class    : Classless /22
Network Address  : 192.0.0.0

Subnet Address   : 192.0.0.0
Subnet Mask      : 255.255.252.0
Subnet bit mask  : nnnnnnnn.nnnnnnnn.nnnnnnhh.hhhhhhhh
Subnet Bits      : 22
Host Bits        : 10
Possible Number of Subnets : 1
Hosts per Subnet : 1022


0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

BeksterAuthor Commented:
So with a subnet of 255.255.255.253 a computer with an ip of 192.0.0.25 can communicate with a computer with the IP of 192.0.1.50
0
pseudocyberCommented:
Neteducation - good catch on the 192.168.0.0 ... that went right past me.  Duh.
0
pseudocyberCommented:
NO - with a subnet mask of 255.255.253.0.  
0
neteducationCommented:
believe me, it's 255.255.254.0, not 255.255.253.0
0
BeksterAuthor Commented:
ok so is 192.168.X.X the equivilent of 192.0.X.X - in that a subnet mask of 255.255.255.0 would give me 255 addresses in each scenario and 255.255.253.0 would give me 510? (which would be plenty) So the only benefit of using 192.168.X.X is that it is more of an accepted standard for private ranges
0
pseudocyberCommented:
Yeah, sorry about that.  

.254 = 510 hosts
.252 = 1022 hosts
.248 = 2046 hosts
0
pseudocyberCommented:
Yes, 192.0.0.0 is actually reserved by the IANA (Internet Assigned Numbers Authority).

192.168.0.0/26 (255.255.0.0) is set asside as "Private IP Addressing" and does not require any special authorization to use.
0
pseudocyberCommented:
However, if it would be a real pain in the ___ to renumber your whole network to a totally different IP scheme - you could put it off by using a Network Address Translation (NAT) device, such as a firewall or router, to change your addresses to a public IP (probably provided by your Internet provider).

If you don't connect to the Internet, you have no worries, until you do.

... but if you're considering changing your subnet mask to expand your range anyway ... now might be a good time to renumber your network - say to 172.16.1.0/23 (mask 255.255.253.0) which would give you 510 addresses.  Alternatively, if you have a router in your core network, or a layer 3 switch, you could simply have two /24 networks and route between them - you could have a user VLAN and a Server VLAN or whatever.
0
BeksterAuthor Commented:
ok pseudo 255.255.0.0 is used with 192.168.x.x? how many addresses does that allow me to go up to 192.168.(0-255).X which would be a boatload?

also is there any way to migrate over from 192.0.0.x or would i have to shutdown all devices on the network and do it all in one shot
0
BeksterAuthor Commented:
what's the big benefit of going with 172.16.x.x over 192.168.x.x
0
dyablonsCommented:
you are confusing .252 and .253.  Note the detailed post above.
there is no .253 subnet mask.   Use .254 or .252.  But also note the comments about about 192.168 and 192.0.  If you are using 192.0.X.X, While a router will allow you to use a mask of  .254 for 510 users or .252 for 1022 users,  the addresses beyond your 192.0.0X are not yours to use on the internet. The way to get more legitimate IP addresses is to ask for more IANA (or whoever is handing out ip addresses nowadays) or to  use NAT (the preferable way to go)
 

0
BeksterAuthor Commented:
dya ok i see.  We are using ISAServer for net access to I don't believe we will ever need public IP's for desktops except for a few servers which already have public addresses from our ISP for mail/www etc

at what point to vlans make sence as apposed to just expanding the IP range.  If we have 255 devices should we just go to .254 subnet or split up the lan in 2
0
pseudocyberCommented:
The benefit of going with the 172.16.0.0 instead of a 192.168.0.0 is that a lot of the Small Office Home Office gear likes to use 192.168.0.0 and 192.168.1.0 - and if you ever try to do something with them, like VPN it just avoids some hassle later.  They're both reserved private address ranges. (There's also 10.0.0.0/8 which you could subnet anyway you feel like.).
0
pseudocyberCommented:
Thanks for the points, but you should have split them - given some Bekster for pointing out my mistakes.
0
BeksterAuthor Commented:
i am bekster lol
0
dyablonsCommented:
Ok ignore most of  my previous post, I only read part of the thread. Let me read the rest to catch up.  
0
pseudocyberCommented:
Geez, I'm really not this dense - doing too many things at once.  dyablons and neteducation.  Thanks.
0
dyablonsCommented:
Alright I thingk I am up to date.  Use 192.168.y.x or 172.16.y.x. and a  /23 -255.255.252.0 subnet mask. Just make "y" somthing other than 0 or 1 to avoid any problems  that pseudocyber is worried about. A great freetool to use for addressing is the solarwinds subnet calulator - http://www.solarwinds.net/FreeTools.htm.  No more stressing over binary math.   As for vlans, it depends on what you are trying to achieve. They could be used for security purposes, to segemnet broadcast domains, ect.  If you don't have any performance issues or security needs,  I would not worry about VLANs.  I will follow up with advice on making the actual changes after I check that you question was not already answered.  
0
dyablonsCommented:
Ok as far as coversion goes are you using static IP's or DHCP? also some idea of how your routing and switching infrastucture is set up will help.
0
BeksterAuthor Commented:
Using DHCP and we have a number of Baystack switches setup all trunked.  No routers
0
dyablonsCommented:
Hmmm,  somewhere there should be a router between your network and the rest of the world. Do you have a Firewall?  How do you connect to your ISP? Do they manage your router and just hand off an ethernet connection?  Are you using Cable/DSL? Was the 192.0.0.X assigned to you or were you just using it?  As far as making the switch,  you have to change the scope on your dhcp sever. make sure you exclude Ip adresses for you servers and networking gear.  Make the change before the weekend so when the IP leases expire they will be renewed with the new adresses. Then you need to change the static IPs on the servers.   If you want to use vlans at some point you need a router to provide connectivity between the vlans.
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
Networking

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.