RE: FRS Only replicates on inbound connection, no changes go out.



Hi run frsdiag and look at the constat txt file and see when they last
joined. A quick win is to delete the connection obnjects under sites and
serivces on both sides then run repadmin /kcc on both servers then see if
they have joined correctly now. You may have to stop and start ntfrs as well

"Mike Drechsler - SPAM PROTECTED EMAIL" wrote:

> I have a pair of servers in a small network that will only do file
> replication in one direction.
>
> Any changes made on the main server are replicating over to the offsite
> server but changes made on the offsite server do not make it back to the
> main server.
>
> The strange thing is that if you investigate with Sonar. There are no
> files backlogged on either server. I installed Ultrasound and the only
> things it show are a few sharing violations on one of the DFS replicas
> but all other items appear to be ok. I cleaned up some of the sharing
> violations but it does not help. There are 2 other DFS links and the
> sysvol that show no errors but none will send changes back to the main
> server. I tried doing a D2 restore on the sysvol on the offsite server
> but this did not help. I have restarted both servers many times. Both
> are running Windows 2000 Server Std. All patches from windows update
> are installed and I even tried the hotfix in KB article 815473 but that
> didn't fix the replication problem (though I do get the event log
> entries for those sharing violations now).
>
> I get an event 13508 for the DFS link that has the sharing violations
> but not for sysvol or the other 2 DFS links. Files from the main server
> still replicate to the DFS link getting the 13508 event so it doesn't
> seem to amount to much. The main server shows the same 13508 for the
> same DFS link but nothing else.
>
> Replication between the two servers has worked fine in the past. It
> just started doing this around July 27. The only events I recall from
> that time was one of the servers ran out of hard drive space around
> then, but it's been fixed and there is plenty of free space on both now.
> The other event was a power outage but the UPS has shutdown software
> running so the servers would have shut themselves down.
>
>
> --
> WARNING! Email address has been altered for spam resistance.
> Please remove the -deletethispart-. section before replying directly.
> Mike Drechsler (mike-newsgroup@xxxxxxxxxxxxxxxxxxxxxxxxxxxx)
>
.



Relevant Pages

  • Re: SBS 2003 and Replication Errors with Remote DC
    ... I just promoted the remote DC last week, so I still have time to solve the replication issues. ... Domain Controller Diagnosis ... Connecting to directory service on server alpha. ... Performing upstream analysis. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 and Replication Errors with Remote DC
    ... alpha server as soon as you can to get things going. ... A simple DNS replication test is to create a host record in the SBS server ... Domain Controller Diagnosis ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 and Replication Errors with Remote DC
    ... I did make the changes that you suggested on the DNS of my alpha server and rebooted. ... I did run the simple DNS test that you suggested by adding a host record to my SBS server. ... A simple DNS replication test is to create a host record in the SBS server and wait till it shows up in the remote server. ...
    (microsoft.public.windows.server.sbs)
  • Re: Unable to decommission a Windows 2008 DC via dcpromo
    ... Can you open and compare sysvol and netlogon share on both DCs? ... Verifying that the local machine server2, ... The File Replication Service Event log test ... Latency information for 8 entries in the vector were ...
    (microsoft.public.windows.server.active_directory)
  • Re: adding 64-bit R2 DC to existing domain
    ... Server 2003 standard edition 32-bit domain controllers. ... The schema master did not complete a replication cycle ..." ... server1 failed test KnowsOfRoleHolders ... ForestDnsZones failed test CrossRefValidation ...
    (microsoft.public.windows.server.setup)