NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RN314: Static IP-Adresses/Networ is not correctly work since installation/deinstallation of Software
Dear all, a couple of weeks ago I installed via the ReadyNAS-GUI "Monsta FTP" and "NZBGet". Since the packages were no covering my needs I deinstalled them on the same day. Since that time I can...
Just to clarify: The NAS has always used a static address. You installed the two apps, then uninstalled them - but didn't change the network configuration at all? And now it is misbehaving?
Have you checked if NTP is updating the time without problems? You can check this by downloading the log zip file, and looking in connman.log
One thing to check with static addresses is that the DNS servers is configured (easy to overlook) and that the DNS servers are still correct. But that doesn't explain ping failing. Is ping failing on the same network segment, or only on a different segment?
Assuming DNS is correctly configured, I guess you could try an OS reinstall. That will also change the admin password back to password, and turn off the volume quota settings on the volume settings wheel. A factory default would obviously fix it, but you'd have to rebuild the NAS and restore all the files.
Worli wrote:
(Of course I could leave it now on DHCP. But in the one of the segments - for good reasons - I do not run a DHCP-server.)
Not sure why that matters, unless the NAS is running on that segment. DHCP with address reservation should work just as well for the NAS (giving it a persistent IP address).
Hi StephenB,
again, thank you! I would like to add here that I run the same network config (static+on 2 segments) on my RN422.....
Here my answers:
Just to clarify: The NAS has always used a static address. YES, over a long time. You installed the two apps, then uninstalled them - but didn't change the network configuration at all? YES And now it is misbehaving? YES
Have you checked if NTP is updating the time without problems? You can check this by downloading the log zip file, and looking in connman.log Static IP: no update. DHCP: update ok. Also found out on the NAS-Startpage that the last Antivirus-update was done on Feb 9. (on Feb 10 I did the install/deinstall of SW). Also the Hotfix 1 came correctly yesterday after the change to DHCP....
One thing to check with static addresses is that the DNS servers is configured (easy to overlook) and that the DNS servers are still correct. YES, I am quite sure that DNS Servers are correct. Checked it ten times. Same as on all other devices/ReadyNAS-boxes. But that doesn't explain ping failing. is working with static addressIs ping failing on the same network segment, or only on a different segment? In lan 1 with static: WOL + access via Web-GUI + File-Share-Access is working. In lan "50" simply nothing is working. Even the LAN-Management tool shows "no ip address" on this active switch-port.
I already thought about an OS-reinstall. With a kind of weird feeling. Is the ~8TB of data really safe?. (I never an OS-reinstall...)
kind regards, Worli
Worli wrote:
In lan 1 with static: WOL + access via Web-GUI + File-Share-Access is working. In lan "50" simply nothing is working. Even the LAN-Management tool shows "no ip address" on this active switch-port.
Assuming LAN "50" is a different subnet: The only things in the NAS config I can think of that would cause these symptoms is a misconfigured subnet mask or gateway.
You might also want to enable ssh in the NAS, and see if it can ping anything on LAN 50 (outbound).
One more clarification - are you using both NICs on the RN314 (one for each subnet), or just one?
Worli wrote:
I already thought about an OS-reinstall. With a kind of weird feeling. Is the ~8TB of data really safe?. (I never an OS-reinstall...)
FWIW, I always recommend having a solid backup plan, since devices can always fail w/o warning.
But it is designed to be safe. Of course something can always go wrong, but I don't see any significant risk here. Risk would be higher if there were file system issues. You do need to be careful not to do a factory default.
Instructions are on page 74-75 here: https://www.downloads.netgear.com/files/GDC/READYNAS-100/ReadyNAS_%20OS6_Desktop_HM_EN.pdf
Hi StephenB, yes, 50 is a subnet were I do have my servers running, promoted to the web.
The box is still on dhcp and I connected via ssh. I could ping any ip in the same subnet but nothing outside.Neither to subnet 50 nor to the internet (I did the tests via the ip address and not via hostname.). From subnet 1 to 50 it is open. From 50 to 1 it is forbidden via Secure Gateway definition. So also via dhcp it is somehow "catched" in the subnet.
On any other of my about 40 devices (most of them are dhcp, some static) everything is working perfectly.
Since now I also cannot longer change the box to static. When I tray to save the static-config (via GUI) I get "Error setting network properties". Strange...
Kind regards, Worli
Again, are you connecting just one NIC in the RN314, or are you connecting one to LAN 1 and the other to Lan 50???
Worli wrote:
The box is still on dhcp and I connected via ssh. I could ping any ip in the same subnet but nothing outside.Neither to subnet 50 nor to the internet
That's different from what you said before (when DHCP was reaching the internet). Of course many internet servers won't respond to ping. 8.8.8.8 and 1.1.1.1 will, so they are both good options for testing.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
