cbrasga

Sounds like they do not have proper permissions to one or more shares. Additionally, if you have their Active Directory user accounts setup with a Home Directory and Drive Letter you could just use "NET USE /HOME" instead of "net use H: \\ruffles\rnfile\Users\%USERNAME%".

VLANs would be the simplest route.

Bottom Line Meraki: Great for Public WiFi (no recurring costs for Public WiFi APs aka "Pro License", cheap 802.11g APs). Ruckus: Great for enterprise wireless (best in class wireless technology, excellent management, and competitive pricing). Note: If you're curious about Meraki's management interface, you can create an account and login. https://account.meraki.com/login/new_account

The Ruckus APs only go to the zone director for authentication and config, all other data traffic would be direct. Are they all "gateway APs" (cabled to the network) or are some of them meshing to get to a gateway AP? Run inSSIDer or netstumbler real quick to check the channels and for other APs. Otherwise, are there any other wireless devices, phones, or even microwaves ovens in the area?

If you're running Windows XP, Windows SteadyState allows for that option. http://farm3.static.flickr.com/2038/2400628229_746a2bcaa3.jpg

Ruckus APs are individually manageable, if you're comfortable with eBay, I'm seeing 802.11g Zoneflex 2942's for $269 each, so you could get 3 within your budget.

I'm simply advocating, right sizing an organization's network (not subnets, the whole network). With a /21 on a 10.x.x.x network that accommodates 8192 networks with 2046 devices per network. So if the organization is going to come close to using 8,000 subnets (including room for growth) then go ahead and use a 10.x.x.x network. If an organization will have closer to 30 subnets, which is more realistic, then use a 172.16.x.x /21 allowing for 32 networks and 2046 hosts per.

To put it into a simple physical analogy, lets say the network addressing space is a piece of land and a subnet is a house. You can build 10 houses on a 16,000,000 acre piece of land and even though each house is self-contained and cozy, it's a waste of land for just those 10 houses. I'm coming from the arena of having a logical and orderly network. Why use a class A if you're subnetting down to only a few networks or hosts?

I understand he will be subnetting the 10.x.x.x network, but I would still stay away from using a Class A network unless there will actually be a need for it. Even with subnetting it is a waste of a Class A network because it will be extremely underutilized. Use a Class B network.

Updating the boot rom requires a reboot of the switch. Also, in some cases it requires upgrading versions incrementally. (i.e. 10.1 > 10.5 > 11.0).

While Ruckus makes an awesome product. A budget of $1000 will only get you 1 or 2 ruckus APs. Are you looking for simply wireless internet access or internal network access as well?

Do you have any other services/applications on that server running on the following ports: Port 67 (DHCP) Port 69 (TFTP) Port 4011 (PXE)

As a helpful in between (web vs console), type "menu" in the console for a menu driven setup of VLANs or other basic switch configuration. Won't do everything that the command line can but can still do a bit more than the web interface, pretty helpful when getting used to the command line.

I would split your network, create a VLAN for the "business" side and one for the classrooms and setup routing between. Because they will be on different IP networks, you can DHCP different gateways while still using the same DNS servers.

First recommendation, get away from the 10.x.x.x network. Unless you see yourself ever coming close to using 16,000,000 addresses or need an obscene amount of networks, go with a Class B (172.16.0.0 - 172.31.255.255). Most 10.x.x.x networks never even scratch 1% of the IP address allocation. People use that network as the lazy way to never run out of addresses, rather than taking time to plan a logical network(s). A 10.x.x.x network can take days to scan if you ever feel like discovering/auditing your network resources. Additionally, I see A LOT of organizations go with a the 10.x.x.x networks, so if your company/school connects or merges with another organization/network which coincidentally runs on a 10.x.x.x, you will run into conflicts/routing issues. Second, broadcast domains used to be a big issue back in the day because every broadcast needs to get processed by the CPU. With today's powerful CPUs it is hardly an issue, but that is still no reason not to run a clean network. I would recommend no larger than 512 nodes per network segment. So VLANs are your friends. I agree with your allocations beginning with Static IPs first then Dynamic IPs. Personally, I would setup ranges for your devices, for example .20-.49 for switches, .50-.69 for servers, .70-.99 for wireless. It makes IDing IPs/devices easier rather than having to reference a list because the device type changes at a random number. I'm also a little surprised you didn't include any spares for your "General Purpose Servers". Lastly, don't you mean the IP will being using a /24 mask rather than /32? Unless you're using the mask to specifically identify the IP address itself in the list. Just my 2 cents. Also, if you want to fly me out to Australia I'd be happy to help you with the project.