Re: DNS and Secondary DC
- From: "Craig P." <thehelpdesk@(nospam)chdnet.com>
- Date: Fri, 30 Nov 2007 18:14:17 -0600
I usually build my remote office servers, additional DC's not in the offices
but in my lab/shop and join them to the domain via a vpn connection to the
main SBS office. A simple PPTP vpn connection on the server that I am
setting up connecting to the main office available for "All Users" is all
that is needed.
After joining the server to the domain as a member server, reboot, logon
with domain credentials, and then create a VPN tunnel to the main office and
to the new server. The rest is just allowing plenty of time for
replciation if you make it a DC and GC. Upon deployment of the server to
the final location all I have to do is change the external IP address's
where applicable.
So in your case of using a pre-existing connection or network, as long as
you can get to your SBS server from there you should not have any problem.
You may have somewhat of a delay login in with domain credentials but I
don't think anything would be an issue.
Craig P.
"Maxxsir" <Maxxsir@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:44E3769A-F19F-4223-836C-391364318932@xxxxxxxxxxxxxxxx
I suppose this would be good for testing but I don't have a server here to
test with. I do have a decent desktop at the house I could use I suppose.
I
will build this over the weekend just to get an idea of what the end
result
should look like. I do have an extra VPN router I can setup at my home and
connect to my network at the office so my home project should reflect the
end
result of what things should look like when I am done in CA.
The issue still remains that I will be wiping out the SBS server in
California and starting over from scratch. I can't do that until I get out
there and I have to start and finish in a weekend.
Can a DC server be built and joined to my SBS 2003 AD network in Michigan
through a dedicated existing VPN connection?
--
Maxxsir
"Merv Porter [SBS-MVP]" wrote:
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
- Next by Date: Re: Sbs 2003 installing fax setup
- Next by thread: Re: DNS and Secondary DC
- Index(es):
Relevant Pages
|
Loading
