Orbi WiFi 7 RBE973
Reply

RAIDar does not show ReadyNAS nv+ v2

rsharma314
Follower

RAIDar does not show ReadyNAS nv+ v2

Hello all -

 

I'm having an issue with my ReadyNAS not showing up on my network.  These are the things that I have checked:

 

1- The PC and the NAS are on the same subnet - my router's address is 192.168.168.1.  My router is wired in the router switch, and my PC is wirelessly connected to the router.  The IP Address of my NAS is 192.168.168.168, and the IP Address of my PC is 192.168.168.151

2- I did a OS Reinstall on the NAS , and now gives me an IP Address of 192.168.168.168 on the front console.  When I look at my router, I can see that it has successfully granted the 192.168.168.168 IP Address - the router also shows that IP Address as active.  However, when I ping 192.168.168.168, I loose all packets.

3- Rebooted my Router, PC and NAS several times.

4- i use three drives on the NAS (on Bay 2, 3, and 4).  When i remove any of the three drives and reboot, it shows me the same IP Address on the front console, but doesn't show up on RAIDar or when I ping it.  When I insert the drive, it goes through and rebuilds it looks like the data on the drives are okay.

 

I don't remember changing anything that would have caused this, and have already spent 10-12 hours troubleshooting this.  Anyone know what might be causing this, or anything else that I can check?

 

Thanks in advance.

Message 1 of 3
BrianL2
NETGEAR Employee Retired

Re: RAIDar does not show ReadyNAS nv+ v2

Hi rsharma314,

 

Try a direct connection using your PC and use a static IP address 192.168.168.167 with 255.255.255.0 as its subnet mask. If this works, it means that using 192.168.168.x as your network subnet is not advisable and consider changing it to something like 192.168.1.x or any class C IP address range.

 

Hope this helps!

 

 

Kind regards,

 

BrianL
NETGEAR Community Team

 

Message 2 of 3
StephenB
Guru

Re: RAIDar does not show ReadyNAS nv+ v2

192.168.168.168 is the address the NAS uses when DHCP fails.  In your case, your subnet is 192.168.168.x, so we really can't tell if DHCP has failed, or if the router has actually given out that address.

 

If you don't use static addresses, it might be worth resetting the router to use a different range.  Try Brian's direct connect test first.

Message 3 of 3
Top Contributors
Discussion stats
  • 2 replies
  • 2307 views
  • 0 kudos
  • 3 in conversation
Announcements