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
- NhellieVirtuosoShaw,
try forwarding port 6300 to your NAS' IP.. - _shawAspirantHi. Not quite sure what you mean. I have no port filtering on my switch between Windows or Macintosh PC's and my ReadyNAS.
- _shawAspirantI usually use port forwarding on a firewall. Ah! Is there some incoming port filtering set up on the ReadyNAS?
- NhellieVirtuosoWhat I mean is forward port 6300 to the IP of the NAS.
- StephenBGuru - Experienced User
that is, forward port 6300 in the firewall to the NAS.Nhellie wrote: What I mean is forward port 6300 to the IP of the NAS. - _shawAspirantHi - thanks for clarifying. To be clear. I have my NAS set up on a typical domestic arrangement with a small (netgear) switch between several wired computers. This is unmanaged with no firewalling. The gateway to internet services is a small (netgear) DSL router which is using NAT to bridge between a public IP and my private network which I have set up (since installing this NAS) to have no firewall rules set and no port filtering. I have created a service "ReadyNAS on TCP Port 6300" and opened it explicitly for the NAS IP Incoming and Outcoming and restarted everything.
From a PC on the same segment. Admin webpage loads fine - go to cloud tab, switch on readycloud circling timer (about 20 seconds) then it reports "Services Offline". Back open a tab on the browser (in this case chromium portable) login to my account at readycloud.netgear.com which reports I have no registered devices (because I deleted my RN102 when it was not connecting) now click on discover. Nothing. Press the backup button on the NAS for 5 seconds. Nothing. Enter my serial number in the form shown on the Admin Page. Nothing.
Port scan on TCP 6300 shows its open.
My suspicion is that the ReadyCloud database which links all these things is locking me out for some reason. Its a little irritating. - krazydavAspirantIs IPv6 enabled?
- _shawAspirantNot on my home network. Its NATed over to an IPv4 192.168.xx.xx range.
I have my readyNAS with a static IP in a small reserved group of IP's, the rest are all served by a DHCP server on the router.
This worked fine with 6.1.
Is IPv6 a requirement of 6.2.2? - StephenBGuru - Experienced User
No._shaw wrote: Is IPv6 a requirement of 6.2.2? - krazydavAspirantI noticed that I seemed to have quite a few issues with readycloud when I disabled IPv6. I asked, but never received an answer from tech support about any relation. I verified the loss of Readycloud on mulitple occasions even with the beta FW/SW. I guess there is a chance I did something wrong, but as soon as I enabled it everything went back to normal.
Related Content
NETGEAR Academy

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