Readynas 202 cutting in and out, it works then it doesnt work, but works on macs just fine

[delgado87]

current state:

Readynas 202 running os 6.9.3

computer running Windows 10 Pro version 1803

Issue:

opening the file browser in windows freezes and crashes and gives the error code: 0x80070035. Then after a moment the browser works and i can see the shared folder and it works fine. But if i close the browser and open it again it will give the error again and not let me access the files. before updating the windows the system worked perfectly. Is anyone else having this issue? on a side not there is a mac that is working along side with no issues so the readynas is working fine on the mac just not the windows computer

[StephenB]

Check that the network is classified on the Windows system as private.

Also, try disabling any internet security software that might be running on the PC, and see if that helps.

[delgado87]

Network is already set to private and disabling firewall and AV did nothing.

In the admin page I changed the eth0 settings for the IPv4 to static and assigned an IP address. Then in the file explorer I typed in \\192.168.1.100 and the shared files appeared. And in the network folder is now two icons: one is the NAS that does not connect and the new icon with the label of the static Ip which allows me to view the shared files with out freezing the file browser window

So the NAS was never disconnecting it seems to be having trouble with the the host name and the dynamic IP address and causing it to crash the file browser.

So by assigning a static ip and entering it manually in the file browser it allows me to access the files normallu again and does not crash the browser.

How can I fix this issue any further? I Would like to not have to manually type the IP address and Change the eth0 settings back to default.

[StephenB]

---

@delgado87 wrote:

So by assigning a static ip and entering it manually in the file browser it allows me to access the files normallu again and does not crash the browser.

---

Most routers let you reserve an IP address - letting you continue to use DHCP in the NAS.  So look for that feature - sometimes it is called "Address Reservation", sometimes "ARP reservation" or "Mac Address Reservation".  Reserving an address is better than assigning a static one - in particular when you shift to a new router, often the static address isn't compatible with the address range in the new router.

I also suggest going into the Windows credential manager, and looking for credentials that are stored for your NAS (either by IP address or hostname).  Delete any credentials that are there, and create two new ones - one for the reserved IP address, and a second one for the hostname.  Use a NAS account ("admin" will work), and the associated password.

Sometimes PCs are tempermental when it comes to resolving hostnames, though I haven't heard of a case where that actually causes a browser crash.  I don't have a great answer to that one.  But you can eliminate the need to enter the address by adding it as a "network location" in File explorer.  The problem here is that you'd need to add every NAS share as a network location.  Though if you used "admin" as your NAS credential, you can also use \\nas-ip-address\data, which will show you the complete data volume.

[delgado87]

To make a quick patch fix I created desktop shortcut with the static IP address and the folder path needed.

the icon with the host name in the network folder only works when I disable and enable the network adapter on the computer and when it comes back online the original method works but then crashes after a few minutes while the shortcut with the static IP address continues to work.

This issue was not happening before a windows update. There was no need for login credentials or setting the IPv4 to static or any of the work around that I am doing.

I would like to return to that state. Is my only option reverting back to before the windows update?

[StephenB]

---

@delgado87 wrote:

I would like to return to that state. Is my only option reverting back to before the windows update?

---

You could try the suggestions I made above   

Also, check if ipv6 is enabled on the RN202.  If it is, disable it.

You could also try enabling the SMB 1.0 client on the Windows PC, as that would also re-enable the older Windows network discovery protocol.

Once you have a reserved address, you could also try entering the NAS name in the windows host file, and see if that helps.  Generally I don't recommend that, but it will ensure that the system resolves the hostname.

As far as credentials go - guest access creates security issues with ransomware, especially for enterprises.  So Windows is tightening up on that.  You're better off just entering the credentials, rather than trying to fight it.  You only need to do that once per PC.