Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 990
  • Last Modified:

NTDS Replication Errors

I have recently started looking after a network that has 2 servers running. The first is a Windows  SBS2003 Server and the second is Windows 2003 Standard Server.

My main concern with these servers is the presence of these errors in the logs:

Directory Service Log - NTDS Replication Error Event ID 1864
Directory Service Log - NTDS Replication Warning Event ID 2092

The  NTDS Replication Warning Event ID 2092 error suggests running repadmin /showrepl as a diagnostic step and it returns 16472 CONSECUTIVE FAILURES since 2007-09-04 17:24:54 and as the 2003 Standard server was installed with its OS on the 2007-09-06 I am lead to believe that the replication has never worked.

I havent worked with replication before but think in this situation that it would be safe to just disable it.

any advise would be appreciated
0
kylegreig
Asked:
kylegreig
  • 3
  • 2
1 Solution
 
GMorineauCommented:
You can´t just disable it.... the replication is very important between DCs.

verify if the sysvol share exist it this second server and if it populated.
0
 
kylegreigAuthor Commented:
16472 CONSECUTIVE FAILURES since 2007-09-04 17:24:54

The server that it is meant to be replicating too was installed with its operating system on the 2007-09-06 which is 2 days after replication was configured. From the 16472 consecutive failures from 2 days prior to the second server being implemented, it never worked in the first place.

There is no sysvol share on the second server.

I have had advice that it should be ok to disable replication or maybe the better option would be to configure it correctly??

All of the equipment is in the one location and is as follows:
1 x SBS Server - ISS Application, domain controller, file server, ISA
1 x Windows 2003 Standard - Exchange
17 x Workstations running windows XP
0
 
GMorineauCommented:
well...

You have a huge Active Directory problem. The AD in the second server is useless. Do you have any network service running in this server? or share folders? anyway... you will need fix this AD and it is a very complex job. I´m not sure that is safe to be done by forum... too many variables in this case must be carefuly anticiped. May be is better to contact a local MCSE.
0
 
kylegreigAuthor Commented:
I cannot see any active directory services running on the second machine. I have attached a screenshot of administrative tools list and there is no active directory options in there.

From what I can tell, the second server appears to be only enrolled in the domain and not promoted to any domain controller role. The first server was configured for replciation but no secondary server is accepting that responsability.

Is there anything that I can check to confirm this? If you think best to speak with a local MCSE then thats what I need to do but I get the feeling that it should be as simple as disabling the replication from the SBS server. It doesnt appear that the relationship with the other domain controller has never stood up.
active-directory.PNG
0
 
GMorineauCommented:
True.
You don´t have Active Directory in this server. Great. no MCSE needed! But it still strange.

Check in your SBS Server, in Active Directory Sites and Services: default-first-site-name/ Servers/"Servername"/NTDS Settings, if you have a replication partner. If yes, someone tried to setup a second DC and when he remove it, he forgot to cleanup the AD.

Just delete this entry if exist.
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now