We have a ReadyNAS 516 which is used as our main source of fileshare/storage - We are a mixed environment of PC's (windows 7-10) and Mac's. We find that throughout the day we have regular disconnection of the fileshare, so users who are working on an exisitng document from the share are unable to save, and users looking to open files are unable to do so as the share does not seem to be live anymore. A couple of minutes later we find that everything connects again and works as normal. The status of the NAS is healthy, and all the drives are fine. There is no disk spin-down time enabled either.
Is there any reason as to why this is happening? What can we do ro rectify the issue? any help will be greatly appreciated.
Lets assume, that what you experience is not caused by the way your network infrastructure is setup.
Then the nas might be for a short time overwhelmed by the following activities and temporarily not respond to users' requests:
- There are scheduled tasks being kicked off during the day like scrub, defrag, balance or disk test
- There might be heavy workload caused by the antivrus service due to the way your users are accessing the files on the share
So, first I would make sure, that no scheduled tasks are running during the time you need the nas' capacity for your users. Second, if you can afford and antivirus service is running at the moment, switch it off for one or two days. Your users will probably let you know in case there is no improvement.
These are first guesses. Other community members might have more and better ideas.
fwiw I have one sitting at remote location with no server yet the comcast modem has ipv6 on by default (firmware does not allow disabling) which caused issues with lan shares. so possibly could still help disabling.
it does take full day of use to know for sure though.
yeah if running server 2012r2 or higher essentails (or full server with essentials role) you may need it.
I was lucky on the remote locations as my essentials connectors still worked fine with ipv6 disabled on all clients due to yet another comcast modem not following the stateful/stateless seettings and only trating the server 2012r2 essentials as ipv6 dhcp server.
however on the nas box itself I do not think it would matter realy, so interested to see if disabling works.
right here at home running 2 full server 2012r2 servers, one with essentials role and ipv6 enabled dhcp role second exchange 2013.
my modem bridged to netgear fvs336gv3 and ipv6 enabled on clients which are domain joined.
both my 104 and 314 nas units have ipv6 disabled with zero access issues including from 2 NON domain linux mint systems and 2 rasp pi units
Thank you all for your suggestions, unfortunately disabling IPv6 has not improved the situation. Users are all still losing connection to the NAS for a few minutes before regaining connection,
Dont think i'll be left with much hair at the end of this!
on one or two machines known to have the issuse can you disable ipv6 on them?
that way those clients as well as the nas would have ipv6 disabled and if those clients stop having issues you know to disable ipv6 on all clients or look at your router ipv6 settings.
