DHCP Question

I have 2 domains on the same physical segment. Domain 1
addresses 192.168.100.0/24 (NT 4 Server) and Domain 2
192.168.200.0/24 (Windows 2003 Server). There is a trust
setup between the two domains using RRAS (Windows 2003)
with 2 NICs and a static route. One NIC is 192.168.100.1
other NIC is 192.168.200.1. My question is how can I set
DHCP on each domain to only supply addresses for it's own
domain. I want both DHCP servers to be running.

Kim,
I have exactly the same question. I have already posed
this one in this forum and have yet to get a satisfactory
reply. My particular question is how do I tell the client
where to get its DHCP from which is similar to your how
do I tell the DHCP server to supply addresses to its own
domain members. Either way we need an answer - anybody?
Jon
>-----Original Message-----
>I have 2 domains on the same physical segment. Domain 1
>addresses 192.168.100.0/24 (NT 4 Server) and Domain 2
>192.168.200.0/24 (Windows 2003 Server). There is a
trust
>setup between the two domains using RRAS (Windows 2003)
>with 2 NICs and a static route. One NIC is
192.168.100.1
>other NIC is 192.168.200.1. My question is how can I
set
>DHCP on each domain to only supply addresses for it's
own
>domain. I want both DHCP servers to be running.
>.
>

Hi,

Just my 2 cents worth comment.
You may need to lock the IP on each MAC address of NIC.
This means you need to manually set it for the first time.
or when the new computer join the domain as well.

Krit Kanrat,
www.microthai.com

"Kim" <(E-Mail Removed)> wrote in message
news:4cbb01c3e444$093fa1a0$(E-Mail Removed)...
> I have 2 domains on the same physical segment. Domain 1
> addresses 192.168.100.0/24 (NT 4 Server) and Domain 2
> 192.168.200.0/24 (Windows 2003 Server). There is a trust
> setup between the two domains using RRAS (Windows 2003)
> with 2 NICs and a static route. One NIC is 192.168.100.1
> other NIC is 192.168.200.1. My question is how can I set
> DHCP on each domain to only supply addresses for it's own
> domain. I want both DHCP servers to be running.

Hi Jon, did you post with subject 'DHCP Rouge Servers' also?
I replied in that thread. I there gave just basic information
on how DHCP server - client work.

Anyway, from the below configuration you informed,
please note that, if both DHCP servers are on same
physical network segment, it is not possible to tell
cleints to use a particular DHCP server (unless
the clients support BOOTP protocol, where it
then can be configured, then the DHCP severs also
sould be configured to use BOOTP.)

Also please note that, DHCP has nothing to to with
domains. During the client booting process the client
send 'DHCP_DISCOVER' packet before it tries
to connect to the domain, and by the time the client
negotiate for domain controller, it has already obtained
IP address from a DHCP.

What you can do is.. Shut down the clients which
you want to get IP from NT4 DHCP, and on NT4
stop DHCP Server. Reboot all cleints which you want
to get IP from win 2003 DHCP. In absence of NT4
DHCP they will get IP address from win 2003 DHCP only.
Clients remeber their last IP address obtained, and next time
they try to get the same one, so next time they reboot they
will try first to obtain IP from win 2003 DHCP, even if
NT4 DHCP is running.

So repeat same as above, by shutting down all cleints which
you want to obtain IP from win 2003 DHCP and stop
DHCP server on win 2003. Keep NT4 DHCP running
and boot the clients which you want to obtain IP from NT
DHCP server.

After this done, then with both DHCP running, the repsective
cleints will try to get IP from respective DHCP and will go
to other DHCP only if the the respective does not respond
(like it is down etc.) Also if you take a cleint to some different
place, its IP will be toally different and then bring it back,
then it again may chose any of one DHCP. If you add a new
client machine, or reinstall OS on a client etc. it may go
to any one of DHCP again.

The best option will be make to domains and their repsective cleints
on different physical network segments. When they are on two
physical different segments, then their either should NOT be
a DHCP relay agent in the segements, or if they need to be their
they need to be confiured and enter respective DHCP servers
in their config.

Sharad

<(E-Mail Removed)> wrote in message
news:4e4a01c3e49f$cc2cd8d0$(E-Mail Removed)...
> Kim,
> I have exactly the same question. I have already posed
> this one in this forum and have yet to get a satisfactory
> reply. My particular question is how do I tell the client
> where to get its DHCP from which is similar to your how
> do I tell the DHCP server to supply addresses to its own
> domain members. Either way we need an answer - anybody?
> Jon
> >-----Original Message-----
> >I have 2 domains on the same physical segment. Domain 1
> >addresses 192.168.100.0/24 (NT 4 Server) and Domain 2
> >192.168.200.0/24 (Windows 2003 Server). There is a
> trust
> >setup between the two domains using RRAS (Windows 2003)
> >with 2 NICs and a static route. One NIC is
> 192.168.100.1
> >other NIC is 192.168.200.1. My question is how can I
> set
> >DHCP on each domain to only supply addresses for it's
> own
> >domain. I want both DHCP servers to be running.
> >.
> >

