RE: New DC not visible in Default-First-Site

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



Looking at your connection objects it looks correct.

Lets have a look why....

Firstly, we're talking intra-site replication here. The KCC will generate a
ring topology by default. Not until you reach 7 or more DCs will the KCC
generate extra shortcut connection objects to reduce latency. Hence, your
topology will be a ring.

Secondly, lets lay out the topology according to the automatically generated
connection objects:


DC1 <=====> DC3
| |
| |
| |
DC4 <=====> DC2

Hence, the default replication topology is correct. It's a ring topology -
you haven't got more than 7 DCs so there will be no shortcuts. When you
added DC2 - it just reconfigured the topology and deleted the connection
object.

Thus, I would delete any manual connection objects you created since there
are no need for them. As a quick check...in Active Directory Sites and
Services - right-click NTDS settings and select Check Replication. Now check
the Directory Services log and there should be no errors. If so, you are
OK...

Hope this helps.




"Edita" wrote:

No errors in the log …
The picture from sites and services is…
Under default-first-site\servers I have connections for all four DC’s

DC1 under NTDS settings has DC3 and DC4 (this is the new one). As for DC2
which was here few days ago, it just disappeared (the server is up and
running)
DC2 under NTDS settings has DC3 and DC4 (DC1 suddenly missing but is added
now manually )
DC3 under NTDS settings has DC1 and DC2
DC4 under NTDS settings has DC1 and DC2

I checked the replication topology using replmon and DC4 is not replicating
with DC3. I also run searh for replication failure In the domain and no
errors were found. I can add the new DC and the one that’s missing manually
but I am concerned that maybe I have some hidden errors which caused DC2 and
DC1 to stop replicating. Also I don’t know why DC4 didn’t connect with DC3
and vice versa… The plan in the company is to transfer FSMO roles from DC1 to
DC4 and to demote DC1 so I need a clear situation


"Steve B" wrote:

Are there no entries in the Event Log (Directory Service)? Have you used
Replmon (Gui tool - part of Support Tools) to check the status of the
replication links. It will at least tell you when it last tried. In
addition, you can also force replication through this utility.

Another thing to look at in Active Directory - Sites and Services. Are
there replication connection objects between all of the DCs underneath NTDS
Settings. If not, right -click and select Check Replication Topology (or
something very similar).

"Edita" wrote:

I checked what you proposed and all four DC's are pointing to the same DNS
server and all the GUID records are in place. i can't find any sign of error
anywhere and i have no idea what to do....

"Steve B" wrote:

Could be a DNS issue. Take a look under _msdc.<forest name>. Are the GUID
records there for all four domain controllers? GUID records will have a type
CNAME and then a long string of letters and numbers. GUID records are
required for AD replication.

If you not sure - point all your DCs to the same Preferred DNS Server (make
a note of where they currently point to). At a command prompt - type net
stop netlogon and then net start netlogon. This will register the GUID
records. Check replication. Reconfigure DNS back to how it was before.

"Edita" wrote:

Hi,
I have three dc’s in the Default-First-Site (DC1,DC2,DC3) and they are all
replicating correctly with each other. Recently I have installed DC4 and I
put it in Default-First-Site. Now I have the situation that the DC3 cannot
see DC4 and DC4 cannot see DC3. Also for some totally unknown reasons DC1 and
DC2 don’t see (replicate) each other any more although they worked normally
until few days ago. I couldn’t find anny erros anywhere and I have no idea
what is happening.
I’d appreciate any help

Thanks


.



Relevant Pages

  • Re: Merge Replication Topology and Virtual Machines...
    ... Looking for a SQL Server replication book? ... Our subscribers will be offline while entering data and will go online ... Our current topology is a Centralized Publisher and Distributor, ... Move to a "Central Publisher with Remote Distributor" topology. ...
    (microsoft.public.sqlserver.replication)
  • Re: Replication Issue?
    ... if you'd like to change the topology. ... If you decide to change the replication topology take into account the ... The site for the main domain contains 2 DCs. ... > between the 2 remote sites. ...
    (microsoft.public.win2000.active_directory)
  • Re: New DC
    ... You have only one connection at all sites? ... The KCC analyzes the replication topology within a site every 15 minutes to ... additional connection objects across the ring structure so that if a change ...
    (microsoft.public.windows.server.active_directory)
  • Re: DNS Replication behavior
    ... the DNS replication behavior, about, if DNS Forest Directory ... The other is the forest replication topology. ... You can view the partnerships in Sites and Services, NTDS, ...
    (microsoft.public.windows.server.networking)
  • Re: replication topology
    ... 'other' sites for replication to/from each other? ... If there are alternative WAN Links then: ... KCC would treat the Site Links as transitivie Spoke-Hub-Spoke ... On the connection objects however, they appear to be configured to ...
    (microsoft.public.win2000.active_directory)