NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Crofty7
Dec 31, 2017Aspirant
Unable access readynas from windows explorer
Hi, Since updating to the latest firmware 6.9.1 from 6.9.0 i can no longer access the readynas through windows explorer. My laptop is operating Windows 10. WE detects the readynas but will not co...
StephenB
Dec 31, 2017Guru - Experienced User
What happens if you open CMD and then enter
net use * /delete
net use t: \\nas-ip-address\data /user:admin nas-admin-password
Use the real IP address and password of course, and be careful with the spaces and the slash directions. The first command terminates any open network sessions, the second attempts to map the NAS data volume to drive letter t. (BTW, if your volume isn't named data you will need to adjust the command to match your volume name).
Crofty7
Jan 01, 2018Aspirant
Hi StephenB
When i enter net use * /delete i get the following message, "There are no entries in the list".
When i enter net use t: \\nas-ip-address\data /user:admin nas-admin-password i get the following message, "System error 53 has occurred. The network path was not found".
The NAS ip address is use is 192.168.1.## and i assume when you say volume it's the name i have given the NAS as it would appear in WE?
- Crofty7Jan 01, 2018Aspirant
I've added an attachment showing what i see in WE, if that helps.
(Not sure how to insert screen shots!!)
- StephenBJan 01, 2018Guru - Experienced User
Crofty7 wrote:
i assume when you say volume it's the name i have given the NAS as it would appear in WE?
NO. It's the name of the RAID volume. You see that on the volumes tab of the web ui. If you did the usual setup it is called data.
The NAS name in WE is called the "hostname". You'd normally set up a credential for both 192.168.1.## and for CROFTY7 (windows actually treats them as two machines).
Crofty7 wrote:
When i enter net use * /delete i get the following message, "There are no entries in the list".
That's fine, just ignore that. If there were entries in the list you'd have gotten a prompt to continue (which you should do).
Crofty7 wrote:
When i enter net use t: \\nas-ip-address\data /user:admin nas-admin-password i get the following message, "System error 53 has occurred. The network path was not found".
First check that you have the correct volume name. Also, if the admin password of the NAS is still set to password you need to change it to something else.
Also check that Windows has the network connection set to "private" and not "public".
Another thing to do is to go into the ReadyNAS network settings and disable IPv6.
Another command you can try is net view \\192.168.1.## That should give you the share list.
BTW it is perfectly safe to post the complete 192.168.1.## address. 192.168.x.x addresses are purely local, and can't be used to reach your systems over the internet.
- Crofty7Jan 01, 2018Aspirant
The volume is called data so i tried t: \\nas-ip-address\data /user:admin nas-admin-password and this time it responded with "The system cannot find the drive specified".
The pasword on the NAS was changed, i use the same password for readycloud and WI. I assume this is correct?
The netowrk connection is set to Private and i have disbled IPV6. No change in cmd when i try again.
Tried net view \\192.168.1.86 but it came back with "System error 5 has occurred. Access is denied".
if i go onto chrome and type in 192.168.1.86 it takes me straight through to admin page. Is this the correct IP address to be using in cmd?
- StephenBJan 01, 2018Guru - Experienced User
Crofty7 wrote:if i go onto chrome and type in 192.168.1.86 it takes me straight through to admin page. Is this the correct IP address to be using in cmd?
Yes.
I saw from your screenshot that the NAS is configured as being in workgroup. Make sure that the desktop PCs are also in workgroup.
Also, it's good to use the net * / delete command prior to your tests with net use and net view. It makes sure everything starts with a clean slate.
Do you have internet security software running on the desktops? If so, try disabling it and retesting. Similarly, if the windows firewall is running turn that off and retest also.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!