Forum Discussion

Aspirant

Oct 20, 2016

Can no longer browse ReadyNas

Hi, I have a ReadyNAS Ultra 2 [X-RAID2], RAIDiator 4.2.30 and have been running it succesfully for a couple of years. Suddenly as of yesterday I can no longer browse the Nas drive via file ex...

Other Discussions

apeterson

Aspirant

Jul 25, 2017

Now, I am getting the same problem. My ReadyNas, Model: RNDU6000, has been up and running for almost 5 years, with no issues. Until now. Now I am getting the messages that I cannot connect a share. I've followed all the suggestions listed in this tread. none work. I still keep getting the messages:

- The specified network name is no longer avialable.

- System error 64 has occurred

What works:

1) RAIDiator successfully connects, telling me that the system is just fine.

2) web/browser admin successfully connects, and lets me make adjustments, check status, etc.

What does not:

- mapping a drive, from explorer, or in a cmd window via net use (from examples above)

- I've tried three different machines, that previously could connect to the ReadyNas.

Two things happened. Note sure which, if either is causing the problem.

ReadyNas firmware upgraded to RAIDiator 4.2.31

And Windows 10 did some updates.

Any thoughts or suggestions would be appreciated.

Thanks

StephenB
Guru - Experienced User
Jul 25, 2017
What happens if you run CMD on the windows system and enter

net use * /delete

net use t: \\nas-ip-address\C /user:admin nas-admin-password

Use the real IP address and admin password of course, and be careful with the spaces and slash directions.

The first command terminates any open SMB sessions, the second attempts to map the NAS data volume as drive letter T.
- apeterson
  Aspirant
  Jul 25, 2017
  Thanks, but already tried all the steps listed in this thread:
  C:\>net use * /delete
  There are no entries in the list.
  C:\>net use t: \\192.168.1.13\C /user:admin --pw--
  System error 64 has occurred.
  The specified network name is no longer available.
  - StephenB
    Guru - Experienced User
    Jul 26, 2017
    Did you check that SMB is still enabled on the NAS?
    
    What version of Windows 10 are you running? It's possible that the SMBv1 client was disabled on the windows system.