Replication Problems

[Ricky]

I'm migrating some servers from one network to another network and one of my
servers is giving the following errors in the event log:

*****************************APPLICATION
LOG*********************************
LDAP Bind was unsuccessful on directory ServerXXX for distinguished name ''.
Directory returned error:[0x51] Server Down.

For more information, click http://www.microsoft.com/contentredirect.asp.

*****************************DIRECTORY SERVICE
LOG*********************************
with the following directory partition.

Directory partition:
CN=Configuration,DC=myDomain,DC=br

There is insufficient site connectivity information in Active Directory
Sites and Services for the KCC to create a spanning tree replication
topology. Or, one or more domain controllers with this directory partition
are unable to replicate the directory partition information. This is
probably due to inaccessible domain controllers.

User Action
Use Active Directory Sites and Services to perform one of the following
actions:
- Publish sufficient site connectivity information so that the KCC can
determine a route by which this directory partition can reach this site.
This is the preferred option.
- Add a Connection object to a domain controller that contains the directory
partition in this site from a domain controller that contains the same
directory partition in another site.

If neither of the Active Directory Sites and Services tasks correct this
condition, see previous events logged by the KCC that identify the
inaccessible domain controllers.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

------------------------------------------------------------------------------------
All domain controllers in the following site that can replicate the
directory partition over this transport are currently unavailable.

Site:
CN=XPTO,CN=Sites,CN=Configuration,DC=MyDomain,DC=br
Directory partition:
CN=Configuration,DC=MyDomain,DC=br
Transport:
CN=IP,CN=Inter-Site Transports,CN=Sites,CN=Configuration,DC=idt,DC=br

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


***********************************************************************************
***********************************************************************************
When i execute the same command at the server where i've change the network
it gives the following message:

LocalSite\ServerXXX via RPC
DC object GUID: ca0c0137-08b3-4f6f-a91d-36a8c67eba57
Last attempt @ 2007-02-28 20:20:02 failed, result 1722 (0x6ba):
Can't retrieve message string 1722 (0x6ba), error 1815.
1206 consecutive failure(s).
Last success @ 2007-02-09 06:48:29.


But when I execute the command "repadmin /showreps" at the master domain
controller it gives the following message
C:\>repadmin /showreps
LocalSite\ServerXXX
DC Options: IS_GC
Site Options: (none)
DC object GUID: ca0c0137-08b3-4f6f-a91d-36a8c67eba57
DC invocationID: 9571ec43-a3ef-4463-b8c3-65aef9d3858c

==== INBOUND NEIGHBORS ======================================

DC=myDomain,DC=br
MasterDomain\MasterServer via RPC
DC object GUID: 0f7afc52-c653-4546-bf11-1f5a3bc0dd65
Last attempt @ 2007-02-28 20:13:52 failed, result 1726 (0x6be):
The remote procedure call failed.
1 consecutive failure(s).
Last success @ 2007-02-28 19:58:53.

CN=Configuration,DC=myDomain,DC=br
MasterDomain\MasterServer via RPC
DC object GUID: 0f7afc52-c653-4546-bf11-1f5a3bc0dd65
Last attempt @ 2007-02-28 20:13:51 failed, result 1726 (0x6be):
The remote procedure call failed.
1 consecutive failure(s).
Last success @ 2007-02-28 19:58:52.

CN=Schema,CN=Configuration,DC=myDomain,DC=br
MasterDomain\MasterServer via RPC
DC object GUID: 0f7afc52-c653-4546-bf11-1f5a3bc0dd65
Last attempt @ 2007-02-28 20:13:51 failed, result 1726 (0x6be):
The remote procedure call failed.
1 consecutive failure(s).
Last success @ 2007-02-28 19:58:52.

DC=DomainDnsZones,DC=myDomain,DC=br
MasterDomain\MasterServer via RPC
DC object GUID: 0f7afc52-c653-4546-bf11-1f5a3bc0dd65
Last attempt @ 2007-02-28 20:13:51 failed, result 1256 (0x4e8):
The remote system is not available. For information about
network troubleshooting, see Windows Help.
1 consecutive failure(s).
Last success @ 2007-02-28 19:58:53.

DC=ForestDnsZones,DC=myDomain,DC=br
MasterDomain\MasterServer via RPC
DC object GUID: 0f7afc52-c653-4546-bf11-1f5a3bc0dd65
Last attempt @ 2007-02-28 20:13:51 failed, result 1256 (0x4e8):
The remote system is not available. For information about
network tr
oubleshooting, see Windows Help.
1 consecutive failure(s).
Last success @ 2007-02-28 19:58:54.
DsBindWithCred to ServerXXX failed with status 1722 (0x6ba):
The RPC server is unavailable.


I hope someone can help me in this hard issue.

Thanks in advance
[]
Ricky

 

[Paul Williams [MVP]]

The servers that are currently set to replicate with this server cannot
resolve the name of this server to its new IP address. This is probably
down to the fact that the network change hasn't updated in DNS. Point the
server that is unable to replicate to a central DNS server and restart
NETLOGON. Manually trigger replication with a DC that is pointing to the
same DNS server, or wait for replication of the DNS updates to propagate,
then manually replicate. Once done, you can change DNS back to what it was
(assuming it was a valid configuration).

Note. If the DC is pointing to self for DNS, ensure that it's listening on
all interfaces, or the single interface has been updated.

 

[Ricky]

Hi Paul

The problem is solved. Thanks for the tips but could you explain me how can
i do a restart to NETLOGON? just for future problems.

[]
Ricky

 

[Paul Williams [MVP]]

NETLOGON is a service, so you can restart it in a number of ways. The two
most common are probably using the SCM MMC Interface (SERVICES.MSC) or NET
STOP/ NET START and/ or SC.

e.g.

net stop netlogon & net start netlogon


Typing the above at a command prompt will restart the service.

NETLOGON is responsible for registering the DCs SRV RRs in DNS. In 2000 it
used to try and register SRV records every 60 mins (it might not be
successful depending on your aging settings). In 2003 this was changed to
24 hours. Manually restarting the service causes the DNS update to be
attempted.

There are other ways of doing this, e.g. NETDIAG, but this is painless and
quick.