Just got my first NAS, an RN102. But I'm a bit confused and ran into some troubles already, so that's why I'm here 🙂
First, why did I get a NAS: - I wanted to have my own alternative to dropbox. That's basically the main reason.
The first thing I ran into is this:
I would like to access the NAS from the outside world directly, so without using readycloud.netgear.com The NAS is behind a router so that would involve some port mapping. For this to work I would have to give the NAS a staic IP within my network
However when: - I assign a static IP to the NAS within the network (see screenshot below) - And log in to readycloud.netgear.com
I got the foloowing errors: - Device is offline, - No volumes or usb disks
Why does assigning a static IP within my network cause readycloud.netgear.com to malfunction ?
Since this an initial setup of your new RN102, you could start by doing a factory reset. You may want to contact Netgear Support for this and they would be glad to help you: http://support.netgear.com/general/contact/#tab-call
If you want to access the NAS from outside your network without using ReadyCloud, you could open port 443 on your existing router then point it to the local IP address of your NAS and take note of your WAN IP Address then access your NAS remotely by https://WAN_IP_Address/admin. Check this link: http://kb.netgear.com/app/answers/detail/a_id/23100
Note: From the link above, notice that there is a "Port 2" field wherein you could set an alternative port number for HTTPS
Access the web-GUI by typing https://NAS_IP_Address/admin at the address bar then press Enter. ...
Thank you for your reply.
I have updated to V 6.2.2
In the meantime I tried to get and set up owncloud to explore what that is about. - installed the app: webdav error - removed the app: connection to NAS on local network lost
Now I cannot connect to the nas when using : https://192.168.1.101/admin/ (see screenshots "local")
I can however log onto readycloud.netgear.com: screenshots "readycloud"
I tried rebooting the NAS (power button....blink...power button....shutdown.... powerbutton... reboot) To no avail...
What are my options now ? Should I do a factory reset ?
What I have found out about these forum links above is that the reason was Apache could not start because of sites-enabled which contained “.conf file” left by the App after its been uninstalled. To solve this, a telnet/SSH access to the NAS is needed and that “.conf file” should be removed then restart Apache and the web-GUI of the NAS will be accessible again.
Losing access to the web-GUI after uninstalling an App/s on FW v6.2.2 is a known issue. What you have just experienced is similar to these forum links: http://www.readynas.com/forum/viewtopic.php?f=7&t=79291&p=446613&hilit=Apache#p446613 http://www.readynas.com/forum/viewtopic.php?f=7&t=79412 http://www.readynas.com/forum/viewtopic.php?f=7&t=79412
What I have found out about these forum links above is that the reason was Apache could not start because of sites-enabled which contained “.conf file” left by the App after its been uninstalled. To solve this, a telnet/SSH access to the NAS is needed and that “.conf file” should be removed then restart Apache and the web-GUI of the NAS will be accessible again.
However, it is already corrected on Beta FW v6.2.3: http://www.readynas.com/forum/viewtopic.php?t=78866
Since this is just a new RN102, you may proceed on doing a factory reset and check if that would help.
Ok, Didn't see you reply before I posted my last screenshots.
So you would advise a factory reset and installing Beta FW v6.2.3 ?
Factory default . Initiates a short disk test that takes approximately 5 minutes. After the disk test, a 10-minute time-out period begins. WARNING: The factory default reboot process resets the storage system to factory settings, erases all data, resets all defaults, and reformats the disk to X-RAID2. - If you want to cancel the factory default process, power off the storage system before the 10-minute time-out ends. The system powers down safely without causing any data loss. - If you want to reset the system to factory default settings, do not power off your system. After the 10-minute time-out period, the factory default process begins. Tip: To start the factory default process immediately, press the Backup button during the 10-minute time-out period.
OK, factory reset works for now. I have access through http://readycloud.netgear.com
It works fine again. But I've gone through a whole lot of s_hit, installing it, wrecking it by installing/uninstalling an app, restoring factory defaults...
Now I'm back to zero.
I mean, this is not how a product you buy for a few $100 is supposed to work now is it ?
For me, RN102 is still a good choice of NAS.... I could say that all fixes should be included on the next firmware release. I have faith on the ReadyNAS engineering team about this :lol:
When you set a static I.P. you need to make sure things such as the DNS settings are set correctly. If they are not then things such as ReadyCloud won't work.
Personally I find it simplest to get the router to assign a static I.P. to the MAC address of the ethernet port in the NAS and leave the NAS configuration on the default setting to pickup an I.P. via DHCP from the router.
As for the app uninstallation issue that issue can be fixed quickly. It is already addressed in 6.2.3 beta, so a fixed system that is then updated to 6.2.3 beta can subsequently have apps uninstalled without running into this issue.
At this moment I'm afraid to install any apps, they might throw me back into the factory defaults again... Unless you can assure 6.2.3 beta resolves this.
This is not a noob piece of hardware, netgear should get its s_hit together and provide stable firmware before considering apps.
About the IP for the NAS. My router does not have the option to assign an IP based on a MAC-address. My WRT54GL is now running Linksys firmware and I would have to install DDWRT or Tomato to have that functionality.
So let's say I set a static IP on the NAS, what should I enter for DNS then ?
If you have a windows PC, open a command window ("cmd" in the windows search bar) and type "ipconfig /all". There will be a lot of information, but if you look through it you'll see the DNS server your PC is using. Generally its a good idea to use the same settings.
