Office A: 1 Server 2003 box running AD/DNS and it's my DC on subnet
192.168.1.x
Office B: Just a workgroup which is on subnet 192.168.2.x and gets
it's DHCP from the cisco router which connects to Office A through a
point to point connection.


How do I set up Office B to replicate with Office A. I have a copy of
Server 2000 which I will install on a machine that will be located in
Office B. Both Offices need to communicate fully and be able to
resolve computer names, etc...

Any insight would be appreciated.
Mike

On Mar 24, 12:00 pm, "mcatgt" <mike.catalf...@gmail.com> wrote:
> Office A: 1 Server 2003 box running AD/DNS and it's my DC on subnet
> 192.168.1.x
> Office B: Just a workgroup which is on subnet 192.168.2.x and gets
> it's DHCP from the cisco router which connects to Office A through a
> point to point connection.
>
> How do I set up Office B to replicate with Office A. I have a copy of
> Server 2000 which I will install on a machine that will be located in
> Office B. Both Offices need to communicate fully and be able to
> resolve computer names, etc...
>
> Any insight would be appreciated.
> Mike

FYI: Office B: I would like them to join the Domain in Office A. I
would like all computer to be on the same Domain. Should I still
create a child domain for Office B?

"mcatgt" <mike.catalfamo@gmail.com> wrote in message
news:1174752951.494079.291070@e65g2000hsc.googlegr oups.com...
> On Mar 24, 12:00 pm, "mcatgt" <mike.catalf...@gmail.com> wrote:
>> Office A: 1 Server 2003 box running AD/DNS and it's my DC on subnet
>> 192.168.1.x

>> Office B: Just a workgroup which is on subnet 192.168.2.x and gets
>> it's DHCP from the cisco router which connects to Office A through a
>> point to point connection.


>> How do I set up Office B to replicate with Office A. I have a copy of
>> Server 2000 which I will install on a machine that will be located in
>> Office B.

Install that Win2000+ and DCPromo the server to new DC in the same
domain with OfficeA.

You will need to (initially) setup that server to use the DNS which can
resolve the domain zone info (e.g., on Office-A-DC-DNS.)

>> Both Offices need to communicate fully and be able to
>> resolve computer names, etc...

You will likely want to setup a VPN (IPSec or L2TP) if the OfficeA-B
connection traverses (semi-)Public networks.

>> Any insight would be appreciated.
>> Mike
>
> FYI: Office B: I would like them to join the Domain in Office A. I
> would like all computer to be on the same Domain. Should I still
> create a child domain for Office B?

No, since a child domain would be a NEW domain and would not
replicate the OfficeA domain info.

On Mar 24, 5:03 pm, "Herb Martin" <n...@learnquick.com> wrote:
> "mcatgt" <mike.catalf...@gmail.com> wrote in message
>
> news:1174752951.494079.291070@e65g2000hsc.googlegr oups.com...
>
> > On Mar 24, 12:00 pm, "mcatgt" <mike.catalf...@gmail.com> wrote:
> >> Office A: 1 Server 2003 box running AD/DNS and it's my DC on subnet
> >> 192.168.1.x
> >> Office B: Just a workgroup which is on subnet 192.168.2.x and gets
> >> it's DHCP from the cisco router which connects to Office A through a
> >> point to point connection.
> >> How do I set up Office B to replicate with Office A. I have a copy of
> >> Server 2000 which I will install on a machine that will be located in
> >> Office B.
>
> Install that Win2000+ and DCPromo the server to new DC in the same
> domain with OfficeA.
>
> You will need to (initially) setup that server to use the DNS which can
> resolve the domain zone info (e.g., on Office-A-DC-DNS.)
>
> >> Both Offices need to communicate fully and be able to
> >> resolve computer names, etc...
>
> You will likely want to setup a VPN (IPSec or L2TP) if the OfficeA-B
> connection traverses (semi-)Public networks.
>
> >> Any insight would be appreciated.
> >> Mike
>
> > FYI: Office B: I would like them to join the Domain in Office A. I
> > would like all computer to be on the same Domain. Should I still
> > create a child domain for Office B?
>
> No, since a child domain would be a NEW domain and would not
> replicate the OfficeA domain info.

OK. Thank you for that info.

As for a VPN, I'm not sure I need to do that because Office B is
directly connected via a Point to Point T1 and the connection is
always on... Office B gets to the internet through Office A (main
office with DC/DNS/AD). Let me know

"mcatgt" <mike.catalfamo@gmail.com> wrote in message
news:1174840817.515894.69710@o5g2000hsb.googlegrou ps.com...
>> No, since a child domain would be a NEW domain and would not
>> replicate the OfficeA domain info.
>
> OK. Thank you for that info.
>
> As for a VPN, I'm not sure I need to do that because Office B is
> directly connected via a Point to Point T1 and the connection is
> always on... Office B gets to the internet through Office A (main
> office with DC/DNS/AD). Let me know

Cool, then you can treat this just like a LAN from the point of view
of (no) VPN and (no special) firewall filters.

You probably should make OfficeB a separate SITE in AD Sites and
Services.

Do this before you create the new DC -- it's easier.


Create a site for each location
(Optionally rename the Default-First-Site-Name to HQ or some
meaningful name but I will refer to it as the Default site here)
Create subnet(s) for all the IP subnets at each location and use these
to define each site
Create a SiteLINK that represents each physical WAN from
location to HQ or between locations -- I am assuming here that
these are only HQ<->BranchX but that is not a restriction if you
have additional physical lines...
Put the HQ-Default Site and each BranchX in the apppropriate
SiteLINK
Remove the BranchX site from the Default-IP-SiteLink

DCPromo the new DC and it should put itself in the correct site.

Check this in Sites and Services -- move it and correct the site definition
(probably subnet) that caused the mistake if it is not there.

Check replication with "DCDiag /c" and search for WARN and FAIL
messages.

After you get it all replicating you (probably) will want to make the second
DC an "AD Integrated DNS" server and set the local (that site) machines
to use it as the preferred DNS server.

Have the local DNS forward to the main site DNS server for Internet access,
or to your Firewall/ISP for Internet access.

--
Herb Martin, MCSE, MVP
http://www.LearnQuick.Com
(phone on web site)