NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
ReadyNAS shown on network but not accessible after upgrade to OS 6.5.0
I upgraded the OS today and got the ReadyCLOUD changeover completed to day successfully, however when I try to access the NAS through the 'Network' ( intranet ), it says that the device is inaccessible.
This is also the case when using the IP address for the NAS. Access to the device is only able to be done through http protocols. Local IP works with http, and access through the ReadyCLOUD account works as well.
I have also rebooted ALL devices since the upgrade twice to see if that was all that was needed, but it seems that the NAS is the only one refusing connections. This was working well before the upgrade.
ReadyNAS RN316-100NAS ver. 6.5.0
Windows 10 Pro x64
Windows 8.1 RT Lumia 2520 Tablet
Windows 10 Mobile Lumia 630 Phone
NETGEAR NighthawkX6 R8000 Router
NETGEAR ReadyCLOUD App for Windows ver. 1.12
- Yeah I have it sorted out for now... Dropping the ReadyCLOUD service for now. Rebooting clears it out too.
82 Replies
Replies have been turned off for this discussion
I didn't see this behavior with my RN102 and RN202.
If you are eligible for free chat support, I suggest using it.
No, I purchased the 316 as a pre-owned display model.. This would seem like something simple... unless there is some sort of problem within the 6.5.0 version of the OS regarding my specific model... My use case however is quite common.
Hello MarkusX0,
6.5.0 needs ReadyCloud account upgrade to myNetgear, so make sure the account is upgraded.
Log out any ReadyCloud account from the ReadyCloud Windows desktop client, then test again the share access. Check the permission of the share that you are accessing too.
Unregister your ReadyCloud account from the admin page then register it, this should be in an email format. Then please also test if you can browse the folders when main ReadyCloud account is logged to the desktop client.
Regards,
- My system does not have anything called Samba.. and as I mentioned above I do not have anything under the logs error it otherwise pointing to the cause of the problem... Not really for sure what Samba is exactly..
MarkusX0 wrote:
My system does not have anything called Samba.. and as I mentioned above I do not have anything under the logs error it otherwise pointing to the cause of the problem... Not really for sure what Samba is exactly..Samba is the linux package that provides SMB access (e.g., Windows Network Shares). So he is suggesting that you go to system->settings and turn off the SMB service (and then turn it back on again).
jak0lantash meant the SMB protocol under System > Settings > Services.
- I will check that out when I get a chance this evening. I did check that, it was definitely on... But this may help.. I even uninstalled the SMB Plus app to see if it was interfering as well but no change afterwards.. Planning on reinstalling.. Will check back in later though..
I am having the exact same problem the original poster lists. I've just tried the advice listed in this thread, and none of it worked.
One additional piece of info for my case. When I tried to upgrade my ReadyCloud account to MyNetgear it got stuck when I tried to put in my original email address. It only progressed when I entered a new email address, which is now what I seem to have to use to log in through the ReadyCloud web portal.
- I have the same exact problem here, just uphrade my two Readynas (104 and 314) and after the firmware upgrade no SMB access. Netgear suport spend like 4-5 houres last night connectet to my system by TeamViewer and nothing. I can connect by FTP, the DLNA works and everything else but the SMB acces, 5 different computers with different operating systems and 1 MacBook Pro??? This is definitely a firmware problem.
Are you trying to login to SMB using your ReadyCLOUD account? How many characters are in your email address?
- My friend it's got nothing to do with the ReadyCloud. I can login and access them with no problem, The problem is on the network.
From the Microsoft web page:
The Server Message Block (SMB) Protocol is a network file sharing protocol, and as implemented in Microsoft Windows is known as Microsoft SMB Protocol. The set of message packets that defines a particular version of the protocol is called a dialect. The Common Internet File System (CIFS) Protocol is a dialect of SMB. Both SMB and CIFS are also available on VMS, several versions of Unix, and other operating systems.But earlier in the thread I see that ReadyCLOUD is being used, so I am wanting to see if there is a connection.
If you are using a local user does that have an email address that is in use by one of your ReadyCLOUD users?
- In my case, it is completely different. I use the admin account, however a message pops up saying that it is not able to be accessed... Without even asking for the login..
But like I was saying... No email address being used for the user account.. I also have the exact same problem!
just updated to 6.5.0 and completely lost SMB support/access!.
All works fine via web, but when I try access with Windows Explorer it fails to connect "cannot access...".
Tried turning OFF/ON, rebooting, etc. Still not working. IP adresses all ok. SMB is simply not working! Never had an issue before this update!
Please fix ASAP!! I cannot use the NAS without SMB!
- I can access the admin page by the IP address, I am at work right now but I can check more when I get home.
I too am having this issue after upgrading to 6.5.0 - can access the NAS via the web browser but not on windows by navigating to the file folder anymore.
This needs to be fixed IMMEDIATELY!!
- OK my friend this is what I just find out , I don't know if somebody else wants to try it and let us know but this is my results. I have 2 NAS a 104 and a 314, I decided to backup my 104 to my pc and did a factory default reset And believe it or not after that everything is back to normal on thE 104, the 314 still have the same problem. On the 104 I clean the disks and start all over again. If you want to trythis do it on your own risk, for me it worked. Now I am going to back up the 314 to the 104 try the same thing on it. Good luck and let us know your results.
I wonder if I remove my disks before a Factory Default reset, if the data will still be accessible..
Like do a factory reset... Then after it finishes, inserting the HDD's and picking up from there?
The reason I say this is mainly because I have nowhere to back up everything... ( Backups of the backups scenario )
...and I am assuming it will not... because it just sounds like too easy of a solution.. :P
OK I did tried this on my 314 andit work. I didn't have to reset the defaultlike I did with the 104 and for some reason it start working. The only thing I did was change the email on my cloud to a different email from the Microsoft account that I use to log into the computer. Somebody else mentioned and I didn't believe it, and last night after work I fix it in less than two minutes. Automatically all my computers on the network start seeing both Drives, and that's without the Mycloud app on, because another workaround Wass to map the drives from the Mycloud app but it Wass map from a VPN ( virtual private network ) that was created by the app. Go ahead just change the email from Mycloud login.
Changing the MyNETGEAR email address for ReadyCLOUD to a email addres that's not the same as the one I'm useing for Windows 10 fixed it for me as well.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
