NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Cannot connect to frontview
I can't seem to get any connection to the frontview of my readyNas Pro 4.
I can (read: could) connect to it via SSH, and RAIDar shows my NAS with a lot of fine green dots, as well as the IP address.
But, when I try to connect to the IP address in either Chrome or Firefox, I get the following message:
I just tried to perform a OS re-install via the boot menu, but that didn't give me anything. Other than removing the possibility for accessing the NAS via ssh :/
RAIDar tells me that I'm running with the latest firmware, 4.2.26
Any ideas of what I can do to access my NAS via frontview? :)
I can (read: could) connect to it via SSH, and RAIDar shows my NAS with a lot of fine green dots, as well as the IP address.
But, when I try to connect to the IP address in either Chrome or Firefox, I get the following message:
(And similar in Firefox)
Oops! Google Chrome could not connect to 192.168.40.78
Try reloading: 192.168.40.78
I just tried to perform a OS re-install via the boot menu, but that didn't give me anything. Other than removing the possibility for accessing the NAS via ssh :/
RAIDar tells me that I'm running with the latest firmware, 4.2.26
Any ideas of what I can do to access my NAS via frontview? :)
8 Replies
Replies have been turned off for this discussion
- What is the IP address and subnet mask of the PC?
- The IP is 192.186.40.10
Subnet I can't remember, but will check back when I get home from job :) - I am thinking there's a typo. Did you mean 192.168.40.10?
- Yes, sry :) It was a typo :)
Subnet is 255.255.255.0
Default gateway is manually set to 192.168.40.1 - Ok. That confirms that the IP addresses are all in the same address space. So that is not the problem.
What firmware are you running? - If you can SSH in, what is the output of
# tail -n 20 /var/log/frontview/error.log - RAIDar says 4.2.26 :)
I can't do SSH anymore - Some files that the apache conf for Photos II depended on were missing which broke apache and hence Frontview.
Installing the Photos II add-on over the top of itself and triggering an OS extraction (but not reset of config) using a flag file appears to have fixed the problem.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
