NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Remote access to frontview unusably slow - what can be done?
Hi, not sure if this is the right place for this question, but here goes:
How can I improve or even influence the speed of accessing a remote NAS from across the Atlantic? I'm trying to set up a backup between an Ultra 4 Plus and NV+ on either side of the Atlantic but accessing Frontview is the first problem - it won't fully load (just the background).
At my end the connection is 37.4mbps down and 8 up, at the other end it's 22.4 down and 23.7 up
A tracert shows:
What can be done to achieve a workable speed
How can I improve or even influence the speed of accessing a remote NAS from across the Atlantic? I'm trying to set up a backup between an Ultra 4 Plus and NV+ on either side of the Atlantic but accessing Frontview is the first problem - it won't fully load (just the background).
At my end the connection is 37.4mbps down and 8 up, at the other end it's 22.4 down and 23.7 up
A tracert shows:
Tracing route to pool-108-20-43-198.bstnma.fios.verizon.net [108.20.43.198]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.254
2 6 ms 6 ms 6 ms 217.32.146.171
3 6 ms 7 ms 6 ms 217.32.146.222
4 7 ms 6 ms 7 ms 213.120.177.106
5 7 ms 6 ms 6 ms 213.120.176.74
6 7 ms 7 ms 7 ms 213.120.176.182
7 7 ms 7 ms 6 ms acc2-10GigE-0-2-0-5.l-far.21cn-ipp.bt.net [109.159.249.227]
8 12 ms 10 ms 11 ms core2-te0-14-4-0.ealing.ukcore.bt.net [109.159.249.143]
9 7 ms 7 ms 7 ms transit2-xe1-1-0.ealing.ukcore.bt.net [62.6.200.142]
10 7 ms 7 ms 7 ms t2c4-xe-9-1-0.uk-eal.eu.bt.net [166.49.168.53]
11 8 ms 8 ms 8 ms xe-8-0-0.edge4.London2.Level3.net [212.187.192.61]
12 18 ms 17 ms 17 ms ae-31-53.ebr1.London2.Level3.net [4.68.117.94]
13 8 ms 15 ms 17 ms ae-1-100.ebr2.London2.Level3.net [4.69.141.118]
14 8 ms 8 ms 8 ms ae-3-3.ebr1.London1.Level3.net [4.69.141.189]
15 9 ms 8 ms 8 ms vlan103.ebr2.London1.Level3.net [4.69.143.94]
16 77 ms 77 ms 77 ms ae-42-42.ebr1.NewYork1.Level3.net [4.69.137.70]
17 77 ms 77 ms 77 ms ae-4-4.ebr1.NewYork2.Level3.net [4.69.141.18]
18 86 ms 77 ms 77 ms ae-1-51.edge2.NewYork2.Level3.net [4.69.138.195]
19 76 ms 76 ms 76 ms Verizon-level3-2x10g.NewYork.Level3.net [4.68.62.42]
20 76 ms 76 ms 76 ms 0.ae1.XL4.NYC1.ALTER.NET [152.63.18.233]
21 93 ms 93 ms 93 ms xe-4-1-2-0.NY5030-BB-RTR1.verizon-gni.net [130.81.17.122]
22 * * * Request timed out.
23 93 ms 94 ms 94 ms pool-108-20-43-198.bstnma.fios.verizon.net [108.20.remote.ip]
Trace complete.
What can be done to achieve a workable speed
22 Replies
Replies have been turned off for this discussion
StephenB wrote:
I suggest you start a new thread on your problem, since having two conversations on this thread will be very confusing.Jjnsgy wrote: Can I trouble you for more specific instructions for a noob? A little about the port forwarding, but the front view access remotely.
Also, I am just setting up my nas and do have port 80 forwarded (to test - understand security risks and will change later on) and also have port 443 forwarded to the NAS. When I log on remotely (with IP address or with my domain name assigned by TZO - option for linksys router) with HTTP or HTTPS, I connect (I think) but get a blank page and it appears to be stuck in a loop of trying to load something from the server (IE reads "connecting") - but nothing comes up. Suggestions?
My apologies and will do so. Thanks for your help. But will have solved the problem and will post the solution here:
My primary router is a Linksys e4200. Unfortunately, it is located in a closet and the house is well shielded so the room where the NAS is has poor wireless access - but is wired on a LAN. I plugged my old WRK54G (all DHCP turned off, acting as a switch and WAP) and connected the NAS to this (in addition to stereo receiver and Sony Bluray player) - all are connected to the ethernet ports. Somehow, the wrk54g was blocking access. When I connected the NAS directly (omitting the WRK54G), everything worked like a charm!
Thanks for the assistance!
Ok. Turning off DHCP is not enough to turn a router into a switch. It is still acting as a NAT router between the WAN connection and LAN connections. This could certainly block connections.Jjnsgy wrote: I plugged my old WRK54G (all DHCP turned off, acting as a switch and WAP) and connected the NAS to this (in addition to stereo receiver and Sony Bluray player) - all are connected to the ethernet ports. Somehow, the wrk54g was blocking access. When I connected the NAS directly (omitting the WRK54G), everything worked like a charm!
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
