Sites and Services
- From: "MT" <MT@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 1 Jul 2005 06:35:08 -0700
We just recently upgraded our NT domain to 2K3 AD. We have one corp site with
around 40 branches. The in place upgrade went great, however when deploying
DC's to other sites I am having an issue with Headquarters clients
authentication to a Branch.
We are using a mixed Bind windows DNS environment where our AD name is the
same as our existing Bind DNS name. The appropriate zones are handed off to
our windows DNS server. Our Windows DNS servers then transfer the zones to
the BIND dns servers. All clients/server use our BIND servers located at
headquartes for DNS.
Each DC is a GC and I have configured sites and services with the
appropriate server for each subnet.
Example Branch subnet 135.74.65.0/24 assigned to Branch site Houston which
includes the Houston DC.
Branch subnet 135.74.41.0/24 assigned to Branch site Tulsa which includes
Tulsa DC.
I have not defined any subnets for the Headquarters yet. (135.74.48.0 - 55.0)
I would like to keep Headquarters pc's from authenticating at branches...and
vice versa. That is the whole reason to have GC's at each site.
My thoughts are...It might have something to do with DNS. Setup each DC at
each branch as a DNS server and point all client at each branch to them for
resolution. Setup forwaders to the BIND servers.
Any thoughts?
.
- Follow-Ups:
- RE: Sites and Services
- From: sambrake
- RE: Sites and Services
- Prev by Date: Re: VBS Logon Script not always executing upon logon on TS
- Next by Date: Re: file and AD replication question(s)
- Previous by thread: not enough computer accounts
- Next by thread: RE: Sites and Services
- Index(es):
Relevant Pages
|