NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Readynas Ultra 2 cannot be accessed
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 ...
Stephen
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?
Rumpole wrote:
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?
Are you running Windows 10 in the PC?
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.....
Rumpole wrote:
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 ).
Rumpole wrote:
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).
Rumpole wrote:
Any other ideas, I’m hoping not to have to rebuild.....
You could try paid support (my.netgear.com).
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
