TS-WXL to TS-WXL WAN replication problem

[Naster]

Hi forum,
I'm new to the product line so learning as I go.
I have two TS-WXL's. One is in a main office storing server backups, the other is in another building on a different network. I set the second TS-WXL to replicate the data from the shared folder of the first that had the backups in it.  I followed all procedures I could find. (ie forwarded ports listed in documentation, set folders to disk backup). The first time I resynced the devices the replication worked. However all subsequent attempts to replicate have failed.
No error showed on either NAS but I did get a "replication_error" on the source NAS and a "Unable to connect to ntp server" error in the syslog of the second NAS.
I've tried various different ntp servers and opened up port 123 for ntp as well, still no connection there.
Source NAS is behind a consumer grade D-link router with appropriate ports opened and a static ip. Target NAS is behind a consumer grade Lynksys router with ports opened and a static ip.
Firmware is 1.58. (North America)
I was wondering if there is a bandwidth minimum for replication over internet as the area can have very pour throughput at times.

[Naster]

Update.
    Both NAS are now running 1.60
    Full model on NAS2 is TS-WX4.0TL/R1
    Will confirm model of NAS1 soon.

I resync'd the NAS' and while that was still in progress the targed NAS gave the error E26 replication error, with the alarm, led and red background.  This is the first time either device has done this.
Site two speedtest was very poor; Down 2.41Mbps, Up 0.47Mbps.
Is there a bandwidth minimum for replication?

Edit:
This is what was in the syslog

Code Select Expand

Jul 20 00:39:24 TS-WXLEB2 errormon[1498]: Error situation detected! Replication  E26ReplicateFailure
Jul 20 00:39:31 TS-WXLEB2 linkstation: Replication error occured.
Jul 20 00:39:45 TS-WXLEB2 kernelmon: cmd=micon_interrupts

[Naster]

Update2:
Site one speed test was worse, 0.53Mbps Down :o, 0.47Up

[Naster]

Any help on the bandwidth question?
Is there a minimum for replication?

[Eastmarch]

Are you simply port forwarding replication packets that hit your internet-side IP to the NAS? This is going to be a very poor method, if it works at all. Those speeds are going to make it slow even if you did create a VPN tunnel. Most consumer grade routers can act as a VPN server, though most routers cannot be a VPN client (DD-WRT has this functionality, however).

First step is to create a pingable connection between the two machines via VPN. Simply forwarding packets is not going to work. Second step is to upgrade your internet connection. Replication is a bandwidth-intensive feature and doing it over slow internet is only going to cause you heartache. It might be faster to run a nightly backup and drive to site two to copy it over, and that isn't sarcasm.  ;)

[Naster]

Yes in the end we'll be waiting on the bandwidth to improve.  Support said that 1M up was a minimum for reliable replication so no real options here.

[Eastmarch]

Yeah, the agent pinged me about this case as well.

If you get a better connection, still be sure to do the VPN. Even with good bandwidth, just port forwarding won't do it.

Ben

[Naster]

Figured it would be better to necro this post.
I now have a functioning VPN between the two locations. Upload speed is floating around 1Mbps.
However when I go into the source NAS gui to the "View NAS devices" it is not showing the remote NAS at all.
Using a cisco RV082 on the source NAS side and a Cisco RV120W on the target side.
Both routers have a static WAN ip.
opened ports 873, 22938 - 22939 even though should not be needed as the VPN is up now.
I'm stumped.


Edit: Another question, PPPoE has an MTU of 1492 and the smallest frame size I can set the NAS to is 1518. Will this cause problems?