NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
bcraigie
Aug 20, 2011Aspirant
Web interface stops responding after a while
I have a ReadyNas Duo Name: RAIDiator Version: 4.1.7 Date: Sat Nov 6 00:09:53 2010 (actually, I have two, at different locations, on different networks). I have noticed that ...
NAS_t
Oct 05, 2011Aspirant
@dazman,
IMHO, Virgin is incompetent if they think turning off firewall is a solution to speed problems. However, assuming that your router implements NAT (it has to, so you can have your NAS and a PC or three on your LAN), it's unlikely that external attacks could have reached the Duo. The Duo's IP address would not be routable from your router's WAN interface. All of which to say that I don't think external internet traffic could be the root cause of your problem. Unless you have configured port forwarding to permit WAN access to the Duo's IP address.
(parenthetically, you should run a ShieldsUp scan at grc.com to verify that your router is indeed blocking external connections).
If you see SIGTERM messages in the httpd log, that suggests some other other process on the Duo is deliberately causing the shutdown of the httpd process. I don't know enough about the inner workings of ReadyNAS to know what logs you should look at. Perhaps Yoh-dah or Chirpa will chime in with a suggestion.
Meanwhile, you could also use the shell command provided earlier in this thread to restart the httpd process. That's what I did. I wrote a little script that would send the restart command off to the Duo whenever I found the web interface not responding. To do so, you'll have to enable ssh access with one of the ReadyNAS add-ons.
Good luck,
Dave
IMHO, Virgin is incompetent if they think turning off firewall is a solution to speed problems. However, assuming that your router implements NAT (it has to, so you can have your NAS and a PC or three on your LAN), it's unlikely that external attacks could have reached the Duo. The Duo's IP address would not be routable from your router's WAN interface. All of which to say that I don't think external internet traffic could be the root cause of your problem. Unless you have configured port forwarding to permit WAN access to the Duo's IP address.
(parenthetically, you should run a ShieldsUp scan at grc.com to verify that your router is indeed blocking external connections).
If you see SIGTERM messages in the httpd log, that suggests some other other process on the Duo is deliberately causing the shutdown of the httpd process. I don't know enough about the inner workings of ReadyNAS to know what logs you should look at. Perhaps Yoh-dah or Chirpa will chime in with a suggestion.
Meanwhile, you could also use the shell command provided earlier in this thread to restart the httpd process. That's what I did. I wrote a little script that would send the restart command off to the Duo whenever I found the web interface not responding. To do so, you'll have to enable ssh access with one of the ReadyNAS add-ons.
Good luck,
Dave
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!