Remote access to shares has been working reliably for a few months, until last Monday 3 July 2017 it stopped working on all 3 clients with the popup box error
"ReadyNAS Remote could not connect to the ReadyNAS server, please check your internet connection and DNS settings. If the ReadyNAS is behind an HTTP proxy, please make sure you have entered correct proxy server settings"
It is a ReadyNAS 202 firmware 6.4.2 The remote access via the readyNAS ReadyCloud remote client and cloud service. I did not have to do any port fowarding or pinholes to get it to work originally.
I don't run any addons.
Using a single NIC on static IP but the router has DHCP
As far as I know there were no changes on the LAN or the WAN that weekend.
Things I have tried.
Reinstalled the client application to latest and even an older version. (Clients are all fairly fresh Win10 64 laptops)
Turned off IPV6.
Added DNS entries of the local router, and 8.8.8.8 and 8.8.4.4
Restarted the NAS gracefully.
Restarted the router.
successfully migrated from your old ReadyCLOUD account to newest MyNETGEAR account
Now I can at least login to theReadyCLOUD.netgear.comportal, and the ReadyNas is in the list, but shows
RadyNas is offline
Check power and internet connectivity
Alert email tests fail to send
so I'm guessing either the NAS is not able to send the data out or network ports have been changed (blocked).
But there is no detailed log that I can see to find out what is happening...
We had a problem with our ReadyCloud and ReadyNAS Remote VPN server but it should be resolved now, i think that was fixed the other day.
You are using a ReadyNAS OS6 unit so you should be using ReadyCloud desktop client and not ReadyNAS Remote. All ReadyNAS Remote users should upgrade to SSO account (ReadyCloud or myNetgear account). You are also running a very old firmware on your NAS, the latest is 6.7.5. If you currently have access to all the data as well as the home shares of all the users (local and ReadyNAS Remote users), backup all the data.
I somehow got the intenet access working again yesterday - I think just by turning ReadyCloud off and on again. (although I'm pretty sure I had also tried that earlier.)
I also repowered the device at that time - (inadvertently as the power cable had been cable tied too short 😞 ! )
After getting ReadyCloud working, I made sure I had a good backup, then upgraded the firmware successfully to the latest current 6.7.5.
I will certainly use the latest client available.
Not sure how to attach a screen shot of a before and after of the issue, so I'll describe it:
On the Cloud page, top left showed
[blank] Offilne TICK Services Available
and after
TICK Internet Available TICK Services Available
Blank as in no cross or symbol, but an empty spaceholder instead.
One last question: when a drive is mapped via the Remote access client as \\5.123.321.14\sharename
will the traffic still travel through the internet when the client is onsite on the same lan as the readynas?
I think yes, because that ReadyCloud and ReadyNAS Remote desktop client connects to a VPN server and authenticates the login first. So, if the user is at the same network where the NAS is, it is best to map the LAN IP address of the NAS instead.
The issue is that if the LAN address \\readynas\sharename is mapped as X: when on the LAN, when working remotely, the user needs X: mapped to the same content but as \\remoteip.sharename instead.
Two locations cannot be mapped at the same time under Windows, and I don't want users changing mappings each time they move, so the remoteip mapping must be used. It does work in this configuration.
When on the LAN, does the network traffic "realise" it does not need to go over the internet - and so stays in the LAN (even if the authentication is first done over the vpn)?
There must be a large body of users who have overcome this hurdle..? I couldn't find an FAQ on it?
You can keep using the ReadyCloud mapped share with its assigned drive letter it is just that since it is using a Leaf Network adapter, it always needs Internet and needs to be able to log in to ReadyCloud. Maybe it is best you make another mapped drive letter so that in case there is a problem logging in to ReadyCloud, the user has an option to use it.
We’d greatly appreciate hearing your feedback letting us know if the information we provided has helped resolve your issue or if you need further assistance.
If your issue is now resolved, we encourage you to mark the appropriate reply as the “Accept as Solution” or post what resolved it and mark it as solution so others can be confident in benefiting from the solution.
The Netgear community looks forward to hearing from you and being a helpful resource in the future!
