This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
RN102 shows up as network drive but can't access admin
I'm staying at a place temporarily and setting up my ReadyNAS 102 as well as some other devices, and I'm having some issues connecting to the NAS. I don't have admin access to the router.
-On a laptop connected to the same network, the NAS shows up as a "computer" when viewing the network. I can access the files on the NAS just fine this way.
-When pinging the name of the NAS it pings a IPV6 address. When pinging with the -4 suffix it doesn't succeed in resolving the name (seems like the NAS only has IPV6, not IPV4)
-On ReadyCloud the NAS is listed as offline
-When discovering devices on ReadyCloud it fails to find any devices
-I can't seem to access the admin page, when putting in the IPV6 address in a browser (with or without brackets), it searches the term instead. I don't have a ipv4 address to navigate to in the browser.
-I know that DLNA is enabled, but neither the computer nor a PS4 on the network seems to detect the DLNA.
Any suggestions for how to access the admin page, find it through readycloud or access the DLNA? Thank you.
Re: RN102 shows up as network drive but can't access admin
Did you have a static IP address assigned to the NAS that may now be outside the subnet of the router in your new location? RAIDar is the best way to find that out, and an OS re-install can solve it (it resets the NAS to use DHCP). Just be sure to select OS Re-install, not Factory Default.
Re: RN102 shows up as network drive but can't access admin
Did you have a static IP address assigned to the NAS that may now be outside the subnet of the router in your new location? RAIDar is the best way to find that out, and an OS re-install can solve it (it resets the NAS to use DHCP). Just be sure to select OS Re-install, not Factory Default.
Re: RN102 shows up as network drive but can't access admin
Thanks guys, this was exactly the problem. I used RAIDar which showed that the device was on a static IPv4 from my previous network. Doing the OS reinstall fixed it and I can now access and set it up properly for this place.
Thanks guys, this was exactly the problem. I used RAIDar which showed that the device was on a static IPv4 from my previous network. Doing the OS reinstall fixed it and I can now access and set it up properly for this place.
Great. Reserving the IP address in the router (instead of assigning a static IP address) is one way to prevent this from happening again.
