We have a school server setup with an IP of 172.24.53.2 and a DHCP range setup from 172.24.53.10 to 172.24.53.126, Subnet 255.255.255.128. The lease is set to 8 hours as we get close to running out of IP addresses when staff bring in there wireless laptops. We need to add some more PC's to the network which will push us over the number of IP addresses available. What's the best way to increase the range? There are managed network switches, printers, wireless points, projectors on the LAN so don't want to have to reconfigure all the devices if possible. The school LAN is setup as 2 VLANS, one for admin, the other for curriculum and the issue is on the curriculum side. The gateway/router is setup as IP 172.24.53.1 and Subnet
255.255.255.128 by the local authority so we can't alter this (and they wont change it anyway!)
One thing i experimented with (on a test network, not live!)is creating a superscope (because thats what 2003 server prompts me to do when I enter the large range) that includes a scope ranging from 172.24.53.10 to 126 and another scope from 129 to 250. But anything that gets an IP from the "secondary scope", 129 or above, can't ping the server or see shared resources. If I release the IP and make it get one from the 10 to 126 range, I can ping and see shared resources.
Someone mentioned I should add a static route to the second DHCP scope so it can see the first scope. Can anyone advise how I can do this in Windows Server 2003 or an alternative solution.
Other points to mention, the server has one NIC but I can add another if required.
Many thanks.
255.255.255.128 by the local authority so we can't alter this (and they wont change it anyway!)
One thing i experimented with (on a test network, not live!)is creating a superscope (because thats what 2003 server prompts me to do when I enter the large range) that includes a scope ranging from 172.24.53.10 to 126 and another scope from 129 to 250. But anything that gets an IP from the "secondary scope", 129 or above, can't ping the server or see shared resources. If I release the IP and make it get one from the 10 to 126 range, I can ping and see shared resources.
Someone mentioned I should add a static route to the second DHCP scope so it can see the first scope. Can anyone advise how I can do this in Windows Server 2003 or an alternative solution.
Other points to mention, the server has one NIC but I can add another if required.
Many thanks.