Further as Krit says, if you don't have a large number
of clients, you can manually configure each to first
obtain static IP in the repsective DHCP scope, reboot,
then change back to dyamic IP and reboot.

"sharad" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi Jon, did you post with subject 'DHCP Rouge Servers' also?
> I replied in that thread. I there gave just basic information
> on how DHCP server - client work.
>
> Anyway, from the below configuration you informed,
> please note that, if both DHCP servers are on same
> physical network segment, it is not possible to tell
> cleints to use a particular DHCP server (unless
> the clients support BOOTP protocol, where it
> then can be configured, then the DHCP severs also
> sould be configured to use BOOTP.)
>
> Also please note that, DHCP has nothing to to with
> domains. During the client booting process the client
> send 'DHCP_DISCOVER' packet before it tries
> to connect to the domain, and by the time the client
> negotiate for domain controller, it has already obtained
> IP address from a DHCP.
>
> What you can do is.. Shut down the clients which
> you want to get IP from NT4 DHCP, and on NT4
> stop DHCP Server. Reboot all cleints which you want
> to get IP from win 2003 DHCP. In absence of NT4
> DHCP they will get IP address from win 2003 DHCP only.
> Clients remeber their last IP address obtained, and next time
> they try to get the same one, so next time they reboot they
> will try first to obtain IP from win 2003 DHCP, even if
> NT4 DHCP is running.
>
> So repeat same as above, by shutting down all cleints which
> you want to obtain IP from win 2003 DHCP and stop
> DHCP server on win 2003. Keep NT4 DHCP running
> and boot the clients which you want to obtain IP from NT
> DHCP server.
>
> After this done, then with both DHCP running, the repsective
> cleints will try to get IP from respective DHCP and will go
> to other DHCP only if the the respective does not respond
> (like it is down etc.) Also if you take a cleint to some different
> place, its IP will be toally different and then bring it back,
> then it again may chose any of one DHCP. If you add a new
> client machine, or reinstall OS on a client etc. it may go
> to any one of DHCP again.
>
> The best option will be make to domains and their repsective cleints
> on different physical network segments. When they are on two
> physical different segments, then their either should NOT be
> a DHCP relay agent in the segements, or if they need to be their
> they need to be confiured and enter respective DHCP servers
> in their config.
>
> Sharad
>
> <(E-Mail Removed)> wrote in message
> news:4e4a01c3e49f$cc2cd8d0$(E-Mail Removed)...
> > Kim,
> > I have exactly the same question. I have already posed
> > this one in this forum and have yet to get a satisfactory
> > reply. My particular question is how do I tell the client
> > where to get its DHCP from which is similar to your how
> > do I tell the DHCP server to supply addresses to its own
> > domain members. Either way we need an answer - anybody?
> > Jon
> > >-----Original Message-----
> > >I have 2 domains on the same physical segment. Domain 1
> > >addresses 192.168.100.0/24 (NT 4 Server) and Domain 2
> > >192.168.200.0/24 (Windows 2003 Server). There is a
> > trust
> > >setup between the two domains using RRAS (Windows 2003)
> > >with 2 NICs and a static route. One NIC is
> > 192.168.100.1
> > >other NIC is 192.168.200.1. My question is how can I
> > set
> > >DHCP on each domain to only supply addresses for it's
> > own
> > >domain. I want both DHCP servers to be running.
> > >.
> > >
>
>

