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.
You wait for a fix and 2 arrive at the same time. Just found the ReadyCLOUD app. Works well. Need to uninstall ReadyNAS remote. New ReadyNAS Duo might be EOL, but it just works. Probably should be on another forum?
I got the same issue. On my laptop and desktop pc With my desktop i can acces my nas via the task manager by tiyping in \\192.168.2.1 than i get connection , i can ping it and also via webbrowser is accesible ,
But it's not via the file explorer. What is going on .
So we just have to throw our equipment out the window 10?
OR will ReadyCloud support Duo v2?
(I should have seen why it suddenly got cheaper just before the new one came)
Darn
Will I be able to use the readynas without the remote?
Are you saying that the Windows 10 beta isn't working for you?
The Remote software is not needed to use your duo v2. It provides access over the internet, but there are alternatives - port forwarding in your router, or OpenVPN in the router.
The v2 platform has been end of life for some time now.
I'm having a slightly different problem in connecting since I switched to Windows 10. Windows does not like the security certificate from my ReadyNAS 4 Ultra and won't let me access the data. It will let me override the security problem using Raidar and use Frontview, but I can't get at my data. Is there a way to fix the certificate problem?
You said you could ping it by IP address, I was asking about pinging it by name.
If you can ping it by name, then go into Windows Credential manager and delete any credentials stored for the NAS name. Then create a new one, specifying the log on and password that you want to use with the NAS.
I can only ping my ReadyNAS 4 Ultra by IP address, but not by name.
So that is the key to your problem.
One workaround is simply to use the IP address. You can also workaround by editing the PC hosts file (adding the ultra name/IP manually), though that isn't a great solution - especially if you have multiple PCs with this problem.
Is the name resolving to a different IP address? Or is it just not finding it? If it does get the wrong IP, is that IP on your local lan?
What happens if you enter ping -a IPaddress? That should return the NAS name.
I realise that but can't the solution be removed and replaced with one that works?
That can be done, but it is not a path I'm willing to go down.
There are way too many posts in this forum to try to keep them all up to date. Plus I won't change other people's words w/o a really strong reason - and being outdated is not strong enough.
