DHCP Scope problem

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.

There's a limit to what you can run on the VLAN that's directly connected to
the router provided by the local authority, but there's no limit to what you
can run on your switched network behind the gateway.
On the DHCP server, no matter which VLAN it is on, create a unique scope for
each VLAN. Then set up an ip helper address in the VLAN properties on the
switch to forward DHCP requests to the DHCP server.
Hope that helps,
Anthony,
http://www.airdesk.co.uk




"jasonb007" <(E-Mail Removed)> wrote in message
news:FEDF5B3E-7A7B-401C-86AA-(E-Mail Removed)...
> 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.
>

Anthony, thanks for your reply. The biggest issue I have is the local
authority, they hold all the usernames & passwords for the router and
switches and won't "help us help them" by giving us the information so we can
simply change the subnet mask. So I was just looking at other alternatives
as the school has to pay for the service to be carried out and I was hoping
to help them out.

Many thanks

"Anthony [MVP]" wrote:

> There's a limit to what you can run on the VLAN that's directly connected to
> the router provided by the local authority, but there's no limit to what you
> can run on your switched network behind the gateway.
> On the DHCP server, no matter which VLAN it is on, create a unique scope for
> each VLAN. Then set up an ip helper address in the VLAN properties on the
> switch to forward DHCP requests to the DHCP server.
> Hope that helps,
> Anthony,
> http://www.airdesk.co.uk
>
>
>
>
> "jasonb007" <(E-Mail Removed)> wrote in message
> news:FEDF5B3E-7A7B-401C-86AA-(E-Mail Removed)...
> > 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.
> >
>
>
>

Ah! I assumed you meant they controlled the router. I did not appreciate
they also control the switches, ie your LAN infrastructure.
You mentioned two VLAN's. Is the only problem that they don't have ip helper
addresses to forward the DHCP requests? In that case you just need to have a
DHCP service on each VLAN.
Anthony,
http://www.airdesk.co.uk


"jasonb007" <(E-Mail Removed)> wrote in message
news:5B8E6F0C-E066-411F-BFCA-(E-Mail Removed)...
> Anthony, thanks for your reply. The biggest issue I have is the local
> authority, they hold all the usernames & passwords for the router and
> switches and won't "help us help them" by giving us the information so we
> can
> simply change the subnet mask. So I was just looking at other
> alternatives
> as the school has to pay for the service to be carried out and I was
> hoping
> to help them out.
>
> Many thanks
>
> "Anthony [MVP]" wrote:
>
>> There's a limit to what you can run on the VLAN that's directly connected
>> to
>> the router provided by the local authority, but there's no limit to what
>> you
>> can run on your switched network behind the gateway.
>> On the DHCP server, no matter which VLAN it is on, create a unique scope
>> for
>> each VLAN. Then set up an ip helper address in the VLAN properties on the
>> switch to forward DHCP requests to the DHCP server.
>> Hope that helps,
>> Anthony,
>> http://www.airdesk.co.uk
>>
>>
>>
>>
>> "jasonb007" <(E-Mail Removed)> wrote in message
>> news:FEDF5B3E-7A7B-401C-86AA-(E-Mail Removed)...
>> > 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.
>> >
>>
>>
>>