Sharad,
Yes it was me that posted the Rogue DHCP thread.
The use of DHCP is critical and so far we have been unable
to use it because we share a network infrastructure and
have no control over who runs these other DHCP
environments. We were hoping that the what with DHCP
authorisation in the AD, to prevent idiots firing up
additional forest/domain DHCP, so that clients were
unlikely to be given an incorrect address if this happens.
I was hoping that MS would have gone the extra mile and
put something on the client (which for us will be all XP
Pro) to assist. This could be something like the LMHOSTS
file to predefine domain controllers.
I would be interested to know how the BootP side of XP
could be leverage this - if it is possible.
Jon
>-----Original Message-----
>Further as Krit says, if you don't have a large number
>of clients, you can manually configure each to first
>obtain static IP in the repsective DHCP scope, reboot,
>then change back to dyamic IP and reboot.
>
>"sharad" <(E-Mail Removed)> wrote in message
>news:(E-Mail Removed)...
>> Hi Jon, did you post with subject 'DHCP Rouge Servers'
also?
>> I replied in that thread. I there gave just basic
information
>> on how DHCP server - client work.
>>
>> Anyway, from the below configuration you informed,
>> please note that, if both DHCP servers are on same
>> physical network segment, it is not possible to tell
>> cleints to use a particular DHCP server (unless
>> the clients support BOOTP protocol, where it
>> then can be configured, then the DHCP severs also
>> sould be configured to use BOOTP.)
>>
>> Also please note that, DHCP has nothing to to with
>> domains. During the client booting process the client
>> send 'DHCP_DISCOVER' packet before it tries
>> to connect to the domain, and by the time the client
>> negotiate for domain controller, it has already obtained
>> IP address from a DHCP.
>>
>> What you can do is.. Shut down the clients which
>> you want to get IP from NT4 DHCP, and on NT4
>> stop DHCP Server. Reboot all cleints which you want
>> to get IP from win 2003 DHCP. In absence of NT4
>> DHCP they will get IP address from win 2003 DHCP only.
>> Clients remeber their last IP address obtained, and
next time
>> they try to get the same one, so next time they reboot
they
>> will try first to obtain IP from win 2003 DHCP, even if
>> NT4 DHCP is running.
>>
>> So repeat same as above, by shutting down all cleints
which
>> you want to obtain IP from win 2003 DHCP and stop
>> DHCP server on win 2003. Keep NT4 DHCP running
>> and boot the clients which you want to obtain IP from NT
>> DHCP server.
>>
>> After this done, then with both DHCP running, the
repsective
>> cleints will try to get IP from respective DHCP and
will go
>> to other DHCP only if the the respective does not
respond
>> (like it is down etc.) Also if you take a cleint to
some different
>> place, its IP will be toally different and then bring
it back,
>> then it again may chose any of one DHCP. If you add a
new
>> client machine, or reinstall OS on a client etc. it may
go
>> to any one of DHCP again.
>>
>> The best option will be make to domains and their
repsective cleints
>> on different physical network segments. When they are
on two
>> physical different segments, then their either should
NOT be
>> a DHCP relay agent in the segements, or if they need to
be their
>> they need to be confiured and enter respective DHCP
servers
>> in their config.
>>
>> Sharad
>>
>> <(E-Mail Removed)> wrote in message
>> news:4e4a01c3e49f$cc2cd8d0$(E-Mail Removed)...
>> > Kim,
>> > I have exactly the same question. I have already posed
>> > this one in this forum and have yet to get a
satisfactory
>> > reply. My particular question is how do I tell the
client
>> > where to get its DHCP from which is similar to your
how
>> > do I tell the DHCP server to supply addresses to its
own
>> > domain members. Either way we need an answer -
anybody?
>> > Jon
>> > >-----Original Message-----
>> > >I have 2 domains on the same physical segment.
Domain 1
>> > >addresses 192.168.100.0/24 (NT 4 Server) and Domain 2
>> > >192.168.200.0/24 (Windows 2003 Server). There is a
>> > trust
>> > >setup between the two domains using RRAS (Windows
2003)
>> > >with 2 NICs and a static route. One NIC is
>> > 192.168.100.1
>> > >other NIC is 192.168.200.1. My question is how can I
>> > set
>> > >DHCP on each domain to only supply addresses for it's
>> > own
>> > >domain. I want both DHCP servers to be running.
>> > >.
>> > >
>>
>>
>
>
>.
>

