ReadyNAS Shares keeps disconnecting from network

---

GawenT wrote:

 

Will the logs give any more clues where the issue lies if this is happeing on the NAS?

 

---

They might - have you submitted them to the mods for analysis?

---

GawenT wrote:

 

SMB 1.0/CIFS Automatic Removal is also checked, could this be unchecked?

 

---

When this is checked, then if a PC doesn't access the NAS (or another device that uses SMB 1.0) for 15 days, then Windows will disable the client.  It would then need to be re-enable via "turn windows features on or off".  If the client replaces the NAS with a newer model, then they should just leave the settings alone.  But if the NAS ends up remaining in service for a while, then it'd be good to uncheck it.

BTW, there is another issue with this NAS that will need to be worked out soon: it only supports an obsolete version of TLS.  Soon that will create issues reaching the web interface.  https://community.netgear.com/t5/New-ReadyNAS-Users-General/ReadyNASRND2110-not-supporting-TLS-1-2/m-p/1946376

---

GawenT wrote:

 

ALL clients are affected simultaneously, none exempt when the issue occurs.

 

---

That does point to an issue on the NAS. 

You could try turning SMB off and then on again in the NAS, and see if that is a workaround you can use instead of the reboot.  It won't fix the problem, but it would attempt to restart the SMB server in the NAS.  It would be faster if it works.

Have you tried re-connecting to a NAS share using the command line on a PC? I suspect it will fail, but probably useful to to confirm.

You'd run CMD, and then enter

net use * /delete /y
net use t: \\nas-ip-address\sharename /user:admin nas-admin-password

using a real public sharename, ip address, and admin password of course.  Be careful on the typing- particularly spaces and the slash direction.

The first command terminates any open SMB sessions; the second attempts to mount the share as drive letter T.

---

GawenT wrote:

 

Can you please advise how to post logs to the mods?

---

You upload the full zip file into cloud storage (google drive, onedrive, dropbox, etc).

Then send a PM (Private Message) to the mods ( JohnCM_S and Marc_V ) asking them to take a look.  You send a PM using the envelope icon in the upper right of the forum page.

Include a downloadable link to the logs in the PM.

---

GawenT wrote:

 

 

NAS has been in service for years, deselecting this is unlikely to resolve the issue as I am more inclined to this being the NAS than a client issue.

I agree it's not your current problem. The automatic removal wouldn't disable network share access on all the PCs at the same time - and if the SMB 1.0 client were disabled on a PC, rebooting the NAS wouldn't restore access.

---

GawenT wrote:

 

 

 

You could try turning SMB off and then on again in the NAS, and see if that is a workaround you can use instead of the reboot.

 

     -     Will this be per each share or can this (should this) be done globally?

 

 

---

I would do it globally.  I'm mot sure exactly how to do that an a v2 NAS (I don't own one, and the documentation doesn't include many screenshots).  But in other ReadyNAS there is a way to turn the service off and then back on.  You might need to renable it on all the shares after you turn it on.

The idea here is to see to see if the SMB service is hung on the NAS.

Are you comfortable using ssh?

Hi,

The client has a high performance desktop computer which had SMB1.0/ CIFS Server enabled (now disabled, no clue as to why this had been enabled), this was turned off for the last few days and while off the NAS showed (and continues to show) none of the issues.

I am monitoring the NAS however as there have been no issues as had been happening it seems most likely there as a conflict from this computer.

Thank you for the support, it is appreciated,