hi, currently im maintaining almost 200+ workstations and including 2 servers.each servers has different functions. now, we are planning to deploy another add't 100 workstation.since, our network are static ip's.i will now exceed to 254 hosts. im asking your suggestion what would be the best yet simple and costless network lay-out,equipments,software,etc that all clients will communicate each other.thanks!

Managed layer 3 switches that are VLAN capable would help. You could setup VLAN's and configure routing on them. You could also buy a router (not a SOHO router, but a real one) and just use subnetting and route between them to allow communication between subnets. If you know Linux or UNIX, you could build a router from one of those two OS's.

change your scope from a class c to a class b [172.16.0.0 to 72.31.255.255 with subnet mask 255.240.0.0]address range. No cost involved just labor. Might be a good time to convert everyone [except servers and switches] to dhcp. Imagine the power if you knew how to internet search

If you have an old box laying around collecting dust you could use that as a DHCP server. Put a distro of Linux on it such as Ubuntu. If thats out of the question, what Wanderer suggested is your best bet. Nowadays it's not practical to use static addresses for your workstations. But, if you must, check out the LMHOSTS file which allows you to maintain a central LMHOSTS file for your network, and host it on a server. The workstations will use that LMHOSTS file as if it was on the local machine. "Computer security." — Oxymoron

@CurtR: this is very nice way but i think i need extra budget on this.Thanks. Maybe i can use this in my different sites. @wanderer: i will adopt your suggestion,just a little confuse with your addressing and subnetting .sorry im just starting to learn addressing/subnetting.

What I listed is the range of private class b addresses. Simply pick one range between those. Note: I just noticed my printout from Morenet on private ips is wrong. 172.x.x.x to 72.x.x.x should be 172 to 172 not 72. Here is a paste from another site: Class B network IP address range = 172.16.0.0 - 172.16.255.255 Class B network IP address range = 172.17.0.0 - 172.17.255.255 Class B network IP address range = 172.18.0.0 - 172.18.255.255 ... Class B network IP address range = 172.31.0.0 - 172.31.255.255 For each of the 16 Class B networks: Subnet mask = 255.255.0.0 Network address length = 16 bit Computer address length = 16 bit Perhaps this will help http://www.howstuffworks.com/questi... Imagine the power if you knew how to internet search Oh and since the hosts file is now cached by MS there is no need for the lmhosts file. Just use the hosts file.

@CurtR: this is very nice way but i think i need extra budget on this.Thanks. Maybe i can use this in my different sites. Yes, upgrading equipment always leaves one with budget considerations. However, if you have multiple sites, VLAN's would definately be the way to go as most any VLAN capable switch allows multiple VLAN's on the same switch. This is great for WAN's when you have user's in separate locations who need to be on the same subnet.