| kc1 wrote: |
|---|
| StephenB wrote: |
|---|
| I also use fios. |
What's that? |
Your traceroute indicates that your US ISP is Verizon Fios (pool-108-20-43-198.bstnma.
fios.verizon.net)
| kc1 wrote: |
|---|
| StephenB wrote: |
|---|
| for file transfers I would suggest FTP |
All I'm trying to do with frontview is setup an rsync backup to pull data from the local NAS from a remote NAS...which I thought was the whole idea with these boxes? |
You can also choose FTP for backup, though I've not tried it myself. I was thinking more about remote file access than backup when I made the FTP suggestion.
| kc1 wrote: |
|---|
| StephenB wrote: |
|---|
| Even if you have fast connections at both locations, you are still subject to cross-congestion / slowdowns on the full wide area connection path |
What can be done to deal with or improve this, so that it at least works? Surely I can't be the only one with a ReadyNAS on both sides of the Atlantic? |
Large companies make their own deals with ISPs that have performance guarantees ("service level agreements"). The rest of us get to use best-effort internet service, so we have to live with what we get. In your case, the problem could be with your UK or US providers, or Level3 (which is doing the London to NY hop). What usually happens if you complain is that the service providers all point to someone else. The speed limit is not because of the ReadyNAS, it is certainly faster than your wide area network connections.
Are you attempting to connect with ReadyNas remote??? I don't think that would be fast enough for a backup (and it is not intended for that). Assuming no: if you
never get a functional frontview connection to the remote system [from any remote site], you could have a port forwarding problem on the US site's router. And you will also need to configure proper port forwarding for rsync (which router depends on where the backup job is being run).
Your traceroute provides latency information, but doesn't give any idea about throughput. The "Request timed out" hop is almost certainly not an error - that router is likely configured to ignore ping requests. Maybe you could try making some reasonable size files transfers (either with rsync or FTP), and post the measured transfer speeds and sizes?
