ReadyNAS NV+v2 - Windows 11 issues

I have reset the unit back to factory and are running the default password of password.

Here is the output of cmd in admin mode:

Microsoft Windows [Version 10.0.22621.2134]
(c) Microsoft Corporation. All rights reserved.

C:\Windows\System32>net use z: \\nas-BE-6F-4D-02\Pictures /u:admin password
System error 67 has occurred.

The network name cannot be found.

C:\Windows\System32>ping nas-BE-6F-4D

Pinging nas-BE-6F-4D.local [10.1.2.80] with 32 bytes of data
Reply from 10.1.2.80: bytes=32 time<1ms TTL=64
Reply from 10.1.2.80: bytes=32 time<1ms TTL=64
Reply from 10.1.2.80: bytes=32 time<1ms TTL=64

Ping statistics for 10.1.2.80:
Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
Control-C
^C

C:\Windows\System32>\\10.1.2.80\Music
The user name or password is incorrect.

C:\Windows\System32>net use z: \\nas-BE-6F-4D-02\Music /u:admin password
System error 67 has occurred.

The network name cannot be found.

The folders on the NAS are setup up as default:

Just for kicks, I have also tried disabling my norton firewall whilst running CMD and tried uploading a file and running the windows commands, figured it wouldn't make a difference but wanted to rule it out. 

Music, Pictures, and Videos are subfolders of the media Share.

Try 

net use z: \\10.1.2.80\media /u:admin password

Windows often has a problem properly locating a NAS by name.  It's not a unique ReadyNAS issue, I've seen it on general Linux forums, but without a true solution.

There are two work-arounds.  One is to just always use the IP address instead of the name, as StephenB suggested.  The other is to add the name to the Windows hosts file (Google it).  Both of these require that the NAS always be at the same address, which is best accomplished by reserving the address in your router, not setting up a static IP in the NAS.

Thanks Guys, 

I did input the cmd line as Stephen and mentioned and when navigating via the browse button in raidair it popped asking for credentials and now gives me access to upload files etc as well as more folders be visible compared to via DNS route.  

I did also try adding the DNS entry in my hosts file as (and saved etc): 

 but this made no difference, i also then tried inputting cmd line entry for DNS target and here is the output:

C:\Users\dave2>net use z: \\nas-BE-6F-4D-02\Pictures /u:admin password
System error 67 has occurred.

The network name cannot be found.

---

Dfurn21 wrote:

 

 

C:\Users\dave2>net use z: \\nas-BE-6F-4D-02\Pictures /u:admin password
System error 67 has occurred.

The network name cannot be found.

 

 

---

Pictures is NOT a share, it is a subfolder of the media share.  You aren't using the correct path.

This one should work:

 net use z: \\nas-BE-6F-4D-02\media\Pictures /u:admin password

Your second windows explorer screenshot is actually showing the ReadyDLNA media server.  That is only for playback of media, there isn't any write access.  If you aren't using DLNA to play the media on the NAS (for instance on a smart TV), then I recommend that you disable the DLNA service in the dashboard.  That will remove the DLNA server from your network locations.

Your screen shots have not been approved, so I can't see them to see your hosts file.  I hope you did Google how to do it, not just go in and try to do a normal edit.  You have to edit with an editor (notepad works fine) that's launched as administrator.  Otherwise, when you "saved" it, it didn't actually save.

Have you made sure that the NAS is at the IP address you put in the hosts file?  Did you re-boot the PC after changing hosts?

I suggest that we focus on getting full file access using the IP address first, and then circle back to the NAS hostname.

Trying to do too many things at once is creating some confusion. 

Sorry Guys, 

Working fine for the via the IP address, doesn't work via the DNS address.

# localhost name resolution is handled within DNS itself.
# 127.0.0.1 localhost
# ::1 localhost

10.1.2.80(tab)(tab)nas-BE-6F-4D-02

---

Dfurn21 wrote:

# 127.0.0.1 localhost
# ::1 localhost

10.1.2.80(tab)(tab)nas-BE-6F-4D-02

---

Not sure if the tabs are getting in the way or not, generally I've used a space.

What happens if you enter ping nas-BE-6F-4D-02 from the command line?

Note you don't need to stick with this hostname - you can use something simpler if you like.  For instance, just nas.

You can also change this in the dashboard, to keep things consistent.

I have always tab when doing it for work but tried with a space and made no difference.

Ping response looks fine: 

C:\Users\dave2>ping nas-BE-6F-4D-02 -t

Pinging nas-BE-6F-4D-02 [10.1.2.80] with 32 bytes of data
Reply from 10.1.2.80: bytes=32 time<1ms TTL=64
Reply from 10.1.2.80: bytes=32 time<1ms TTL=64
Reply from 10.1.2.80: bytes=32 time<1ms TTL=64
Reply from 10.1.2.80: bytes=32 time<1ms TTL=64
Reply from 10.1.2.80: bytes=32 time<1ms TTL=64

Ping statistics for 10.1.2.80:
Packets: Sent = 5, Received = 5, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
Control-C
^C
C:\Users\dave2>

---

Dfurn21 wrote:

 

Ping response looks fine: 

C:\Users\dave2>ping nas-BE-6F-4D-02 -t

Pinging nas-BE-6F-4D-02 [10.1.2.80] with 32 bytes of data
Reply from 10.1.2.80: bytes=32 time<1ms TTL=64
Reply from 10.1.2.80: bytes=32 time<1ms TTL=64
Reply from 10.1.2.80: bytes=32 time<1ms TTL=64
Reply from 10.1.2.80: bytes=32 time<1ms TTL=64
Reply from 10.1.2.80: bytes=32 time<1ms TTL=64

 

---

Ok.  How about 

net view nas-BE-6F-4D-02

Note with cmd running as admin:

Microsoft Windows [Version 10.0.22621.2134]
(c) Microsoft Corporation. All rights reserved.

C:\Windows\System32>net view nas-BE-6F-4D-02
System error 5 has occurred.

Access is denied.

C:\Windows\System32>

Is the network designated as private on the PC you are using?  I'm not really sure that would affect this, but it's something good to check.

Like StephenB , I don't know if Windows likes tabs in the hosts file.

Yep, Ethernet connection set as private network.

Also worth noting network discovery on and file and printer sharing on.

---

Dfurn21 wrote:

Note with cmd running as admin:

C:\Windows\System32>net view nas-BE-6F-4D-02
System error 5 has occurred.

 

---

Do you get the same error when you enter this?

net view 10.1.2.80

Do you have any antivirus packages or internet security software running on the PC? If you do, then try disabling them before running the command.

Sorry Guys, 

Was working away last week and didn't get chance to have a look at this.

Output from cmd ran as admin with norton 360 firewall turned off is as follows:  

Microsoft Windows [Version 10.0.22621.2134]
(c) Microsoft Corporation. All rights reserved.

C:\Windows\System32>net view 10.1.2.80
System error 53 has occurred.

The network path was not found.

C:\Windows\System32>

A competitive NAS provider has an informative and very complete System Error 53 Check List 

---

schumaku wrote:

A competitive NAS provider has an informative and very complete System Error 53 Check List 

---

This one doesn't quite fit, since Dfurn21 can access the NAS using its IP address

• Ping works both using IP address and host name
• SMB access works using ip address
• SMB access fails using hostname
• adding hostname to the hosts file doesn't help.

The network is set to private, and the various group policies in the guide you linked in must already be ok, since IP address access works.

Might seem obvious, but perhaps try rebooting both the PC and the NAS next.