I have used this for some years as a dedicated music server for squeezebox. Two 1GB discs. Never had any probs. From memory I had it configured with dedicated IP address 192.168.1.64 which is within range of my BT Hub which acts as DNS. I am not aware of any changes having been made to this unit but it is on auto updates (I suspect there haven’t been any for some time). Suddenly it disappeared from network. All other devices and network fine. Lights on front all look normal (blue power, 2 solid led green). Using Raidar v 6.4.0 on windows 7 pc I can see device as being ‘healthy’, firmware 4.2.31. See screenshots. Nothing happens when try to access or setup readynas from raidar. I also cannot see from Windows explorer. Seems to have adopted IP 192.168.168.168. Reading other posts I changed my PC IP to 192.168.168.164 in hope this would get me on same subnet at least (I did not change hub settings - see screenshot). No connection. Can anyone suggest how to proceed. I suspect I just need to reset the IP address on readynas but cannot get in there. Data is mirrored from one disk to other (I hope but cannot check).
many thanks
Model: ReadyNAS RNDU2000|ReadyNAS Ultra 2 Chassis only
192.168.168.168 is the address it uses when DHCP fails. Try disconnecting the ultra from the network, and then connect it again. Then see if RAIDar reports a different address.
Another option is to directly connect the PC to the Ultra's LAN port (using your 192.168.168.164 address configuration), and see if you can access it. Use the IP address (https://192.168.168.168/admin), not the hostname.
thanks for reply. Tried that. Sadly same result. Also rebooted everything (Hub, pc, NAS) just to be sure. When connecting directly from pc to NAS via Ethernet tried both the original ip (192.168.1.64 fixed) and 192.168.168.168, used Explorer browser and also looked at pc network visible through windows browser. Neither would pick it up. Raidar still sees it with 192.168.168.168. Tried the second Ethernet port too as I think I had that configured to different IP but it wasn’t connected. Nothing. This is a bit like cracking walnuts. They’re a bugger to get in to but great when you work out how to do it. Any other bright ideas?
When connecting directly from pc to NAS via Ethernet tried both the original ip (192.168.1.64 fixed) and 192.168.168.168, used Explorer browser and also looked at pc network visible through windows browser. Neither would pick it up. Raidar still sees it with 192.168.168.168.
Did you also try https://192.168.168.168/admin in your web browser?
Have tried that and didn’t work. As it’s not acting as DNS (my hub is) would that work at all anyway? My networking knowledge is minimal, always had brighter people than me who could do all this.
I have not changed the IP address or the server address range in my hub that acts as DNS. This means the default IP of Readynas is outside the dns specified range. Do I need to change this to a range that includes 192.168.168.168, (eg192.168.168.160 to say 192.168.168.170?)
Any other ideas, I’m hoping not to have to rebuild.....
Have tried that and didn’t work. As it’s not acting as DNS (my hub is) would that work at all anyway?
With a direct connect to the PC (ethernet cable going directly from the ultra to the laptop - not through a router), there is no DNS or DHCP. RAIDar is reporting the IP address of the NAS as 192.168.168.168 - so whatever static address you might have set up there is not being applied. The PC is set up manually to be on the same subnet (192.168.168.164 in your case).
Resolving names to IP addresses in this case is problematic, so use the IP address - both in explorer - ( \\192.168.168.168) and in your browser( http://192.168.168.168/admin ).
Do I need to change this to a range that includes 192.168.168.168, (eg192.168.168.160 to say 192.168.168.170?)
No, since we are bypassing the hub using the direct connect procedure. If direct connect fails, reconfiguing the hub won't solve anything (and it risks breaking the rest of your network).
