Repadmin gives operational error 58

44,499

After some investigation, I found that a set of firewall rules was completely blocking communication between the site in question and the remote site, which happened to be the FSMO roles holder. Without the ability to talk to the FSMO masters, things started getting weird.

So, make sure if you run into this error that you double and triple-check that your firewall rules are not blocking communication between your domain controllers.

In our case, we were completely blocking all communication to the DC, so the non-smart-ass answer to your query @Iain is "all of them." Sorry I can't be more specific!

44,499

user1364702

Sysadmin, Assister for Users of Technology, Writer of Words, and Flixer of Nets

Updated on September 18, 2022

Comments

user1364702 almost 2 years
While testing some remote DC's, "repadmin /replsummary" ended with an error of
```
   Experienced the following operational errors trying to retrieve replication information:
       58 - mydc1.mydomain.com
       58 - mydc2.mydomain.com
```
Information for "Source DSA" for mydc1 and mydc2 both show up with 0 fails/errors; the information is lacking under Destination DSA. This domain controller I ran the command on (remotedc1) can see mydc1 and mydc2.

Pinging from remotedc1 to mydc2 and mydc1 shows an average time of 43ms...

What causes this kind of error?
- MDMarra over 11 years
  
  I know you guys were offline for quite a while. Any chance that your DCs in NYC were offline long enough to hit the 180 day tombstone lifetime?
- user1364702 over 11 years
  
  We've had internal networks up before the 180 days also :-)
- MDMarra over 11 years
  
  Ok, that's good at least. What happens when you try and force a sync with repadmin /syncall /APed? Any interesting feedback?
- Peter Grace over 11 years
  
  We never went more than 3 days without DCs able to talk to each other.
- MDMarra over 11 years
  
  OK, PETE, I GET IT! NO TOMBSTONES :)
- Peter Grace over 11 years
  
  Hey, he asked me to pipe up, I'll go back to my hole now...
user9517 over 11 years

Which particular rules were causing the problem ?
Peter Grace over 11 years

In our case, we were completely blocking all communication to the DC, so the non-smart-ass answer to your query @Iain is "all of them." Sorry I can't be more specific!
user9517 over 11 years

Knowing that is more useful than a plain check your firewall - thanks.