Re: DNS and Secondary DC

Ok, I configured a VPN with another router from my home office to corporate.
Below is what my network now looks like.

California Subnet 192.168.0.0
Corporate Office subnet 192.168.1.0
Chicago Subnet 192.168.2.0
New
Home Office Subnet 192.168.3.1

I have a Standard Windows 2003 Server ready to go. It has an IP address but
I am unsure how to proceed. I know SBS is picky on how things are done. I can
ping my SBS server through my VPN tunnel on my subnet here at home. I
assigned the DNS on this server to look at my SBS server. Was this correct
and if so what should my next step be? Do I need to open ports on my routers
for AD?

--
Maxxsir


"Craig P." wrote:

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






.

Relevant Pages

  • Re: Some Questions
    ... you may need to follow the steps below to configure VPN access ... And make sure you have typed the public FQDN of the SBS ... server on the Web Server Certificate page. ... log in and download Connection Manager. ...
    (microsoft.public.windows.server.sbs)
  • RE: VPN Connection Problems
    ... Note that we are able to successfully VPN into the office. ... to browse the network, RDP to the server or even ping the server. ... > This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • Re: 2 NIC SBS2003R2 LAN/WAN Firewall Router Connection Failure
    ... I have to admit to a preference for VMWare Server which can only be ... I've asked the other SBS MVP's to comment on the current status of SBS ... I connected directly to the router and changed its LAN side subnet ...
    (microsoft.public.windows.server.sbs)
  • RE: Enabling VPN Remote Access using SBS 2003 standard with ISA 20
    ... I am glad to hear the VPN issue has been resolved! ... on the SBS Server. ... Enabling VPN Remote Access using SBS 2003 standard with ISA ...
    (microsoft.public.windows.server.sbs)
  • RE: SBS 2003 and WAN connections useing Cisco Routers
    ... Thank you for posting in SBS newsgroup. ... do you mean you have created VPN using router to router or router ... server on the Web Server Certificate page. ... 0x2F if you are looking in Network Monitor). ...
    (microsoft.public.windows.server.sbs)