replication problem

  • Thread starter Thread starter debra
  • Start date Start date
D

debra

AD stopped replicating to other servers on network. When
investigating the matter I did a nslookup and my domain
server came up...domain not found. How do I begin to
resolve this. Someone mentioned that the master browser
may need to be restarted, is that the case and how does
one start the master browser?
 
Are you able to ping <mydomainname>.com and get a reply?
You should also be able to ping any dc in your domain
<servername>.<mydomainname>.com (or whatever your domain fqdn is)
If not, then you need to address the dns name resolution, and once that
starts working, the replication will probably start working again too.
Verify that in dns, under the zone for your domain, when you highlight the
"_tcp" folder that you see ldap, kerberos, and kpasswd for each dc that you
have, and a gc record for how ever many gc's that you have (should be at
least one)

--
David Brandt
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.
 
David, thanks for answering my problem report. I was able
to complete all steps you mentioned without any problems,
everything checks out. So does that mean there is not a
DNS name resolution problem? What else can I look at to
get the replication working again?
 
Hate to say it, but really depends on a lot of things about how your network
is set up. I mean are all dc/s in the same AD site or multiple sites, what
errors/events you see in the event logs that refer to this problem, what
error do you see when you highlight the ntds settings under your dc in AD
sites/services adn the right click on teh replication objects in the right
pane and choose replicate now.
If the support tools are not installed on these machines I would install
them off the server CD (support/tools/setup.exe) and then run "dcdiag /v"
and "netdiag /v" (they can also be piped to txt file) and see what they
report.
Sort of hate to say it, but that is a pretty open ended question and need a
lot more info to really be able to say where the problem might be. However
if you see all of the records, and all your dc's are able to ping everybody
ok along with the domain name, that would appear to indicate that dns is
probably ok.

--
David Brandt
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.
 
David, The warning message in Event Viewer, Directory
Service is...Source: NTDS KCC, Category: Knowledge
Consistency Event ID: 1265 (The Event to establish a
replication link with parameters.....given
parameters....Failed with the following status. The RPC
Server is too busy to complete this operation.) This
warning message has been repeated since we started having
these problems around the 19th of January.
 
I am having almost exactly the same problem except that the Event Viewer is showing NTDS KCC Event Id 1308. Active Directory replication stopped pretty much the same time as your did.
 
Back
Top