NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

Damien29's avatar
Damien29
Aspirant
Oct 10, 2016
Solved

"Something is preventing the ReadyNAS from connecting to the ReadyCLOUD server."

I have upgraded two of my ReadyNAS104 devices to 6.6.0 and can't get either of them to join to my MyNETGEAR account.

 

I have factory reset both of them, added the Google DNS addresses, turned off remote management on my firewall router (as that also uses port 443), and torn out most of my hair.

 

Is there something else that I could try?

 

RN104 4x3Tb

RN104 2x3Tb

RN102 2x2Tb

RNDv2 2x2Tb

NETGEAR ProSafe VPN Firewall FVS336G

  
  • One of your units has a bad disk.

    The ReadyCLOUD user must not share the same email address as a local user. Did you configure some local users to have the same email address?

10 Replies

Replies have been turned off for this discussion
  • mdgm-ntgr's avatar
    mdgm-ntgr
    NETGEAR Employee Retired

    ReadyCLOUD doesn't require port forwarding and if you do port forward it wouldn't be port 443.

     

    Do the 13-digit serial numbers show up correctly for these NAS units? Can you send in your logs (see the Sending Logs link in my sig)?

    • Damien29's avatar
      Damien29
      Aspirant

      Thanks for replying. I've sent through the logs by PM.

       

      One unit was bought new and registered on MyNETGEAR and the other was bought second hand and already registered to someone else.

       

      Looking at the logs, there are some messages that might be a clue:

       

      System: Local user account […] was renamed to […38a2] due to the conflict with added ReadyCLOUD user […].

      System: Local user account […] was renamed to […9d37] due to the conflict with added ReadyCLOUD user […].

      System: Local user account […] was renamed to […51b3] due to the conflict with added ReadyCLOUD user […].

      • mdgm-ntgr's avatar
        mdgm-ntgr
        NETGEAR Employee Retired

        One of your units has a bad disk.

        The ReadyCLOUD user must not share the same email address as a local user. Did you configure some local users to have the same email address?

  • Retired_Member's avatar
    Retired_Member

    it seems the name of your local user is the same as your old ReadyCLOUD account,once you registered ReadyCLOUD with migrated SSO account,ReadyOS will rename local user due to name conflict reason,I'm not sure why you are still unable to register ReadyCLOUD in 6.6 even you have already added Google DNS,have you tried to register other SSO account? 

    • Damien29's avatar
      Damien29
      Aspirant

      Thank you both - success!

       

      I created a new ReadyCLOUD account with a different email address to my MyNETGEAR account and was able to add both RN104s to it.

       

      Mind you, I'm now the proud owner of two "Single Sign On" MyNETGEAR accounts, one account - 12189303 - with all of my products registered to it (apart from the one that I bought secondhand), and one - 34214231 - brand new account...

       

      (In relation to the bad disk, I added a fourth 3TB disk to my RN104 about 20 hours ago. I've seen a couple of information messages about high reallocated sector count, but no warnings or errors so far. The RN104 is currently showing "Reshape data 54.46%". I was planning to wait another 20 hours until it completed 'reshaping' before deciding whether I'd bought a faulty disk. Should I give up now?)

      • mdgm-ntgr's avatar
        mdgm-ntgr
        NETGEAR Employee Retired

        What are the SMART stats for that disk?

NETGEAR Academy

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

Join Us!

ProSupport for Business

Comprehensive support plans for maximum network uptime and business peace of mind.

 

Learn More