× NETGEAR will be terminating ReadyCLOUD service by July 1st, 2023. For more details click here.
Orbi WiFi 7 RBE973
Reply

Re: Windows 10, Server 2012r2 cannot access NAS 204 as a drive, but can as a ping or HTTP.

Aedmunde
Aspirant

Windows 10, Server 2012r2 cannot access NAS 204 as a drive, but can as a ping or HTTP.

 Model: ReadyNAS 204 Name: nas Status: Healthy Antivirus: 6/17/2017, 5:13:51 AM Firmware: 6.7.4 : June 17, 2017 12:33:01 PM

 

It's not a member of the domain?

 Running Diagnose:

The remote device or resource won't accept the connection Detected 
The device or resource (10.0.0.87) is not set up to accept connections on port "The File and printer sharing (SMB)".
The computer or device you are trying to reach is available, but it doesn’t support what you’re trying to do. This might be a configuration issue or a limitation of the device.

Tried refreshing the Active Directory Accounts (but they are listing correctly, so I'm of the opinion that it is communicating...)

 

 

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

C:\Users\Edmund>ping nas

Pinging nas.0EFBH.local [10.0.0.87] with 32 bytes of data
Reply from 10.0.0.87: bytes=32 time=1ms TTL=64
Reply from 10.0.0.87: bytes=32 time<1ms TTL=64
Reply from 10.0.0.87: bytes=32 time<1ms TTL=64
Reply from 10.0.0.87: bytes=32 time<1ms TTL=64

Ping statistics for 10.0.0.87:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms

C:\Users\Edmund>ping nas.0efbH.local

Pinging nas.0efbH.local [10.0.0.87] with 32 bytes of data
Reply from 10.0.0.87: bytes=32 time<1ms TTL=64
Reply from 10.0.0.87: bytes=32 time<1ms TTL=64
Reply from 10.0.0.87: bytes=32 time<1ms TTL=64
Reply from 10.0.0.87: bytes=32 time<1ms TTL=64

Ping statistics for 10.0.0.87:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Users\Edmund>net use \\nas
System error 53 has occurred.

The network path was not found.

 

C:\Users\Edmund>net use \\10.0.0.87
System error 53 has occurred.

The network path was not found.


C:\Users\Edmund>net use \\10.0.0.88
System error 53 has occurred.

The network path was not found.


C:\Users\Edmund>

 

 And yet using (Windows Media Connect compatible (ReadyNAS)😞  

This PC\nas: ReadyNAS 204  gives 

+\Browse Folders

+\Music

+\Pictures

+\Video 

(But will NOT share all the folders)

 

But access via the IP or name...  doesn't work.

Deleting the Active Directory doesn't work.

 

Last time I reset to factory defaults, but I don't want to copy / safe / restore all that data.... again.

 

suggestions?

 

 

 

Model: RN204|ReadyNAS204
Message 1 of 3
StephenB
Guru

Re: Windows 10, Server 2012r2 cannot access NAS 204 as a drive, but can as a ping or HTTP.


@Aedmunde wrote:

  And yet using (Windows Media Connect compatible (ReadyNAS)😞  

This PC\nas: ReadyNAS 204  gives 

+\Browse Folders

+\Music

+\Pictures

+\Video 

(But will NOT share all the folders)

 

That is readydlna, not SMB.

 

What firmware are you running?

 

Did you check the web ui to make sure SMB is still enabled?

Message 2 of 3
Aedmunde
Aspirant

Re: Windows 10, Server 2012r2 cannot access NAS 204 as a drive, but can as a ping or HTTP.

Sorry,  did look but didn't post back.

firmware 6.7.4  SMB was enabled,  just noted that the permissions refused to work.  (apparently cached in Windows).

 

Solution was to disconnect Active Directory and reconfigure.  Again, with a NEW user.  (don't know why)

 

However, the "appliance" portion that contains the referenced folders in the prior email, that appear in the Browse view, do NOT include any that I have configured or shared.

 

Other than that, it's back up...

Message 3 of 3
Top Contributors
Discussion stats
  • 2 replies
  • 3386 views
  • 0 kudos
  • 2 in conversation
Announcements