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)..
jaholstein wrote:
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 "Operation time out, Communication error, Check your Internet connection, DNS Settings or proxy settings"
When I check time settings and put in 132.163.96.5 I get "failed to set NTP settings. NTP server is untrachable"
Are you using DHCP to assign the NAS an IP address? Or did you create a static IP address?
FWIW, you might consider using 0.us.pool.ntp.org and 1.us.pool.ntp.org for NTP (or similar pool.ntp.org addresses for your geography).
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.
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.Those statements are self-contradictory. "Letting the system assign an address" would result in an address in the DHCP range, which is not the case. You have either assigned a fixed address within the router (which doesn't usually result in this issue) or you have set a static IP in the NAS (which will have this result if you failed to properly set the gateway address).
Sandshark wrote:
Those statements are self-contradictory. "Letting the system assign an address" would result in an address in the DHCP range, which is not the case. You have either assigned a fixed address within the router (which doesn't usually result in this issue) or you have set a static IP in the NAS (which will have this result if you failed to properly set the gateway address).This depends on the router. My Orbi has the DHCP range set to 100...254, and I reserve addresses in the 2 ... 99 range.
StephenB wrote:
Sandshark wrote:
Those statements are self-contradictory. "Letting the system assign an address" would result in an address in the DHCP range, which is not the case. You have either assigned a fixed address within the router (which doesn't usually result in this issue) or you have set a static IP in the NAS (which will have this result if you failed to properly set the gateway address).This depends on the router. My Orbi has the DHCP range set to 100...254, and I reserve addresses in the 2 ... 99 range.
Yes, but you are not "letting the system assign an address", you are specifying to the router what address to assign (the first possibility I listed above).
Sandshark StephenB
No - my statement is not [really] contradictory, here's what I think happened:Previously the DHCP range was 10-253 during that time 192.168.1.10 was assigned
Later the DHCP range was set to the current value of 64-253 [my son did it -- and he's dead]--
All of my devices can file view/manage the NAS on the wired or WiFi connection.
However the NAS
- cannot get to the internet to check for updates or set the NTP server
- cannot be "seen" by the PLEX server running on my ROKU
- cannot be "seen" on the PLEX WebApp running on my old-reliable Win7Pro
http://192.168.1.65:32400/web/index.html#!/
I thought the AT&T router might be the problem.
Today first level support was courteous but of no help.- she had me add IP Passthrough to the NAS MAC address - didn't help - I removed
- she had me change my Network setting from PUBLIC to HOME - didn't help
I'm awaiting 2nd level support.
--
I can't find any Win7Pro firewall in or out that refers to the NAS
The default is 192.168.1.1 to .199 all profiles, Allowed, any program
--
So thanks both of you for responding.
Do you have any ideas?
Jim-near-StLouis,Mo
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
