NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
zackiv31
Jul 11, 2011Aspirant
DNS ( /etc/resolv.conf ) empty on restart
I just upgraded my Pro from 4.2.15 -> 4.2.17. On 4.2.15 I had installed Crashplan and ppp VPN client on it... (I don't know if this is related at all).... CrashPlan is running just fine with th...
berkut1
Jul 04, 2012Tutor
I recently upgraded my ReadyNAS Pro Pioneer Edition [X-RAID2] firmware from 4.2.15 to 4.2.21.
The upgrade for all appearances went without a hitch.
However when I attempted to use my ReadyNAS Remote application I found that the system had lost its DNS settings.
My NAS uses static IP and DNS settings. When I looked under global settings, I found these fields to be both greyed out and greyed out (ie: not editable).
The only way I was able to recover was to:
1) Switch the network to DHCP and Reboot
2) Login via the DHCP address.
3) Switch back to static, changing the static IP back to its original value and then reboot again.
At this point I needed to reboot the Windows machine that was running Remote to reestablish a connection to the server and on the NAS I removed and added back the allowed user. I am not sure If this last step was necessary but I did get the ReadyNAS remote connection working again so its all good.
The upgrade for all appearances went without a hitch.
However when I attempted to use my ReadyNAS Remote application I found that the system had lost its DNS settings.
My NAS uses static IP and DNS settings. When I looked under global settings, I found these fields to be both greyed out and greyed out (ie: not editable).
The only way I was able to recover was to:
1) Switch the network to DHCP and Reboot
2) Login via the DHCP address.
3) Switch back to static, changing the static IP back to its original value and then reboot again.
At this point I needed to reboot the Windows machine that was running Remote to reestablish a connection to the server and on the NAS I removed and added back the allowed user. I am not sure If this last step was necessary but I did get the ReadyNAS remote connection working again so its all good.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!