Re: Join 2 remote offices
- From: Bernard Si-Tech <BernardSiTech@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 9 Mar 2008 04:22:00 -0700
Hi Philip
Thanks for the help.
I have most under controll, we have decided opn a DC plan and it will be
implemented after we complete these tests, currently I am just testing and
these settings will be deleted completely (via a format & re-install).
I have the DNS settings in as you suggested and find I am able to view the
complete network and it shows the servers at both ends of the VPN tunnel from
the remote Server, however it only shows the local server at the local site.
seems I am missing something here.
I have entered the DNS zone of each site in the opposite site server Ip
address table.
I can remote access & Remote control over the VPN link.
I am still getting an error message when I try to make the remote server
join the domain, I am trying this from the change computer name section where
I set it is part of a domain and I type in the domain to be joined.
I get the error message that the domain is not available, any Ideas what I
could be missing.
Regards
Bernard
"Phillip Windell" wrote:
"Bernard Si-Tech" <BernardSiTech@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message.
news:2B86AE10-C340-4739-B712-CDB131426652@xxxxxxxxxxxxxxxx
My questio is how tom make the connection between the offices through the
tunnel between the servers.
Do I need to create the DNS first. and what do I need to set in there for
the subnetworks.
or do I do another way first.
I am going to assume the Tunnel is fine and the Routing Scheme related to it
is fine.
When you first start you will only have one or two DCs at the primary
location.
On the Server at the secondary location you need to enter the DC from the
main location into its DNS Settings in the TCP/IP Config. Do the same for
WINS if there is one. There should be *No* other DNS IP# entered into it.
Join it to the Domain. Use FQDNs,..do not use Netbios Names.
Run DCPromo and specify that it is to be a Domain in an existing Forest. Do
your own research here,...there is more than one model to choose from,...do
not do it wrong the first time. Do not simply take my word for it,...I do
not know all the details of your situation. Research it,...do it right the
first time.
When finished with the new DC change the DNS in the TCP/IP Specs to point to
itself.
Research Active Directory Sites. The AD Sites is a *requirement* for Forest
Replication to work properly over a slow WAN Link. Each location separated
by a WAN Link must be in its own AD Site and must be a different subnet from
other sites.
--
Phillip Windell
www.wandtv.com
The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/ISA2004_AccessRules.html
Troubleshooting Client Authentication on Access Rules in ISA Server 2004
http://download.microsoft.com/download/9/1/8/918ed2d3-71d0-40ed-8e6d-fd6eeb6cfa07/ts_rules.doc
Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.mspx
Microsoft ISA Server Partners: Partner Hardware Solutions
http://www.microsoft.com/forefront/edgesecurity/partners/hardwarepartners.mspx
-----------------------------------------------------
- Follow-Ups:
- Re: Join 2 remote offices
- From: Phillip Windell
- Re: Join 2 remote offices
- References:
- Re: Join 2 remote offices
- From: Bill Grant
- Re: Join 2 remote offices
- From: Bernard Si-Tech
- Re: Join 2 remote offices
- From: Phillip Windell
- Re: Join 2 remote offices
- From: Bernard Si-Tech
- Re: Join 2 remote offices
- From: Phillip Windell
- Re: Join 2 remote offices
- Prev by Date: Re: Problem with workgroup.
- Next by Date: Difficulties getting Windows Server 2003 DC to connect and synch to an Internet time source.
- Previous by thread: Re: Join 2 remote offices
- Next by thread: Re: Join 2 remote offices
- Index(es):
Relevant Pages
|