NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Administrative page won't show up - ReadyNAS 314
Hi everyone, We work at a research station in a remote area where we don't have a lot of internet, so the PC we use to connect to the ReadyNAS 314 does not have an internet connection. We have a...
Dyllo wrote:
Thank you for taking some of your time to study this case, even though it was not very clear at first!
My pleasure, it was interesting to learn a little about your setup.
Dyllo wrote:
"Do you know what LAN address your router is using?" On IPv4 it is set to "Using DHCP" and Router has an IP of 192.168.1.1.
If you are connecting some PCs to both networks simultaneously, you could try setting the LAN IP address range to 10.0.0.x. That might get more consistent behavior when WiFi is turned on.
The whole certificate thing can be fixed. I now log into my ReadyNAS 516 using HTTPS and I'm using Chrome and it works great!!! No more anoying messages.
I have had access problems in th epast with my older ReadyNAS and issues with Chrome. So you want to try IE or Firefox and see if you can log in that way.
To fix the certificate issue and log in using https, just follow these directions. Hope it helps you and others.
Let's keep the cert discussion for later, it's not relevant to the problem at hand.
Can you post the IP addresses for both the PC and the NAS? Note that addresses in the ranges below are safe to disclose (they are not routable over the internet).
- 10.0.0.0/8: 10.0.0.0 -- 10.255.255.255
- 169.254.0.0/16: 169.254.0.0 -- 169.254.255.255
- 172.16.0.0/12: 172.16.0.0 -- 172.31.255.255
- 192.168.0.0/16: 192.168.0.0 – 192.168.255.255
The 169 address (which I think I can see a piece of in your screenshot) generally means that the NAS is unable to get an IP address from the router.
Your firmware is extremely old, which does get in the way of troubleshooting this. Newer firmware would have let you download the logs from RAIDar for instance.
Hi Stephen and JBDragon,
I also believe the certificate is not the main problem but I will get Google Chrome to that computer as well to not encounter this issue next time.
Here is the information, Stephen:
PC
Ehernet adapter Ethernet:
IPv4: 192.168.1.100
Subnet mask: 255.255.255.0
ReadyNAS
IP: 169:254:198:169
Also, what firmware are you exactly talking about? Are you talking about the OS? I think I'll connect this computer to the internet tonight anyway to have it all upgraded! (Thanks for letting me know it was old.)
Finally, the Wi-Fi card was disabled so I am going to set it back on and try to make a lan network for the ReadyNAS 314 and the PC.Best regards,
Dyllo
Ok, so the problem is that the NAS isn't finding a dhcp server. Does your router have dhcp enabled, or are you using static IP addresses?
You can try doing a direct connect procedure
-connecting NAS ethernet directly to the PC
-setting the PC IP address to 169.254.198.100, gateway to 169.254.198.1, subnet mask to 255.255.255.0
-then try accessing https://169.254.198.100/admin
You should get a login prompt (after the cert exception).
Dyllo wrote:
Also, what firmware are you exactly talking about? Are you talking about the OS? I think I'll connect this computer to the internet tonight anyway to have it all upgraded! (Thanks for letting me know it was old.)
The NAS. Your RAIDar screen shot shows it is running 6.1.4, the current firmware is 6.5.1. There are a lot of changes - if you don't have a backup of the NAS you should definitely make one before you upgrade.
Hi Stephen,
NOTE: When I type ipconfig in cmd (running as administrator) a lot of media are disconnected. For the moment I can't even connect to the Wi-Fi network. I'll try to figure this out as well, but I found it was maybe interesting to mention.
The DHCP of the router are enabled but for the Ethernet connection (->IPv4) we use a static IP address to connect to a receiver (from which we receive some accoustic data).
After connecting the NAS and PC directly, I have changed the IP of the PC to 169.254.198.100, gateway to 169.254.198.1 and subnet mask to 255.255.255.0 but as I try to connect to https://169.254.198.100/admin an error message tells me I can't reach this page. Am I doing something wrong? Should I change the IP of the Wi-Fi, or as I was doing, the Ethernet one?
Please forgive my ignorance, as I am not really at ease with network managing.
Also, in regards of the NAS firmware, it never been used so it is totally data free. Should I still do a backup or I suppose it was just to backup any existing data in case something went wrong?
Thanks in advance,
Dyllo
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
