Re: Unable access readynas from windows explorer

Crofty7 · ‎2017-12-31

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 connect to it. I had no issues prior to the latest firmware date. Error code from WE is 0x80070035 The network path was not found.

Please Help!!

StephenB · ‎2017-12-31

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 · ‎2018-01-01

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?

Crofty7 · ‎2018-01-01

I've added an attachment showing what i see in WE, if that helps.

(Not sure how to insert screen shots!!)

StephenB · ‎2018-01-01

@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.

Crofty7 · ‎2018-01-01

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?

StephenB · ‎2018-01-01

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.

Crofty7 · ‎2018-01-01

I saw from your screenshot that the NAS is configured as being in workgroup. Make sure that the desktop PCs are also in workgroup.

The desktop is in the same 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.

Done that and i'm receiving the same messages.

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.

I'm running Kapsersky Total Security, i disabled it and Windows Firewall was already off. Tried everything again with no luck. This is baffling!!

StephenB · ‎2018-01-01

Try the same two commands on your laptop, just to make sure they work properly there.

Crofty7 · ‎2018-01-02

Hi,

Sorry for being a little dumb but i don't understand what you're asking me to do.

StephenB · ‎2018-01-02

@Crofty7 wrote:

Hi,

Sorry for being a little dumb but i don't understand what you're asking me to do.

It's my fault - there's another user with similar problems, but in his case his laptop works ok, and his desktop PCs don't have access.

So where we are is that

net use * /delete

net use t: \\192.168.1.86\data /user:admin nas-admin-password

and

net use * /delete

net view \\192.168.1.86

both fail. The Windows Firewall is off, the Kapersky Total Security software is disabled, IPv6 is disabled on the NAS. The network classification in Windows is private, and the PC and the NAS are both in the same workgroup (called workgroup).

Is all that info correct?

In addition, the PC also has a 192.168.1.## address, correct?

Crofty7 · ‎2018-01-02

Correct.

How do I check the ip address of the laptop?

StephenB · ‎2018-01-02

typing ipconfig in CMD will give it to you (though there is a lot of printout).

Each NIC will give you an output like this:

Wireless LAN adapter Wi-Fi:

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::7c8f:36a9:f667:9fea%6
IPv4 Address. . . . . . . . . . . : 10.0.0.46
Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 10.0.0.1

For that particular adapter, the IP address is 10.0.0.46. You should see a 192.168.1.x address.

Crofty7 · ‎2018-01-02

address is 192.168.1.105

StephenB · ‎2018-01-02

@Crofty7 wrote:

address is 192.168.1.105

which is fine.

I am running out of ideas on this one, as we've checked all the usual things.

If you go into the admin web ui for the NAS, is SMB showing as green on system->settings->services? Also, it is enabled for your shares (check the shares tab).

If it is listed, and green then perhaps try rebooting the NAS and see if that helps.

If it isn't shown for your shares (or isn't green in system->services), then let us know.

Crofty7 · ‎2018-01-02

SMB is green and every folder is shared to everyone apart from Home Folders which is shared with Admin and my email address.

I tried rebooting before i posted on here and it didn't work.

I will try rebooting the NAS and router and see if that does anything.

Crofty7 · ‎2018-01-02

After all that rebooting the router and NAS has sorted it. What a game that was.

I really appreciate all your help.

Do you think the router may lost its path to the NAS after it had updated to the latest firmware?

Once again thanks for your help.

StephenB · ‎2018-01-03

I'm glad it's working now...

@Crofty7 wrote:

Do you think the router may lost its path to the NAS after it had updated to the latest firmware?

You were able to reach the NAS web UI, so I think the action that really fixed it was rebooting the NAS.

Either way, it's up now, and that's the important thing.