Sharad,
Yes it was me that posted the Rogue DHCP thread.
The use of DHCP is critical and so far we have been unable
to use it because we share a network infrastructure and
have no control over who runs these other DHCP
environments. We were hoping that the what with DHCP
authorisation in the AD, to prevent idiots firing up
additional forest/domain DHCP, so that clients were
unlikely to be given an incorrect address if this happens.
I was hoping that MS would have gone the extra mile and
put something on the client (which for us will be all XP
Pro) to assist. This could be something like the LMHOSTS
file to predefine domain controllers.
I would be interested to know how the BootP side of XP
could be leverage this - if it is possible.
Jon
>-----Original Message-----
>Further as Krit says, if you don't have a large number
>of clients, you can manually configure each to first
>obtain static IP in the repsective DHCP scope, reboot,
>then change back to dyamic IP and reboot.
>
>"sharad" <(E-Mail Removed)> wrote in message
>news:(E-Mail Removed)...
>> Hi Jon, did you post with subject 'DHCP Rouge Servers'
also?
>> I replied in that thread. I there gave just basic
information
>> on how DHCP server - client work.
>>
>> Anyway, from the below configuration you informed,
>> please note that, if both DHCP servers are on same
>> physical network segment, it is not possible to tell
>> cleints to use a particular DHCP server (unless
>> the clients support BOOTP protocol, where it
>> then can be configured, then the DHCP severs also
>> sould be configured to use BOOTP.)
>>
>> Also please note that, DHCP has nothing to to with
>> domains. During the client booting process the client
>> send 'DHCP_DISCOVER' packet before it tries
>> to connect to the domain, and by the time the client
>> negotiate for domain controller, it has already obtained
>> IP address from a DHCP.
>>
>> What you can do is.. Shut down the clients which
>> you want to get IP from NT4 DHCP, and on NT4
>> stop DHCP Server. Reboot all cleints which you want
>> to get IP from win 2003 DHCP. In absence of NT4
>> DHCP they will get IP address from win 2003 DHCP only.
>> Clients remeber their last IP address obtained, and
next time
>> they try to get the same one, so next time they reboot
they
>> will try first to obtain IP from win 2003 DHCP, even if
>> NT4 DHCP is running.
>>
>> So repeat same as above, by shutting down all cleints
which
>> you want to obtain IP from win 2003 DHCP and stop
>> DHCP server on win 2003. Keep NT4 DHCP running
>> and boot the clients which you want to obtain IP from NT
>> DHCP server.
>>
>> After this done, then with both DHCP running, the
repsective
>> cleints will try to get IP from respective DHCP and
will go
>> to other DHCP only if the the respective does not
respond
>> (like it is down etc.) Also if you take a cleint to
some different
>> place, its IP will be toally different and then bring
it back,
>> then it again may chose any of one DHCP. If you add a
new
>> client machine, or reinstall OS on a client etc. it may
go
>> to any one of DHCP again.
>>
>> The best option will be make to domains and their
repsective cleints
>> on different physical network segments. When they are
on two
>> physical different segments, then their either should
NOT be
>> a DHCP relay agent in the segements, or if they need to
be their
>> they need to be confiured and enter respective DHCP
servers
>> in their config.
>>
>> Sharad
>>
>> <(E-Mail Removed)> wrote in message
>> news:4e4a01c3e49f$cc2cd8d0$(E-Mail Removed)...
>> > Kim,
>> > I have exactly the same question. I have already posed
>> > this one in this forum and have yet to get a
satisfactory
>> > reply. My particular question is how do I tell the
client
>> > where to get its DHCP from which is similar to your
how
>> > do I tell the DHCP server to supply addresses to its
own
>> > domain members. Either way we need an answer -
anybody?
>> > Jon
>> > >-----Original Message-----
>> > >I have 2 domains on the same physical segment.
Domain 1
>> > >addresses 192.168.100.0/24 (NT 4 Server) and Domain 2
>> > >192.168.200.0/24 (Windows 2003 Server). There is a
>> > trust
>> > >setup between the two domains using RRAS (Windows
2003)
>> > >with 2 NICs and a static route. One NIC is
>> > 192.168.100.1
>> > >other NIC is 192.168.200.1. My question is how can I
>> > set
>> > >DHCP on each domain to only supply addresses for it's
>> > own
>> > >domain. I want both DHCP servers to be running.
>> > >.
>> > >
>>
>>
>
>
>.
>

Hi Jon,

unfortunatelu win XP (or any MS winows OS for that matter) has only a
support for BOOTP protocol, and it
is not configurable. There are some third partu BOOTP protocol available for
MS Windows, which I tested, turn out be for the kind of soltution you seek,
as good as having a static IP for the clients.
Only linux red hat has such an configurable BOOTP.

With the new generation IPV6 protocol, MAY BE, MS will have option to go for
a pre-defined DHCP server. (only a hope.)

But more important is that, when you are on same physical network segement,
it doesn't matter really, from which DHCP
you get a dynamic IP, after all you are on the same physical subnet, and
should know how to handle different subnet IPs, or have a choice
to assing IP statically.

So still the best solution would be to have two different physical network
segmens, fot the two domains, if your requirekent
is that clinets joining diffrent domains must have IP is specifice
respective subnet.

If I come across any solution for what you require within same physical
network segment, I will post it.

Sharad


