It is all a matter of routing... the 192.168.0.x hosts will contact their
default gateway to reach the 192.168.2.x subnet. Is your DNS/DHCP server the
default gateway as well? If it is, then your server is not acting as a
router. However, I believe that you are complicating things unnecessarily
(to put it mildly). Why not define a scope for a subnet like 192.168.0.0
with 255.255.252.0 as subnet mask? This will give you over 1000 valid IPs,
from 192.168.0.1 to 192.168.3.254.
--
Regards,
Adrian Grigorof
www.altairtech.ca/evlog - Free event log monitoring
www.altairtech.ca/troubleticket
"jagsrao" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi,
> We have a Windows2003 Server acting as a DHCP Server with the address
> 192.168.0.1 to 190.168.0.255. The same is also acting as a DNS Sever
> for IPs 192.168.1.1 to 192.168.1.255. We were running out of IP for
> DHCP. Hence we created another scope 192.168.2.x in DHCP.
> When we connected another PC in the DHCP, it did not get 2.x address.
> We added a superscope. Even then it did not work. We then added the
> server as a router adding 192.168.2.1 as an additional IP. We then
> added 192.168.2.3 to the PC. Now, it was communicating with 2.1 but
> not with other IPs in the other subnets (viz 192.168.0.x and
> 192.168.1.x)
> At the server, it is not able to ping to 192.168.2.1 which is an
> additional IP of its interface.
> Where are we going wrong ?
>
> Thanks
>
> Regards
>
> Jagdish
>
Similar Threads
