This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
Re: ReadyNAS 104 [6.8.0] Communication error to NTP & Updates
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)..
Re: ReadyNAS 104 [6.8.0] Communication error to NTP & Updates
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.
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.
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).
Re: ReadyNAS 104 [6.8.0] Communication error to NTP & Updates
@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.
@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).
Re: ReadyNAS 104 [6.8.0] Communication error to NTP & Updates
@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
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.
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.
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.
Re: ReadyNAS 104 [6.8.0] Communication error to NTP & Updates
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)..
