Re: Add a Remote Office to our Corporate Windows 2003 Domain Netwo
- From: "Jorge Silva" <jorgesilva_pt@xxxxxxxxxxx>
- Date: Thu, 18 Oct 2007 09:51:25 +0100
see inline
thanks for the reply. Ok, before i confuse me do i really need to addI only suggested WINS because you'll have different subnets and you said
WINS?
that they should be able to see through Network Neighborhood all computers,
etc...
My thought process on this setup was to create a DC for this remote site
with DNS and DHCP. I want the benefit to have the local users to have
authentication as you mentioned.
Great.
I just dont know where to start. I have configured my new 2003 server so
far
as a member server.
Assuming that the DC is already on the remote office:
*On the existing DC:
- Make sure that everything is setup Ok and no errors are shown in event
viewer and using dcdiag and netdiag from support tools.
- In the existing DC go to Active Directory Sites and Services and create a
new site that will represent the Remote Office, then create and assign the
subnet for that remote office to that new site (also make sure that the
subnet for the main office is assigned to the Main office site), if you
pre-configure the Site for your Domain, when you add the Additional DC to
that domain, the DC will be placed on the site where its subnet corresponds.
*On the new DC to be added:
- Install DNS service
- Make sure that the DC points to the existing DNS server on preferred DNS
NIC properties.
- Run DCPROMO on the DC to be added as additional DC, and choose the option
additional dc in an existing domain.
- Wait for replication or force it using repadmin or Active directory sites
and services.
- After everything replicated between both servers, Point the preferred DNS
NIC to DC/DNS itself and add the other one as secondary DNS server in the
NIC, do the same to the other DC/DNS.
- Configure the DC as Global Catalog (you do this under Active Directory
Sites and Services->Site->Server->NTDS Settings, go to the properties of
this object and select the option for GC).
- Last step is to configure WINS in both sites (if you want to have a WINS
in each site), configure each WINS replication partners, then install and
authorize the DHCP server and configure it.
Does this helps you?
--
===================================
I hope that the information above helps you.
Have a Nice day.
Jorge Silva
MCSE, MVP Directory Services
===================================
"John" <John@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:39916FEE-D599-4944-80A3-0F518DA00C35@xxxxxxxxxxxxxxxx
Jorge,
thanks for the reply. Ok, before i confuse me do i really need to add
WINS?
My thought process on this setup was to create a DC for this remote site
with DNS and DHCP. I want the benefit to have the local users to have
authentication as you mentioned.
I just dont know where to start. I have configured my new 2003 server so
far
as a member server.
That's all i have done so far besides to alot of researching on microsoft
and google.
The corporate network is on 192.168.150.x this remote site will be
192.168.170.x
Any suggestions I will take.
"Jorge Silva" wrote:
Hi
Not much to do.
Assign the remote office site subnet to the correct site, since you're
using
different subnets, create a WINS server and point all clients to that
WINS
server, if you plan to have more than one WINS server (1 in the main
office
and the other in the branch site) make sure that you configure both as
replication partners, you also say that you'll have a DNS at the branch
office, but this DNS server isn't a DC correct?
Why not making a DC at the remote branch office? That way the users would
be
authenticated to that DC as well for DNS registrations. If you configure
a
DNS (no DC) in the branch office you'll need to have a secondary zone or
Conditional forwarding or forwarding, either one of these will force the
client registrattion at the DNS in the main office, if you could have a
DC/DNS at the remote office you could benefit with local registration,
authentication, etc...
--
===================================
I hope that the information above helps you.
Have a Nice day.
Jorge Silva
MCSE, MVP Directory Services
===================================
"John" <John@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B9B71B0A-9B66-4206-980C-17B21361F2C1@xxxxxxxxxxxxxxxx
I have a Active Directory with one Domain on two 2003 domain controllers
running at our main office. I need to add a remote office with 1 file
server
for 20 users/workstations. What is the best way to set this up?
I want to set this up so that the users log on with there windows AD
account
from our corporate domain and getting a dhcp address, dns settings
locally. I
would assume that's the best way in order to minimize wan traffic.
maybe
i'm
way off and there's a better way.
They will be using the server for file and print services. The wan link
is
a
managed mpls circuit T1. They should be able to see through Network
Neighborhood the corporate network and be able to map to servers if
they
have
permissions.
Thanks for your help .
.
- Follow-Ups:
- References:
- Prev by Date: Re: Turning off pre-authentication for a user in 2003 AD?
- Next by Date: Re: Slow Logon procedure
- Previous by thread: Re: Add a Remote Office to our Corporate Windows 2003 Domain Netwo
- Next by thread: Re: Add a Remote Office to our Corporate Windows 2003 Domain Netwo
- Index(es):
Relevant Pages
|
Loading
