NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Accessing a share via HTTP
I've followed the standard instructions here on the ReadyNAS site for creating a web server share, and set the permissions as required (read only access via HTTP enabled, Login authentication disabled).
I've placed my test html file in this share directory, and I can successfully access it on the LAN in a browser via: http://<ReadyNAS LAN IP>
The instructions then say to forward port 80, for WAN HTML connections, to the ReadyNAS's static LAN IP address (static IP is already set up), and I have logged into the router and created a rule for this, as per the instructions on portforward.com.
I've rebooted the Router and the NAS for good measure, and according to the directions I have followed, I should now be able to access my website from the web via: <http://Public_IP> however when I enter this URL I am being served the login prompt for my router. What could be causing that, and does it indicate where I've gone wrong?
I'm working with:
ReadyNAS Duo
Netcomm N300 (NB304N) router
OSX
I've placed my test html file in this share directory, and I can successfully access it on the LAN in a browser via: http://<ReadyNAS LAN IP>
The instructions then say to forward port 80, for WAN HTML connections, to the ReadyNAS's static LAN IP address (static IP is already set up), and I have logged into the router and created a rule for this, as per the instructions on portforward.com.
I've rebooted the Router and the NAS for good measure, and according to the directions I have followed, I should now be able to access my website from the web via: <http://Public_IP> however when I enter this URL I am being served the login prompt for my router. What could be causing that, and does it indicate where I've gone wrong?
I'm working with:
ReadyNAS Duo
Netcomm N300 (NB304N) router
OSX
3 Replies
- Well, the problem is with the port forwarding. Did you try turning off remote management in the router?
Also, did you try this test over the internet or from your local LAN? - Just tried accessing my share/HTML file over the internet again 48hrs later and it's all working. Inexplicable, as I haven't changed anything since I was attempting to set this up the other day and apparently failing.
Thanks for your response Stephen. I hadn't changed any "remote management" setting that I'm aware of, but yes, I am using a separate internet connection (my mobile data connection) to test external internet access to the NAS share. The other night, as described, I was being served my router login (which was slightly alarming from a security point of view?!) and it seemed I must have done something wrong, even though I'd been over and over the port forwarding process. Anyway, I tried the same thing tonight as a starting point and the browser pointed straight to my index.html file as it should.
so it seems I am now in business.
Can I feel reassured that I have not exposed my router login screen and home network to easier malicious access from the WAN than before I messed with the setup? - What you did should not have exposed your router login screen. Figuring out exactly why you saw it might be tricky at this point. Perhaps the router screen was accessible before you did the port forwarding, and the browser had it cached???
Though of course any port forwarding carries some security risk. For instance, if there is a bug in the apache web server in the Duo, it is possible that someone outside could exploit it to gain access to the NAS and from there potentially other devices on your home network.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
