|I am looking to get remote access to my NAS device. |
Please only respond if you have practical experience (that means you have done this... I have seen too many posts out there from people who think how this should work, but no actual experience doing it) and you have a similar setup.
I have a Lacie Net Space Max that advertises that it can be accessed remotely over the internet. They even provide a video which teaches you "how to setup a dynamic dns" and how to enter your dyndns host in the Lacie's user interface... and that's it. As if that were enough to access the device from the internet. (very disappointing).
I have, as many internet users do, a DSL modem (westell 7500 fro verizon) to get internet access.
That DSL modem connects to a Switch (no IP assigned to the switch).
Connected to the switch I have several net devices (all with static IP addesses like 192.168.1.xxx):
A desktop (xxx=14),
A laptop (xxx=125),
A network printer (xxx=3) and
The Lacie NAS (xxx=198).
The DSL modem internal IP is 192.168.1.100..
The external ip is whatever Verizon gives it from time to time. Lets assume it is 22.214.171.124 just for the sake of this question. No DHCP service is provided by the DSL modem to the internal network.
This modem has its own Firewall, with various levels of protection (high, medium, low, none, and custom).
Each level has its own set of open ports (I can not see what they are). I have set it up at high.
The DSL modem also has a Port forwarding feature, with only one entry in it:
Rule Name Mode Host Action
IPSEC ALG Client Dynamic
The IPSEC rule is defined as Protocol=Both(tcp,udp), Global Ports= 500, Local/BaseHost Port= 500
I am not a network expert, but I assume that IPSEC must be a necessary active forwarding rule to allow the DSL modem to pass thru all the incoming and outgoing traffic from and to any of my computers.
No other ports seem to be forwarded, not even port 80.
Now, from inside my network, if I browse http://192.168.1.198.. I get to the Lacie User interface (UI), which means port 80 is listening on the Lacie's web server.
Obviuosly, if i browse to http://192.168.1.100, I get to the DSL modem's UI, form inside my network, which means the modems web server is also listening on port 80.
If I browse to http://126.96.36.199 (the external dsl modem's ip, given by verizon) I also get to the modem's UI, whcih means, its web server is also listening on port 80 for that external IP address. This means, with this ISP service I may not be able to forward port 80, otherwise I would not be able to access the modem's UI from outside.
I have tried to port forward to access my NAS as follows.
Created a rule
name= NASLacie50080 where the protocol=tcp, mode=Host, Host=192.168.1.198, global port=50080, local port=80
with the intention of browsing http://188.8.131.52:50080 and have the DSL modem detect a request to port 50080 and forward it as port 80 to 192.168.1.198.
but I get this error
Unable to connect
Firefox can't establish a connection to the server at 184.108.40.206:50180
(I masked the actual external IP address) I have pinged this URL and the IP resolves
fine, but it does not mean the port is responding
This could mean that port forwarding function of the modem is not really working (please do no suggest to reset or reboot the modem. I have already done it, multiple times, or to reboot the Lacie drive.., done that too).
I do not have access to the NAS OS (I think it is linux based), So I cannot test if port forwarding is actually going to it.
Since I have an internal webserver running on my desktop (192.168.1.14), I also added a forwarding rule to forward port 50280 to port 80 on 192.168.1.14. Then browsed to 220.127.116.11:50180... I get the same error
Unable to connect
Firefox can't establish a connection to the server at 18.104.22.168:50280
Does anyone have an understanding of what may be happening? and how to make thsi port forwarding thing to work well? Please only if you have practical experience making something like this work.