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



In news:SnfOe.76846$576.48391@xxxxxxxxxxxxxxxxxxxxxx,
Mike Drechsler - SPAM PROTECTED EMAIL
<mike-newsgroup@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> made this post, which I then
commented about below:

> Another good idea.
>
> I did some MTU tests, messed with the MTU sizes on the routers on
> either end and I'm 99.99% sure that there is no MTU or WAN issues
> blocking replication. I changed the MTU values of the tunnels to be
> manualy set to make sure. I can do RPC communication (view event
> logs remotely) withough problems on either machine. I can transfer
> large or small files without problems. I can do ping tests with the
> -f (do not fragment) switch and it correctly reports the packet
> requires fragmenting when it reaches a certain size with no "gap"
> where it simply goes into a request timed out mode. (IE. packets
> size 1416 works, size 1417 gives "packet requires fragmenting but DF
> bit set" as it should). The routers on both ends have no packet
> filters installed between the sites, it's wide open between the two
> for traffic on any port, any protocol, and any address. Packetloss
> as measured by ping tests with 1416byte data sizes show 0 lost
> packets and over 1000 received while transferring an 80GB file from
> the remote server to the main server.
> I let it run for about 90 minutes and did a restart of both servers
> just after changing the MTU values on the routers. It is only doing
> the replication in a single direction. As a further test I created a
> new DFS link with some test folders. I threw a few text files into
> the remoteserver and set it as the master when enabling replication. After
> everything settled down the files appeared on the main server
> as you would expect but after this, new files added on the remote
> server or changes to existing files are not being replicated to the
> main server. Changes on the main server are replicating to the
> offsite server just the same as all the other DFS and sysvol folders
> so even a brand new folder setup exibits the problem which means D4
> and D2 restore is not likely going to help me either.

What did you change the MTU to? Are you saying the MTU is set to 1500 on
both sides now? They should be left alone at 1500. If not, LDAP loses it's
ability to communicate, even though RPC will work fine.

What sort of line do you have, T1, ADSL or cable?

Can we see an edited ipconfig /all from both DCs please?

Ace



.



Relevant Pages

  • Re: POP3 Connector Issue
    ... the DF number will always be 28 bytes less than the MTU ... using this ping test. ... your server is not connected to the Internet." ... the router should return the message "packet needs to ...
    (microsoft.public.windows.server.sbs)
  • PROBLEM: Oops, nfsd, networking
    ... NFSD crash at large MTU and odd wsize/rsize. ... over NFS to a Linux NFS server. ... Our product is essentially a high end media server that takes in up to ... null getattr setattr root lookup readlink ...
    (Linux-Kernel)
  • Re: AD Replication over SonicWall site-to-site VPN
    ... The MTU can be an Issue: ... Test your MTU from the problem server by pinging the gateway of your router: ... Kerberos authentication service to use TCP instead of UDP. ... there are no explicit prohibitions on any of the ports required. ...
    (microsoft.public.windows.server.active_directory)
  • RE: POP 3 Errors/Warnings
    ... Server MTU is 1472, Router MTU was 1468. ... You can find the method how to set the MTU value for SBS server in my last ...
    (microsoft.public.windows.server.sbs)
  • Re: FRS Only replicates on inbound connection, no changes go out.
    ... All DFS entires show that both in and outbound replication is joined and the status shows OLP_ELIGIBLE but all 3 DFS replicas also only replicate changes into the remote server but not out from it just like sysvol. ... It turned out he recently upgraded one of his VPN router's firmware and specifically the MTU. ... I can do ping tests with the -f switch and it correctly reports the packet requires fragmenting when it reaches a certain size with no "gap" where it simply goes into a request timed out mode. ...
    (microsoft.public.windows.server.active_directory)

Loading