|
Aric, Thank you for the response.
Yes all 9 sites are configured correctly with the correct subnets in Active
Directory. This network topology has not changed in years and these are
physically separate sites. The clients in question definitely are in the
correct subnet associated with our site because I have check the registry entry
for site association and it is correct, yet these machines will contact a
remote site server for directory services. DNS looks correct with respect to
what servers are registering in what sites. Workstation access of remote DCs
is both during the joining of the domain as well as afterwards. We believe the
renaming error as I have proved it out relates to the “old” system
contacting a remote domain controller for the name change and the new system
contacting a local domain controller for its name, since the local domain
controller does not have the “old” system name change it errors
out. I am going to sniff more
traffic and provide some more information here. Jeremy From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bernard, Aric Under normal (what ever that means)
circumstances 2 GCs should certainly be able to handle 500 users. Have you defined subnets for each of your
9 sites? Are you certain that the clients in
question belong to one of the defined subnets? Are your DCs registering all appropriate
site coverage records in DNS? Is this usage of remote DCs occurring
typically on the workstations first access during/after joining the domain or
does it continue after subsequent reboots? Introducing Windows Server 2003 schema
extensions should not cause this problem. As for the rename error – this could
certainly be the result of the system “believing” that its name is
a duplicate in the organization due to replication latency based on your site
topology. This of course could be exacerbated by the fact that local
systems (the new machines) might be accessing DCs in remote sites. Aric From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Burkes, Jeremy [Contractor] Everyone,
We have an empty root domain and a child domain with approximately 9 or so
sites in the forest. The root domain has 2 DCs (1 GC) and the child
domain has 3 DCs (1GC) both of which are located in our main site. At our
main site where I am located we have approximately 500 users. The best
scenario I can give you is we do PC rollouts where we take a large number of
PCs 30-50 at a time and rename them with an old extension in the host name then
we bring a new machine onto the network with the same name. Sometimes we
get an error saying the computer account already exists in the organization
when we try to name the new machine with the same name, but the issue is
inconsistent. I did some traffic sniffing with a PC and found that
approximately 50% of the time machines in our site are contacting servers in
other site for directory service information instead of our site DCs.
Even machines that have been on the network are not using local site DCs for
information all the time but using other site DCs instead. I am wondering
what could be causing this. This configuration has been static for
sometime nothing new has been introduced except for Windows 2003 schema (could
this be the cause?). I think it is because we do not have enough GCs in
our site (2), but my boss disagrees. What does everyone think? Jeremy ------------------------------------------------------------------- |
- RE: [ActiveDir] GC availability issue? Burkes, Jeremy [Contractor]
- RE: [ActiveDir] GC availability issue? Burkes, Jeremy [Contractor]
- RE: [ActiveDir] GC availability issue? Burkes, Jeremy [Contractor]
- RE: [ActiveDir] GC availability issue? Sakari Kouti
