Re: PC pointing to DC in other locations
- From: "Jorge Silva" <jorgesilva_pt@xxxxxxxxxxx>
- Date: Wed, 26 Jul 2006 17:23:49 +0100
what OS are you using in your client machines?
how did you tested the machines to see whitch DC were they using.
--
I hope that the information above helps you
Good Luck
Jorge Silva
MCSA
Systems Administrator
"Razvan Despa" <RazvanDespa@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0F1B31FD-68AC-4730-851A-5FA05D8AB9C1@xxxxxxxxxxxxxxxx
Hi all,
As already said, I have one GC on each site. On two big sites we have 2
DC,
but only one is GC.
I have a site for each location where is a DC. On the major site A (2 DCs,
1
GC) I added all subnets that corespond to locations where I do not have a
DC.
So all remote location PCs must connect to the major site A (2 DCs, 1 GC).
From time to time it happends that PCs (from all sites - where is a DC and
also where is not a DC) are requesting authentification on a particular
site
B, but not all PCs. This is happening randomize.
The DC are on the same subnets as the PC in each location.
Here i am lost. I cannot understand why this is happening.
--
Razvan Despa
IT assistent
Romania
"Jorge Silva" wrote:
Hi
As frederiik said 1st you need to have DC at the correct sites with the
correct subnets assigned,
Active Diretory Uses Sites to:
- Optimize replication for speed and bandwidth consumption between
domain
controllers.
- Locate the closest domain controller for client logon, services, and
directory searches.
- Direct a Distributed File System (DFS) client to the server that is
hosting the requested data within the site.
- Replicate the system volume (SYSVOL), a collection of folders in the
file
system that exists on each domain controller in a domain and is required
for
implementation of Group Policy.
- To SpeedUp logon process, make sure that you have at least 1 GC per
site,
or if you have a Windows 2003 forest use UGMC.
The DNS configuration is also important:
-Make sure that you configure the Preferred DNS server in TCP/IP
properties
on each Domain Controller to use itself as Primary DNS Server (If DC IP
Address is 10.0.0.1 then Dns should be 10.0.0.1).When adding an
additional
DC to an existent Domain, do not configure the domain controller to
utilize
its own DNS service for name resolution until you have verified that both
inbound and outbound Active Directory replication is functioning and up
to
date. During the DCPromo process, you must configure additional domain
controllers to point to another domain controller that is running DNS in
their domain and site, and that hosts the namespace of the domain in
which
the new domain controller is installed. More Info here:
Best practices for DNS client settings in Windows 2000 Server and in
Windows
Server 2003
http://support.microsoft.com/kb/825036/en-us
- Make sure that every DNS server can resolve all existent domains in the
forest. (You can use Forwarding, Stub Zones or Secondary Zones).
DNS Conditional Forwarding in Windows Server 2003
http://www.windowsnetworking.com/articles_tutorials/DNS_Conditional_Forwarding_in_Windows_Server_2003.html
DNS Stub Zones in Windows Server 2003
http://www.windowsnetworking.com/articles_tutorials/DNS_Stub_Zones.html
How To Create a Child Domain in Active Directory and Delegate the DNS
Namespace to the Child Domain
http://support.microsoft.com/kb/255248/
- Make sure that all clients only use their local(s) Dns Server. Note
That
DNS client does not utilize each of the DNS servers listed in TCP/IP
configuration for each query. By default, on startup the DNS client will
attempt to utilize the server in the Preferred DNS server entry. If this
server fails to respond for any reason, the DNS client will switch to the
server listed in the alternate DNS server entry. The DNS client will
continue to use this alternate DNS server until: fails to respond to a
DNS
query, or The ServerPriorityTimeLimit value is reached (15 minutes by
default). For more information:
The DNS Client Service Does Not Revert to Using the First Server in the
List
in Windows XP
http://support.microsoft.com/kb/320760/en-us
The DNS Client Service Does Not Revert to Using the First Server in the
List
http://support.microsoft.com/kb/286834/en-us
How Domain Controllers Are Located in Windows
http://support.microsoft.com/kb/247811/
How to configure TCP/IP to use DNS in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;305553
--
I hope that the information above helps you
Good Luck
Jorge Silva
MCSA
Systems Administrator
"Razvan Despa" <RazvanDespa@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:991C031D-EDEF-4454-AFA7-AC84DACA3D59@xxxxxxxxxxxxxxxx
Hi all,
We have a child domain with 15 DC spreaded in several locations. From
time
to time the PC are authentificating on DCs in other locations, even if
in
the
same location I have another 2 DC. All actions after the
authentificationa
are taking a lot of time when the user is trying to access the file
server
(queryng again to the DC for authentification).
Do you know a way to force the PCs to search in list of DC before
authentificate?
It is a way to setup in DHCP the addresses of the local DC?
--
Razvan Despa
IT assistent
Romania
.
- Follow-Ups:
- Re: PC pointing to DC in other locations
- From: Razvan Despa
- Re: PC pointing to DC in other locations
- From: Razvan Despa
- Re: PC pointing to DC in other locations
- References:
- Re: PC pointing to DC in other locations
- From: Jorge Silva
- Re: PC pointing to DC in other locations
- From: Razvan Despa
- Re: PC pointing to DC in other locations
- Prev by Date: Re: Domain Controller Feature R2?
- Next by Date: Re: Replication errors - NTDS KCC
- Previous by thread: Re: PC pointing to DC in other locations
- Next by thread: Re: PC pointing to DC in other locations
- Index(es):
Relevant Pages
|
Loading
