NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
TNIS79
May 08, 2013Aspirant
ReadyCloud won't discover new ReadyNAS 102
Hello,
I got a new ReadyNAS 102 2-Bay, Diskless RN10200 out of the box yesterday (and put in a third party HDD). So far everything seems is working fine except I am having problems with ReadyCloud.
I am running the newest firmware 6.0.4
Readycloud is refusing to discover the ReadyNAS. When I am going through the setup process and I try to discover the device, it prompts me to press the Backup or OK button on the front of the ReadyNAS. However, when I do this, it fails and tells me to try again. If I take no action, after three minutes it fails and tells me I did not press the button within three minutes and need to try again. When I do press the Backup button, it fails immediately and gives this same message (even if it's still less than three minutes).
I've tried pressing the Backup button once, holding it for 15 seconds, holding it before I click discover, etc. I have rebooted my computer and also rebooted and unplugged the ReadyNAS and tried again with the exact same results. I tried again throughout the day in case it was some kind of problem with the Readycloud service itself that might have later been corrected, but I continuously get the same result.
Obviously it won't allow me do anything else with ReadyCloud, because it says I don't have a registered device because it won't let me discover it.
So far I have not seen anyone else raise this specific issue.
I believe this might be a problem with ReadyCloud more than a problem with the ReadyNAS hardware itself. Everything on the ReadyNAS remains lit and doesn't seem to have an issue on the device itself.
Does the browser I'm using matter at all? Is there going to be a new firmware update that corrects this issue?
Please help.
31 Replies
Replies have been turned off for this discussion
- StephenBGuru - Experienced UserIt does no harm to enable IPv6 on the NAS, and see if that changes the symptoms.
- _shawAspirantThanks both. I'll give it a go.
- _shawAspirantI have enabled IPv6 but I'm not sure it's fully supported by my router. No IP6 settings to play with.
No noticeable change. - krazydavAspirantIPv6 is disabled on my router. When disabled on the nas the front panel of the nas displayed “cannot connect discovery server.” I still had normal access to the shares. Reset of the router, NAS and attempts at rediscovery using readycloud.netgear.com were unsuccessful. Re enabling it with DHCP enabled for some reason seemed to get it back online.
Very strange.
I also had issues with readycloud, though likely user error, when using static IP. I had access to the shares as usual with the exception of no readycloud and the same front panel display as above. Because things are working now I have stopped button mashing and have not tried reproducing that issue. - _shawAspirantEverything else is working fine, its just a minor annoyance. It looks like my issue is not that common and possibly an anomaly with the ReadyCloud service database - which I can't do much about anyway. When I have time, I'll delete my ReadyCloud account backup everything from the NAS. Factory reset and create a new account.
Thanks all for your help. - _shawAspirantHow peculiar. Switched off the static IP (where it was in a reserved range) and set it to DHCP. A reboot, new ip and suddenly ReadyCloud works! I'll reverse the process and see if that kills it.
- _shawAspirantBack to a static IP4 address. Reboot. Now ReadyCloud remembers I have a device but reckons its offline. Go to the admin page, cloud tab and it can't find the service.
There is something wrong if ReadyCloud can't cope with DHCP off. - krazydavAspirantYep, sounds familiar. I also found that with IPv4 set DHCP and IPv6 off I lost Readycloud.
- _shawAspirantProblem solved - courtesy of some very helpful forum folk.
If you are going to go for a static IP remember to set up the DNS!
Felt a bit foolish! - krazydavAspirantAwesome. After reading some of the inputs I clearly had IPv4 static set up incorrectly. I have no need for static IP so will not monkey with it anymore. I will however check the IPv6 issue again when I get some time.
Sent from my SM-T320 using Tapatalk
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!