Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Re: Getting it up and running
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2015-01-27
10:44 AM
2015-01-27
10:44 AM
Getting it up and running
Hi all,
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 ?
Thanks in advance.
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 ?
Thanks in advance.
Message 1 of 19
Labels:
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2015-01-27
11:04 AM
2015-01-27
11:04 AM
Re: Getting it up and running
What is the current firmware of your new RN102?
Access the web-GUI by typing https://NAS_IP_Address/admin at the address bar then press Enter.
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
You could also access the shares remotely via HTTP/S by enabling HTTP/S access on each share. Check this link: http://kb.netgear.com/app/answers/detai ... /related/1
Access the web-GUI by typing https://NAS_IP_Address/admin at the address bar then press Enter.
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
You could also access the shares remotely via HTTP/S by enabling HTTP/S access on each share. Check this link: http://kb.netgear.com/app/answers/detai ... /related/1
Message 2 of 19
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2015-01-27
11:57 AM
2015-01-27
11:57 AM
Re: Getting it up and running
Ixa wrote: What is the current firmware of your new RN102?
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 ?
SCREENSHOTS LOCAL ACCESS
SCREENSHOTS READYCLOUD
Message 3 of 19
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2015-01-27
12:21 PM
2015-01-27
12:21 PM
Re: Getting it up and running
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:
viewtopic.php?f=7&t=79291&p=446613&hilit=Apache#p446613
viewtopic.php?f=7&t=79412
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: 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.
viewtopic.php?f=7&t=79291&p=446613&hilit=Apache#p446613
viewtopic.php?f=7&t=79412
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: 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.
Message 4 of 19
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2015-01-27
12:22 PM
2015-01-27
12:22 PM
Re: Getting it up and running
Ok, the complete interface seems to be pretty completely f_ucked up now.
Message 5 of 19
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2015-01-27
12:24 PM
2015-01-27
12:24 PM
Re: Getting it up and running
Ixa wrote: 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 ?
Message 6 of 19
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2015-01-27
12:26 PM
2015-01-27
12:26 PM
Re: Getting it up and running
You may go ahead and perform a factory reset on your NAS then update the FW to v6.2.3.
Message 7 of 19
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2015-01-27
12:36 PM
2015-01-27
12:36 PM
Re: Getting it up and running
Ixa wrote: You may go ahead and perform a factory reset on your NAS then update the FW to v6.2.3.
LOL, does your post confirm that my system is officially F_ucked up now 🙂
Oh man, I just got this NAS two days ago, why is this happening to me...
Just to be sure, is this the correct procedure to restore factory defaults:
Message 8 of 19
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2015-01-27
12:54 PM
2015-01-27
12:54 PM
Re: Getting it up and running
You could follow the procedure you have posted regarding factory reset 🙂
Message 9 of 19
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2015-01-27
01:09 PM
2015-01-27
01:09 PM
Re: Getting it up and running
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
Lets move on...
. 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
Lets move on...
Message 10 of 19
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2015-01-27
01:51 PM
2015-01-27
01:51 PM
Re: Getting it up and running
OK, so far so good.
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 ?
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 ?
Message 11 of 19
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2015-01-27
02:09 PM
2015-01-27
02:09 PM
Re: Getting it up and running
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:
Message 12 of 19
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2015-01-27
02:26 PM
2015-01-27
02:26 PM
Re: Getting it up and running
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.
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.
Message 13 of 19
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2015-01-27
02:29 PM
2015-01-27
02:29 PM
Re: Getting it up and running
OK...
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.
Sorry but this experience was a serious downer 😞
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.
Sorry but this experience was a serious downer 😞
Message 14 of 19
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2015-01-27
03:37 PM
2015-01-27
03:37 PM
Re: Getting it up and running
The app uninstallation issue only affected recent firmware.
It is fixed in 6.2.3 beta and this has been confirmed internally and by external testers.
It is fixed in 6.2.3 beta and this has been confirmed internally and by external testers.
Message 15 of 19
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2015-01-28
02:29 AM
2015-01-28
02:29 AM
Re: Getting it up and running
Ok thanks for explaining mdgm.
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 ?
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 ?
Message 16 of 19
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2015-01-28
02:50 AM
2015-01-28
02:50 AM
Re: Getting it up and running
Possibly your router's I.P.
Possibly the ones for your ISP
Possibly one from another party.
Possibly the ones for your ISP
Possibly one from another party.
Message 17 of 19
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2015-01-28
04:01 AM
2015-01-28
04:01 AM
Re: Getting it up and running
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.
But you could use 8.8.8.8 - which is google's open DNS server. (8.8.4.4 is their second open server). https://developers.google.com/speed/pub ... docs/using
I suggest putting a new gigabit router on your tech shopping list btw. You'll get better performance, plus some new features.
But you could use 8.8.8.8 - which is google's open DNS server. (8.8.4.4 is their second open server). https://developers.google.com/speed/pub ... docs/using
I suggest putting a new gigabit router on your tech shopping list btw. You'll get better performance, plus some new features.
Message 18 of 19
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2015-01-28
07:02 AM
2015-01-28
07:02 AM
Re: Getting it up and running
OK, got it up and running now:
- static IP
- used DNS servers from ISP
NAS is accessible directly, through readycloud and via https from outside.
Next challenge is to get a dynamic DNS service running, gonna look into that next.
Thanks all 🙂
- static IP
- used DNS servers from ISP
NAS is accessible directly, through readycloud and via https from outside.
Next challenge is to get a dynamic DNS service running, gonna look into that next.
Thanks all 🙂
Message 19 of 19