ReadyNAS NV+v2 - Windows 11 issues

[Dfurn21]

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

[StephenB]

---

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

[Dfurn21]

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>

[StephenB]

---

@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

[Dfurn21]

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>

[Sandshark]

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.

[Dfurn21]

Yep, Ethernet connection set as private network.

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

[StephenB]

---

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

[Dfurn21]

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>

[schumaku]

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

[StephenB]

---

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