Routing? need different networks but all to talk

Ok guy's this one is a challenge for me:
Situation, the business is running out of IP addresses and I would like to find a solution to the problem:
standard MS Win 2003 server, dhcp, DNS etc, file services about 30 users/pc's/laptops all up
now the complicating issue:
they have gaming machines (not games machines) abut 150 each needs a static IP
they have racing TV's connected to IP abut 50 each needs IP address
They have cash registers each needs IP address
all of these report back to the server and software for reporting etc

So....Obviously they have run out of IP addresses (or will)
Do I
Change the subnet to say (or something like that) to make the network larger and thus more clients on the network?
I know Vlaning would be good but the cabling here is a mess and as this operation runs nearly 24/7 would not be viable.
I's love to do something like this
Server network/PC's etc - 10.1.1.x
Gaming Machines: 10.1.10.x - 10.1.11.x
TV's:                      10.1.20.x
Cash tills:                10.1.30.x
Subnet: or
this would give us 254 addresses plus per network i guess
Would this work or would i need to put in a compex router solution to make this work?

Thanks for any help suggestion you can advise.
they all need internat access and reporting back to the server and software.
Who is Participating?
If you can keep this simple I would. Keep the network the same, just expand the subnet. You can accomplish this by changing the subnet mask of the Win 2003 Server, and for all the clients through DHCP Configuration settings, change to, this will increase your network to 64k possible IPS, you can then then modify the DHCP scope to cover the calculate amounted of IP that you will  actually need to be assigned. This will allow you to fix the issue with minimal change (which is usually the best). The only reason you would want to break up the network into separate subnets or VLAN would be to prevent certain devices, apps, or services from creating a ton of network noise and traffic, such as multicast traffic. This would be necessary if you are running iSCSI or a SAN, or IP Video, but may not be necessary for the types of devices that you have described. Let me know if this helps.
Michael OrtegaSales & Systems EngineerCommented:
What kind of Router do you have? You can certainly subnet as your detailed above, but you need to make sure your routing equipment is adequate to route for all those subnets. Also if you create new subnets for your various devices you realize you'll have to go back and reassign a static IP or at least get their hardware address and setup DHCP reservations.

magtech1Author Commented:
Hi MO,
thanks for the reply
i have a Netgear FVS318 router currently
Would i need to set it up to route as required? what sort of settings would i need to put in it? wouldn't i just setup the LAN port with IP subnet

Yes i know there would be significant pain in resetting their static IP's, but would certainly clean it all up and allow us to then record each device and it's IP, longer term gain i feel.
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

Michael OrtegaSales & Systems EngineerCommented:
You mentioned that you wanted to break up your networks, e.g. 10.1.1.x, 10.1.10.x, 10.1.20.x, etc. All masked with 16 bit mask ( That means that your would have to set separate gateways for each subnet, e.g.,,, etc. With this configuration you'll need to VLAN unless you have dedicated switches for each set of devices that you can physically separate your network. I'm not sure that 318 allows you configure each LAN interface as separate gateways or do 802.1q trunking.

You can either expand your existing subnet or you'll need a different firewall/router to break the networks up.

Michael OrtegaSales & Systems EngineerCommented:
Of course you can only easily do that subnet expansion if you are using a Class A or B subnet already. If you're using a 192.168.x.x subnet then you'll have to create a new ip address scheme using 172.16-31 or 10.x.x.x.

Thank you Mgortega, that is correct. And even if you have to change the IP class, this would be a more simply approach than breaking up into several subnets or vlans, (in my opinion)
magtech1Author Commented:
thanks guy's
what i wanted confirmed.
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.

All Courses

From novice to tech pro — start learning today.