NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Cannot connect to ReadyNAS with windows 10
I have some time ago updated to windows 10 hoping that I had chosen a late update where most bugs had been identified and solved. However, I cannot connect to my ReadyNAS Duo. I can see the NAS via ...
kirsten_d wrote:
RAIDar shows 10.0.0.8 for the NAS.
Router-connected wireless devices all have IP addresses starting with 172.16.0.X - so that must be the area that the router deals in
If your router uses 172.16.0.x addresses, then you can't ping 10.0.0.8.
Did you configure the NAS to use a static address? If not, can you give us some more info on how your NAS is connected to the router (giving the manufacturer/model for any intermediate devices)
There are a couple of things you can try:
(a) directly connect the PC ethernet to the NAS (bypassing the router). Temporarily configure the PC to use 10.0.0.7, gateway 10.0.0.1, subnet mask 255.255.255.0. Then enter https://10.0.0.8/admin in your browser, and reset the NAS network configuration to use DHCP. Reconnect the system as before, and change the PC back to DHCP.
(b) set the router range to use 10.0.0.x, and use address reservation (a usual router feature) to reserve 10.0.0.8 for the NAS. That should let you connect, After that make sure the NAS is configured to use DHCP.
(c) Do an OS reinstall from the front panel of the NAS. That resets the NAS to use DHCP, and also reset the NAS admin password to netgear1. It shouldn't change any other settings or delete data. OS reinstall is described on pages 15-16 here: http://www.downloads.netgear.com/files/GDC/RND2110/Duov1_NV+v1_HW_en_06Dec11.pdf Be careful not to do a factory reset by mistake, that will delete your data.
I am using Chrome by default.
I am not able to ping the Nas from cmd prompt.
Only signs of the Nas being alive is the Raidar search for the Nas: Raidar tells me that the Nas is healthy and running with two disc - as it should be.
However, when I try to browse the Nas or enter admin page from Raidar - I get a message that I can't get access - I should check network settings.
I think it is strange that Raidar is able to contact the Nas to get health status but I am not able to ping it?!
Thanks for your time and suggestions.
I am not able to ping the Nas from cmd prompt.
Only signs of the Nas being alive is the Raidar search for the Nas: Raidar tells me that the Nas is healthy and running with two disc - as it should be.
However, when I try to browse the Nas or enter admin page from Raidar - I get a message that I can't get access - I should check network settings.
I think it is strange that Raidar is able to contact the Nas to get health status but I am not able to ping it?!
Thanks for your time and suggestions.
kirsten_d wrote:
I think it is strange that Raidar is able to contact the Nas to get health status but I am not able to ping it?!
RAIDar has a special "broadcast discovery" protocol that allows it to reach the NAS even if the network interface is mis-configured.
Can you let us know what IP address RAIDar shows for the NAS? Also, let us know the address range used in your router (or the IP address of your PC).
Private IP addresses (not internet accessible) are safe to post. Private address are
- 10.0.0.0 – 10.255.255.255
- 172.16.0.0 – 172.31.255.255
- 192.168.0.0 – 192.168.255.255
RAIDar shows 10.0.0.8 for the NAS. For the router the NAS device is registered with name "unknow" but I can recognize the NAS from its MAC address. Do you think the that the NAS name "unknown" on the router settings has any impact in this relation?
Router-connected wireless devices all have IP addresses starting with 172.16.0.X - so that must be the area that the router deals in
(IP subnet mask: 255.255.255.0 if that can be of any information).
kirsten_d wrote:
RAIDar shows 10.0.0.8 for the NAS.
Router-connected wireless devices all have IP addresses starting with 172.16.0.X - so that must be the area that the router deals in
If your router uses 172.16.0.x addresses, then you can't ping 10.0.0.8.
Did you configure the NAS to use a static address? If not, can you give us some more info on how your NAS is connected to the router (giving the manufacturer/model for any intermediate devices)
There are a couple of things you can try:
(a) directly connect the PC ethernet to the NAS (bypassing the router). Temporarily configure the PC to use 10.0.0.7, gateway 10.0.0.1, subnet mask 255.255.255.0. Then enter https://10.0.0.8/admin in your browser, and reset the NAS network configuration to use DHCP. Reconnect the system as before, and change the PC back to DHCP.
(b) set the router range to use 10.0.0.x, and use address reservation (a usual router feature) to reserve 10.0.0.8 for the NAS. That should let you connect, After that make sure the NAS is configured to use DHCP.
(c) Do an OS reinstall from the front panel of the NAS. That resets the NAS to use DHCP, and also reset the NAS admin password to netgear1. It shouldn't change any other settings or delete data. OS reinstall is described on pages 15-16 here: http://www.downloads.netgear.com/files/GDC/RND2110/Duov1_NV+v1_HW_en_06Dec11.pdf Be careful not to do a factory reset by mistake, that will delete your data.
Thanks - Stephen. sounds like I'm going to spend the evening on the attic with the NAS to get the working. Thanks - I'll try this out and get back :)
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
