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)..
THANKS so much for replying
1) I'm letting the system assign 192.168.1.10 to the NAS [it has remained that ## for ever]
The DHCP start address is 192.168.1.64 so the 1.10 just stays there.
2) I used both NTP values youi suggested and get the same error
If you want screen shots from my ATT router - let me know.
That's where I think the problem is - the NAS is unreachable OUT or INTERNALLY by the ROKU/PLEX application. yet I can file-manage the NAS from anywhere else on the home network. Really confusing me. Thanks.
jaholstein wrote:
THANKS so much for replying
1) I'm letting the system assign 192.168.1.10 to the NAS [it has remained that ## for ever]
The DHCP start address is 192.168.1.64 so the 1.10 just stays there.2) I used both NTP values youi suggested and get the same error
If you want screen shots from my ATT router - let me know.
That's where I think the problem is - the NAS is unreachable OUT or INTERNALLY by the ROKU/PLEX application. yet I
It does sound like the router might be preventing the NAS from reaching the internet.
Have you tried rebooting the NAS and the router?
Good Morning-
I rebooted the NAS and the ATT Router.
Getting same connection errors.
I'm going to paste some relevant information from the Router:
Here is the Router's info on the NAS
MAC AddressIPv4 Address / NameLast ActivityStatusAllocationConnection TypeMesh Client
28:c6:8e:35:3f:c8 192.168.1.10 / unknown28c68e353fc8 Fri Dec 23 09:09:37 2022 on static Ethernet LAN-4 No And the
Firewall Status
Packet FilterIP PassthroughNAT Default ServerFirewall AdvancedOn Off Off On No NAT/GAMING
No Packet Filters
No Public Subnet Hosts
IP Passthrough is OFF
Firewall Advanced
Drop incoming ICMP Echo requests to LAN Off Drop incoming ICMP Echo requests to Device LAN Address On Drop incoming ICMP Echo requests to Device WAN Address On ESP Header Forwarding Off Authentication Header Forwarding Off Reflexive ACL On ESP ALG Off SIP ALG On Does any of this help you?
Thanks AGAIN for your consideration.
Jim
The troubleshooter on the router shows all services PASS
I'm also trying to contact ATT tech for some NetOp help.
As soon as I get this resolved I'll reply here.Does the AT&T router have an IPv4 WAN address?
If it does, you might try disabling ipv6 on the NAS, and rebooting it.
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.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
