RND4000 WIn 10 Unexpected Network error

Question

Hi All,&nbsp;I just upgraded the latest firmware 6.9.3. After the reboot I&nbsp;noticed that I could not access my shared folders. The hostname is "nas" and the device is 192.168.1.99 *DHCP assigned, static).&nbsp;I could not map either ip add or hostname under Network in Win explorer. Getting error message "Windows could access the network driveXXXX"However under "My Pc" I can add the network location using the IP address.&nbsp;Same under window expl, when i enter \192.168.1.99 in the address bar, I can see the contents of the shared folders. I can't do the same using hostname.&nbsp;Both NAS and the PC is in same workgroup. I was able to access the files prior to the upgrade. Since then I downgraded the firmware to 6.9.2 but still having the same issues.&nbsp;Any help greatly apperciated. Thanks heaps.

StephenB · Answer

Resolving hostnames of linux systems via windows has always been a bit hit-or-miss.&nbsp; I don't know any sure-fire fix - though you might try rebooting your router and then the PC.&nbsp;
&nbsp;
Personally I reserve an IP address in my router for my NAS, and just use that.

arul999 · Answer

Thanks.&nbsp;I did reserved an Ip Add for the nas in my router. I just find it strange with .the new firmware

StephenB · Answer

arul999&nbsp;wrote:
I just find it strange with .the new firmware

I've seen lots of posts here which report that

sometimes it happens after a firmware upgrade
sometimes it happens when a router is replaced
sometimes it happens when windows is updated
sometimes it only happens on some PCs and not others
After it fails, it sometimes starts working again with no obvious changes to the setup.

I've also seen references to this issue with other equipment (not ReadyNAS).
&nbsp;
In the specific case of the firmware upgrade, other users have also reported that downgrading the firmware doesn't help.
&nbsp;
My conclusion:&nbsp; Hostname discovery remains fragile even in Windows 10, and there isn't much that can be done about that.

arul999 · Answer

The problem Im facing is i canlog into the admin page but i cannot map shared drive in network.

StephenB · Answer

arul999&nbsp;wrote:The problem Im facing is i canlog into the admin page but i cannot map shared drive in network.
To clarify - can you map the shared drive using the IP Address (but not the hostname)?&nbsp; Or is the issue that you can't map it either way.
&nbsp;
If the latter, then the most likely cause is that Windows silently removed SMB1 client support.&nbsp; Check for that in "turn windows features on or off".

Forum Discussion

RND4000 WIn 10 Unexpected Network error

9 Replies

Related Content

RND4000 WIn 10 Unexpected Network error

Unexpected Network Error with NAS 102

RND4000 v3

Dead RND4000 (ReadyNAS NV+)

RND4000

NETGEAR Academy

ProSupport for Business