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 1 day 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.

One thing i experimented with is creating a superscope 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.

Many thanks.

"jasonb007" <jasonb007@discussions.microsoft.com> wrote:
> 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 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.
>

If you do not change this, you are stuck with 126 IP addresses, DHCP has
nothing to do with it. You need to get at least as many addresses than hosts
on your LAN.

ThePro

I know it's nothing to do with DHCP, but the subnet mask that needs changing
- it's was just a huge (& costly !!) task to get this changed by the
authority involved.

"ThePro" wrote:

> "jasonb007" <jasonb007@discussions.microsoft.com> wrote:
> > 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 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.
> >
>
> If you do not change this, you are stuck with 126 IP addresses, DHCP has
> nothing to do with it. You need to get at least as many addresses than hosts
> on your LAN.
>
> ThePro
>
>
>