I am an assistant network administrator at a medium-sized school that has one Win 2003 server with about 140 PCs, 35 WAPs, and 15+ network printers connected to it. We curently have one scope, 10.0.0.50-10.0.0.254 (or 204 valid IPs). As you can see, with the 190 clients plus the few laptops that teachers and miscellaneous counselors, etc bring in, we're running out of IPs to assign.
My question is: If we configure another scope, say 10.0.1.50-10.0.1.254, we also will have to configure the clients on that scope to use subnet mask 255.255.0.0 instead of the current 255.255.255.0, correct? And if that is correct, that would put those clients on a different network than the printers and WAPs?
*****UPDATE*****
We created a new scope, 10.0.1.50-10.0.1.254, and moved all of our WAPs to it. We reserved IPs for each one, and manually configured each to get a specific IP address instead of letting DHCP assign one. So far, we seem to have solved the problem of having to reset them every day.
There's a new issue now. After moving them to the new scope, we cannot log into the WAPs via IE (or firefox (from any client machine or the server itself)) to configure settings of check logs. We used to just type in the IP address of the WAP, enter the password, and get right in. Now when we enter the new 10.0.1.xx IP, it says it doesn't exist. Is there something in the server' TCP/IP properties that we need to adjust?
Any advice is aprecciated.
My question is: If we configure another scope, say 10.0.1.50-10.0.1.254, we also will have to configure the clients on that scope to use subnet mask 255.255.0.0 instead of the current 255.255.255.0, correct? And if that is correct, that would put those clients on a different network than the printers and WAPs?
*****UPDATE*****
We created a new scope, 10.0.1.50-10.0.1.254, and moved all of our WAPs to it. We reserved IPs for each one, and manually configured each to get a specific IP address instead of letting DHCP assign one. So far, we seem to have solved the problem of having to reset them every day.
There's a new issue now. After moving them to the new scope, we cannot log into the WAPs via IE (or firefox (from any client machine or the server itself)) to configure settings of check logs. We used to just type in the IP address of the WAP, enter the password, and get right in. Now when we enter the new 10.0.1.xx IP, it says it doesn't exist. Is there something in the server' TCP/IP properties that we need to adjust?
Any advice is aprecciated.