Re: DNS and Secondary DC
- From: "Merv Porter [SBS-MVP]" <mwport@xxxxxxxxxxxxxxxxxxx>
- Date: Fri, 30 Nov 2007 12:33:45 -0500
I wonder if this would help...
An Alternative Approach to Building an SBS Branch Office
http://www.windowsitpro.com/articles/print.cfm?articleid=49788
--
Merv Porter [SBS-MVP]
============================
"Maxxsir" <Maxxsir@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:20184C36-1BCF-4216-A945-276CCACB05CC@xxxxxxxxxxxxxxxx
I am a bit confused on DNS and a secondary DC at a branch office. We have
two
SBS 2003 standard servers. One is at HQ and another is at a branch office.
The one at the branch office is just for file sharing.
I was authorized to purchase a 2003 Standard license and install this on
the
branch office server and do away with the redundant SBS OS. Both sites are
connected via a 24/7 VPN tunnel each having their own subnet.
Unfortunately I have to go to the remote site to install 2003 server on
site. This means I have no way to pre-configure the server here at HQ. My
subnets are configured with the following IP addresses.
Michigan Subnet 192.168.1.0
AT&T - T1
VPN to California
California Subnet 192.168.2.0
AT&T - T1
VPN to Michigan
What are the challenges in adding a 2003 server into AD over a VPN and
where
does DNS fit into this if all branch office users will be browsing the
Internet from the branch office internet connection and not going through
HQ?
Once I have 2003 installed will the server be able to see AD on my HQ
subnet
when I try to add it into the domain or is there something else I need to
do?
--
Maxxsir
.
- Follow-Ups:
- Re: DNS and Secondary DC
- From: Maxxsir
- Re: DNS and Secondary DC
- Prev by Date: Re: Remote Access stopped working
- Next by Date: Re: DNS and Secondary DC
- Previous by thread: Re: Windows Deployment Services IMage creation
- Next by thread: Re: DNS and Secondary DC
- Index(es):
Relevant Pages
|