<(E-Mail Removed)> wrote in message
news:4f8801c3e4c0$16bdd820$(E-Mail Removed)...
> Sharad,
> Yes it was me that posted the Rogue DHCP thread.
> The use of DHCP is critical and so far we have been unable
> to use it because we share a network infrastructure and
> have no control over who runs these other DHCP
> environments. We were hoping that the what with DHCP
> authorisation in the AD, to prevent idiots firing up
> additional forest/domain DHCP, so that clients were
> unlikely to be given an incorrect address if this happens.
> I was hoping that MS would have gone the extra mile and
> put something on the client (which for us will be all XP
> Pro) to assist. This could be something like the LMHOSTS
> file to predefine domain controllers.
> I would be interested to know how the BootP side of XP
> could be leverage this - if it is possible.
> Jon
> >-----Original Message-----
> >Further as Krit says, if you don't have a large number
> >of clients, you can manually configure each to first
> >obtain static IP in the repsective DHCP scope, reboot,
> >then change back to dyamic IP and reboot.
> >
> >"sharad" <(E-Mail Removed)> wrote in message
> >news:(E-Mail Removed)...
> >> Hi Jon, did you post with subject 'DHCP Rouge Servers'
> also?
> >> I replied in that thread. I there gave just basic
> information
> >> on how DHCP server - client work.
> >>
> >> Anyway, from the below configuration you informed,
> >> please note that, if both DHCP servers are on same
> >> physical network segment, it is not possible to tell
> >> cleints to use a particular DHCP server (unless
> >> the clients support BOOTP protocol, where it
> >> then can be configured, then the DHCP severs also
> >> sould be configured to use BOOTP.)
> >>
> >> Also please note that, DHCP has nothing to to with
> >> domains. During the client booting process the client
> >> send 'DHCP_DISCOVER' packet before it tries
> >> to connect to the domain, and by the time the client
> >> negotiate for domain controller, it has already obtained
> >> IP address from a DHCP.
> >>
> >> What you can do is.. Shut down the clients which
> >> you want to get IP from NT4 DHCP, and on NT4
> >> stop DHCP Server. Reboot all cleints which you want
> >> to get IP from win 2003 DHCP. In absence of NT4
> >> DHCP they will get IP address from win 2003 DHCP only.
> >> Clients remeber their last IP address obtained, and
> next time
> >> they try to get the same one, so next time they reboot
> they
> >> will try first to obtain IP from win 2003 DHCP, even if
> >> NT4 DHCP is running.
> >>
> >> So repeat same as above, by shutting down all cleints
> which
> >> you want to obtain IP from win 2003 DHCP and stop
> >> DHCP server on win 2003. Keep NT4 DHCP running
> >> and boot the clients which you want to obtain IP from NT
> >> DHCP server.
> >>
> >> After this done, then with both DHCP running, the
> repsective
> >> cleints will try to get IP from respective DHCP and
> will go
> >> to other DHCP only if the the respective does not
> respond
> >> (like it is down etc.) Also if you take a cleint to
> some different
> >> place, its IP will be toally different and then bring
> it back,
> >> then it again may chose any of one DHCP. If you add a
> new
> >> client machine, or reinstall OS on a client etc. it may
> go
> >> to any one of DHCP again.
> >>
> >> The best option will be make to domains and their
> repsective cleints
> >> on different physical network segments. When they are
> on two
> >> physical different segments, then their either should
> NOT be
> >> a DHCP relay agent in the segements, or if they need to
> be their
> >> they need to be confiured and enter respective DHCP
> servers
> >> in their config.
> >>
> >> Sharad
> >>
> >> <(E-Mail Removed)> wrote in message
> >> news:4e4a01c3e49f$cc2cd8d0$(E-Mail Removed)...
> >> > Kim,
> >> > I have exactly the same question. I have already posed
> >> > this one in this forum and have yet to get a
> satisfactory
> >> > reply. My particular question is how do I tell the
> client
> >> > where to get its DHCP from which is similar to your
> how
> >> > do I tell the DHCP server to supply addresses to its
> own
> >> > domain members. Either way we need an answer -
> anybody?
> >> > Jon
> >> > >-----Original Message-----
> >> > >I have 2 domains on the same physical segment.
> Domain 1
> >> > >addresses 192.168.100.0/24 (NT 4 Server) and Domain 2
> >> > >192.168.200.0/24 (Windows 2003 Server). There is a
> >> > trust
> >> > >setup between the two domains using RRAS (Windows
> 2003)
> >> > >with 2 NICs and a static route. One NIC is
> >> > 192.168.100.1
> >> > >other NIC is 192.168.200.1. My question is how can I
> >> > set
> >> > >DHCP on each domain to only supply addresses for it's
> >> > own
> >> > >domain. I want both DHCP servers to be running.
> >> > >.
> >> > >
> >>
> >>
> >
> >
> >.
> >