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

Forum Discussion

emopausal's avatar
emopausal
Aspirant
Dec 16, 2019
Solved

RN102 Invisible on network after move

Heya,

 

Got this RN102 that's been a tank for years and has already suffered through several moves.

 

This move, when rebuilding my lan, I am unable to get the RN102 registered on the network.  The nas powers up just fine and all the lights are in the configuration for normal ops:  all front panel lights are blue/solid and the network light on the back is blinking (yellow) regularly as is the hub-connection indicator.

 

However, the device never appears on the network.  I can neither ping nor ssh into the nas.  I've switched out networking cables, and also have moved the device to several different hubs but the device remains autistic.  I fear this last move may have finally killed off his venerable device.  (All my other nas devices are working on the same hubs I've tried to (re)connect the RN102 on...)

 

So, worst case scenario afaik is that the nic went south.  My drives are config'd as RAID1 (mirror) so I'm not really worried about content retention except:

 

  • if I pull these drives to install in a new nas, is there anything netgear-proprietary that would prevent them from being successfully accessed and read on, say, a WD NAS?  Do I have to stay with a netgear nas b/c of some proprietary weirdness?
  • Can I attach the nas directly to a laptop to see if the device remains autistic?  If so, how?

That's about all I can think of... I think this nas has died and gone to nas heaven.  My concern now is recovering the data from one, or both, drives.

 

Thanks!

 

--mike


  • emopausal wrote:

     

    Machine A (10.245.95.166) can "see" the nas (10.245.95.110) but cannot access it.  As previously stated, all ports (read: protocols) on the nas are closed/inaccessible.  There's no firewalls involved; just something fecked on the device. 

     


    But your RAIDar screenshot says the NAS IP address is 192.168.1.10 which is not compatible with 10.245.95.x.  Where are you seeing the 10.245.95.110 address?

     

    That suggests that your old network was 192.168.1.x, and that you'd assigned the NAS a static address.  The most direct way to fix it is to change the router to use the 192.168.1.x address space temporarily, which would then allow you to access the NAS.

     

    You can also try doing an OS reinstall on the NAS - which will reset the NAS to use DHCP and also reset the admin password back to password.  It also turns off volume quota (which is on the settings wheel on the volume tab).

     

     

10 Replies

  • Just a quick follow-up:

    I connected the nas to my ubuntu 18 latop, setting the laptop IP to 192.168.1.10.  I'd read elsewhere here about static IPs which got me wondering if this nas was statically configured (The answer is: No...pretty sure...no... o/w the IP would be on the first subnet I created: 192.168.0.X.)

    Anyway, nmap can see the readyNas (192.168.1.110) but I can't load that IP up in a browser (timeout).  Port scan shows all 1000 ports are filtered.  Attempting to ssh fails.  Even ping fails - which is weird because, it's just ping, right?

     

    Leaning more and more towards some hardware failure in the nas...

     

    Thoughts?

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