Hi and thanks for your reply.

If I change the NIC card details to 255.255.255.0, increase the range as
suggested (think i'll have to delete the existing DHCP scope to do this),
will I still be able to see all the other devices on the network with the
subnet of 255.255.255.128 as per my previous post, we can't change the router
details because the other network needs to be left alone.

One thing i messd 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, ca'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.

Thanks.

"Calab" wrote:

>
> "jasonb007" <jasonb007@discussions.microsoft.com> wrote in message
> news:C7C42925-C841-4B1F-BBE5-AD2358305435@microsoft.com...
> | 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.
>
> So, your network is 172.24.53.0/25...
>
> <snip>
>
> | side. The gateway/router is setup as IP 172.24.53.1 and Subnet
> 255.255.255.0
>
> Your router has the network set up as 172.24.53.0/24.
>
> Simply change your DHCP server from serving the IP range (.10 to .126), to
> serving the larger range set up in your router (.10 to .254). The only place
> you'll need to make changes will be in any machine that is hard coded with
> it's IP address... You'll need to change the mask from 255.255.255.128 to
> 255.255.255.0.
>
> Also, consider shortening your lease times to 1 hour to free up used IP's
> sooner.
>
>
>

"jasonb007" <jasonb007@discussions.microsoft.com> wrote
> anything that gets an IP from the "secondary scope", 129 or above, ca't
> ping
> the server or see shared resources.

You would need to add a static route to the second DHCP scope so it can
"see" the first scope.

Brian

Brian,

thanks for your input - can you advise on how a static route is setup.

Many thanks

"Brian" wrote:

> "jasonb007" <jasonb007@discussions.microsoft.com> wrote
> > anything that gets an IP from the "secondary scope", 129 or above, ca't
> > ping
> > the server or see shared resources.
>
> You would need to add a static route to the second DHCP scope so it can
> "see" the first scope.
>
> Brian
>
>
>