Communication between to different subnets using one DHCP server.

Is it possible? I mean when you have one network operating on subnet
192.168.0.0 /24 for example, and then you add another scope of network
192.168.1.0 /24. Then you superscope them. I can ping the ip add of router
set to 192.168.0.2 (for network 192.168.0.0 and then DHCP ip add is set to
192.168.0.1) for example in network 192.168.1.0 (w/c router ip add is set
192.168.1.1). But when I try to ping ip add of machine like for example
192.168.0.56 in network 192.168.1.0, it shows request time out, can't
communicate? Is there a way to resolve this issue?

Any feedback regarding this will be highly appreciated ^_^

Im just playing around DHCP server, i'm just confuse.

Thanks,
Joed

Joed

Try 255.255.0.0

--
Mitch Garvis
Microsoft MVP: Essential Server Solutions
http://garvis.ca/blogs

"Joed" <> wrote in message
news:C64BE318-64F6-4542-BEF7-...
> Is it possible? I mean when you have one network operating on subnet
> 192.168.0.0 /24 for example, and then you add another scope of network
> 192.168.1.0 /24. Then you superscope them. I can ping the ip add of router
> set to 192.168.0.2 (for network 192.168.0.0 and then DHCP ip add is set
> to
> 192.168.0.1) for example in network 192.168.1.0 (w/c router ip add is set
> 192.168.1.1). But when I try to ping ip add of machine like for example
> 192.168.0.56 in network 192.168.1.0, it shows request time out, can't
> communicate? Is there a way to resolve this issue?
>
> Any feedback regarding this will be highly appreciated ^_^
>
> Im just playing around DHCP server, i'm just confuse.
>
> Thanks,
> Joed

Montreal_MCT

On Dec 14, 8:36*pm, "Montreal_MCT" <y...@right.ca> wrote:
> Try 255.255.0.0
>
> --
> Mitch Garvis
> Microsoft MVP: Essential Server Solutionshttp://garvis.ca/blogs
>
> "Joed" <J...@discussions.microsoft.com> wrote in message
>
> news:C64BE318-64F6-4542-BEF7-...
>
>
>
> > Is it possible? I mean when you have one network operating on subnet
> > 192.168.0.0 /24 for example, and then you add another scope of network
> > 192.168.1.0 /24. Then you superscope them. I can ping the ip add of router
> > set to *192.168.0.2 (for network 192.168.0.0 and then DHCP ip add is set
> > to
> > 192.168.0.1) for example in network 192.168.1.0 (w/c router ip add is set
> > 192.168.1.1). But when I try to ping ip add of machine like for example
> > 192.168.0.56 in network 192.168.1.0, it shows request time out, can't
> > communicate? Is there a way to resolve this issue?
>
> > Any feedback regarding this will be highly appreciated ^_^
>
> > Im just playing around DHCP server, i'm just confuse.
>
> > Thanks,
> > Joed- Hide quoted text -
>
> - Show quoted text -

in the test world, i'm not 100% sure but I think you have to multi-
nome the server with one NIC per subnet. in the real world you have
VLAN's set up then there is a switch setting called IP Helper where
you put in the DHCP server address. this way if you 10 VLAN's it's
easy for a client to get to one central DHCP server. the client sends
out a DHCP request, switch detects it and forwads it to the right DHCP
server

sql_noob

"sql_noob" <> wrote in message
news:98d05e7b-4f1c-41b6-9898-...

On Dec 14, 8:36 pm, "Montreal_MCT" <y...@right.ca> wrote:

> "Joed" <J...@discussions.microsoft.com> wrote in message
>
> news:C64BE318-64F6-4542-BEF7-...
>
>
>
> > Is it possible? I mean when you have one network operating on subnet
> > 192.168.0.0 /24 for example, and then you add another scope of network
> > 192.168.1.0 /24. Then you superscope them. I can ping the ip add of
> > router
> > set to 192.168.0.2 (for network 192.168.0.0 and then DHCP ip add is set
> > to
> > 192.168.0.1) for example in network 192.168.1.0 (w/c router ip add is
> > set
> > 192.168.1.1). But when I try to ping ip add of machine like for example
> > 192.168.0.56 in network 192.168.1.0, it shows request time out, can't
> > communicate? Is there a way to resolve this issue?
>
> > Any feedback regarding this will be highly appreciated ^_^
>
> > Im just playing around DHCP server, i'm just confuse.


> Try 255.255.0.0

Placing the networks in a common subnet would certainly resolve the
communications aspect, but then you'd not have two separate networks, you
would only have one network with a larger single subnet.


> in the test world, i'm not 100% sure but I think you have to multi-
> nome the server with one NIC per subnet. in the real world you have
> VLAN's set up then there is a switch setting called IP Helper where
> you put in the DHCP server address. this way if you 10 VLAN's it's
> easy for a client to get to one central DHCP server. the client sends
> out a DHCP request, switch detects it and forwads it to the right DHCP
> server

You can actually manage and route traffic to two different subnets on the
same NIC connection. Configure the NIC of the DHCP server with addresses on
*both* subnets (e.g. 192.168.0.1 and 192.168.1.1), and then enable IP
Routing on the machine. TCP/IP traffic can be routed in/out to two different
subnets on the same NIC. This is not the conventional physical topology, but
because physical and logical layers are separated, it's certainly possible.
Just the same as you can connect four nodes from two completely different IP
networks onto the same hub (or switch), and those two 'networks' will
happily truck on as if they were physically isolated -- not a conventional
configuration, but certainly functional.



--
Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

Lawrence Garvin \(MVP\)