NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
ReadyNAS 104 [6.8.0] Communication error to NTP & Updates
Hello ReadyNAS 104 [firmware 6.8.0] I can access the device on 192.168.1.10 just fine as ADMIN. I can see all the SHARES and drill down through them. -- When I press "Check for Updates" I get "O...
I suspect that while the DHCP address range included .10, your son did one other thing you didn't realize -- changed the NAS to use a static address that was previously assigned by DHCP. Step one is to enable DHCP on the NAS. Then, if you want the NAS IP address to remain the same (and you really should), reserve the address in the router instead of setting the NAS to use a static one.
If you have no choice other than to use a static address, then leave the second LAN port set to DHCP, and you can always change the cable over to re-gain access if something happens (like changing the router to one that uses a different address range), you can swap the cable and re-gain access (at a new DHCP address you can find on the display or in RAIDar)..
Does the AT&T router have an IPv4 WAN address?
Yes 192.168.1.254
If it does, you might try disabling ipv6 on the NAS, and rebooting it.
How do I do that?
IPV6 is disabled on the AT&T Router. Is that what you meant to type?
Thanks for sticking with me.. Jim
If this helps - here is a LOG error that I got, further illustrating the NAS -> Internet communication problem
| Fri Dec 23 2022 10:07:40 |
| System: Alert message failed to send. |
| Fri Dec 23 2022 10:07:40 |
System: The system is rebooting.
jaholstein wrote:Does the AT&T router have an IPv4 WAN address?
That would be the AT&T router's IPv4 LAN address - only reachable on your home network. Still, if IPv6 is disabled on the router, it is using IPv4 over the internet.
jaholstein wrote:
If it does, you might try disabling ipv6 on the NAS, and rebooting it.
How do I do that?
IPV6 is disabled on the AT&T Router. Is that what you meant to type?
I meant the NAS.
Log into the admin web ui for the NAS, and go to the networks page. Click on the settings wheel for eth0 (if it is gray, then click on the settings wheel for eth1).
You should now see a pop-up window. Select the ipv6 tab, and you will see a pull-down that includes "disable".
Next select the ipv4 tab, and make sure it says "using DHCP" - not static.
Then reboot.
jaholstein wrote:
the network shows 2 cards, but BOND 0
When I change from static to DHCP I get a warning [screenshot attached]
Please advise if this is normal and I should say OKAY.
You aren't disabling the network interface, so this is ok.
There isn't much benefit in bonding (Link aggregation) - I suggest that you also disable that. Start by just removing the second ethernet connection (assuming it is still connected). The you can change the configuration. We can talk about how later on.
Note that earlier you said the AT&T router LAN address was 192.168.1.254. Your NAS is configured to 192.168.1.1. That could be the source of your problem. After you switch to DHCP, take a look at the router address again, and see if it changes.
I suspect that while the DHCP address range included .10, your son did one other thing you didn't realize -- changed the NAS to use a static address that was previously assigned by DHCP. Step one is to enable DHCP on the NAS. Then, if you want the NAS IP address to remain the same (and you really should), reserve the address in the router instead of setting the NAS to use a static one.
If you have no choice other than to use a static address, then leave the second LAN port set to DHCP, and you can always change the cable over to re-gain access if something happens (like changing the router to one that uses a different address range), you can swap the cable and re-gain access (at a new DHCP address you can find on the display or in RAIDar)..
Well that helped. THANKS GUYS
I was able to get the Update to 6.10.8 and update the time to 0.us.pool.ntp.org
I have the NAS on DHCP and the 192.168.1.10 fixed in the router
--
I am stuck on the PLEX not claiming the server
I think the Netgear NAS 104 problem is RESOLVED.
Thanks so much for your help.
I will post something on "PLEX on NAS" community.
Maybe I'll get a Christmas Present from a similar super-user.
Blessings, Jim
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
