NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
PCJB
Dec 28, 2022Aspirant
ReadyNAS NV+ lost shares access for Windows 10 PC
Hi all, I’ve had a ReadyNAS NV+ (RND400 SPARC running 4.1.16) working fine for about 5 years as a home file server and media server. It’s got 4 * 2TB drives configured in an X-RAID. Last week i adde...
- Dec 29, 2022
Thanks StephenB,
Problem solved but not sure what i have done to fix it!
I checked the file access rights as suggested and set all the shares to read/write with no names in the access fields ( host, read, write , groups) and checked the guest user access was disabled ( unticked). The advanced CIFS settings set to automatically set permissions for new files and folders to R/W for group and everyone. I also turned off Opportunistic locking as I wondered if Windows 10 could be unhappy about local caching of files. But with no difference. Windows gives the same error 'resource not available'.
The 'net use' command worked in that I could add the shares a network drives and could access the files ok using DOS commands, but Windows File Manager could not, although it reported the drives and their capacity correctly! Presumably the Windows apps were not getting correct information somehow, but lower levels were OK. I added two different shares with different user names and Windows didn't like that. 'Different user names to the same share resource are not permitted' type error came up, but adding the shares using the same login details for each one worked fine at the DOS level but still not at the Windows app level.
So I decided to reboot the ReadyNAS and it now works fine! Not sure what has fixed it. Suspect that Windows and the ReadyNAS needed rebooting to resolve.
I've made notes for the future of what to check. Thank Goodness I had SSH access, as I wouldn't have stood a chance of sorting it out.
Now back to the original job of getting the backups sorted out!
Thanks again to all who responded and Happy New Year for 2023.
Paul .
StephenB
Dec 28, 2022Guru - Experienced User
PCJB wrote:
Frontview share access for this share shows this. Do I need user names here?
No. But you could check the guest access box, and also scroll down further and make sure that everything is set to read/write.
I also suggest this:
I suggest trying the following commands from the Windows CMD line:
net use * /del /y
net use t: \\192.168.1.100\Archive /u:admin nas-admin-password
using the real admin password for the NAS of course. The first command terminates any open SMB sessions, the second attempts to map the Archive share to drive letter T.
PCJB
Dec 29, 2022Aspirant
Thanks StephenB,
Problem solved but not sure what i have done to fix it!
I checked the file access rights as suggested and set all the shares to read/write with no names in the access fields ( host, read, write , groups) and checked the guest user access was disabled ( unticked). The advanced CIFS settings set to automatically set permissions for new files and folders to R/W for group and everyone. I also turned off Opportunistic locking as I wondered if Windows 10 could be unhappy about local caching of files. But with no difference. Windows gives the same error 'resource not available'.
The 'net use' command worked in that I could add the shares a network drives and could access the files ok using DOS commands, but Windows File Manager could not, although it reported the drives and their capacity correctly! Presumably the Windows apps were not getting correct information somehow, but lower levels were OK. I added two different shares with different user names and Windows didn't like that. 'Different user names to the same share resource are not permitted' type error came up, but adding the shares using the same login details for each one worked fine at the DOS level but still not at the Windows app level.
So I decided to reboot the ReadyNAS and it now works fine! Not sure what has fixed it. Suspect that Windows and the ReadyNAS needed rebooting to resolve.
I've made notes for the future of what to check. Thank Goodness I had SSH access, as I wouldn't have stood a chance of sorting it out.
Now back to the original job of getting the backups sorted out!
Thanks again to all who responded and Happy New Year for 2023.
Paul .
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!