windowswideopen.com

RPC_Server_is_not_available Event id: 1265

When the local DC tries to establish a replication link with it’s replication partner and it fails.

In that case, repadmin/showreps shows no inbound neighbors, so it doesn’t tell this error. To see it, go to the “Directory Service” event log in which the following event is logged:

Event ID 1265

The attempt to establish a replication link with parameters

Partition: DC=domain,DC=enterprise,DC=com

Source DSA DN: CN=NTDS Settings,CN=HubDC,CN=Servers,CN=DMZ- Administration,CN=Sites,CN=Configuration,DC=company,DC=com

Source DSA Address: 62d85225-76bf-4b46-b929-25a1bb295f51._msdcs.enterprise.com

Inter-site Transport (if any): CN=IP,CN=Inter-Site Transports,CN=Sites,CN=Configuration,DC=enterprise,DC=com

failed with the following status:

Technorati tags: The RPC server is unavailable, GUID, ping

.

The record data is the status code. This operation will be retried.

To troubleshoot this error :

First ping the GUID based DNS name displayed in the content of the message. This name is composed of the GUID of the “NTDS Settings” object of the replication partner, followed by “_msdcs.enterprise.com”. It is declared on the root server of the forest as an alias name pointing to the DC name.

For example :

ping 62d85225-76bf-4b46-b929-25a1bb295f51._msdcs.enterprise.com

Pinging HubDC.domain.enterprise.com[10.18.22.11] with 32 bytes of data:

…

From the output of the ping command, check the <GUID>_msdcs record can be properly resolved by the DNS server at the root of the forest. This is true as long as the output shows “Pinging ” followed by the FQDN of the DC.
Note that this name should always be resolved with the “RPC server not available” error. If it could not be resolved, the error would then be “DNS lookup failure”.

Once the ping command works, replication should then work properly.

Active DirectoryActive Directory