2.168.101.x one.
> >
> >
> >
> > It IS that simple.
> >
> >
> >
> >
> >
> > From: James Kerr [mailto:cluster...@gmail.com]
> > Sent: Friday, 9 March 2012 12:47 AM
> > To: NT System Admin Issues
> > Subject: Re: A Little H
ary
routing in place so just go ahead and activate that DHCP scope and
deactivate the old 192.168.101.x one.
>
>
>
> It IS that simple.
>
>
>
>
>
> From: James Kerr [mailto:cluster...@gmail.com]
> Sent: Friday, 9 March 2012 12:47 AM
> To: NT System Admin Iss
o: NT System Admin Issues
Subject: Re: A Little Help Needed
I have a DC from domain 1 sitting on domain 2's LAN. I can activate DHCP on
that server with the same 192.168.101.x scope, no problem. It is also
running DNS. The DC from domain 1 is happy up there on domain 2's LAN and is
repli
I have a DC from domain 1 sitting on domain 2's LAN. I can activate DHCP on
that server with the same 192.168.101.x scope, no problem. It is also
running DNS. The DC from domain 1 is happy up there on domain 2's LAN and
is replicating with the other domain 1 DCs. It seems too simple though. I
think
You will need to change DNS settings on those computers to point to a DNS
servers in Domain 1 either static or through the DHCP scope. Also setup a
new site in AD and define the subnet.
On Thu, Mar 8, 2012 at 9:17 AM, Christopher Bodnar <
christopher_bod...@glic.com> wrote:
> Not sure you reall
Not sure you really need to do anything, at least initially. So right now
the domain 2 clients (192.168.101.x) are receiving DHCP addresses from
their local DC or some DHCP server on domain 2 that has a scope setup for
the 192.168.101.x address range, correct? When you flip these clients over
t
I think this is more of a network routing question. AFAIK, AD doesn't care
if machines are on separate networks, as long as the DC's can communicate,
and the network is correctly routed.
I'd probably standup a DC for domain 1 at site 2, to minimize traffic
across the VPN.
On Thu, Mar 8, 2012 at
if we are talking about Windows domains (when you refer to domain 1 and 2), as
long as you can reach the Domain controller from 192.168.101.x network you
should be fine.
For that you probably need to add a route to your router to reach from
192.168.101.x to 192.168.100.x network.
Regards,
Mig