I really hope they fix this in the next FW. I've read and participated in many of the other threads where this issue has been discussed, so tried all suggestions etc., but I still have this issue and just toggle NAS off/on to sort it out when the problem happens.
I still haven't been able to nail the exact circumstances under which the Mede8er becomes inaccessible over the network, although it does seem to be after a period of time, rather than to do with anything I'm actually doing. Maybe it's a period of inactivity of the Mede8er, where it's switched on but not doing anything, or maybe it's MS Windows that's the culprit...who knows!
most of time is the target machine fault, in our case M8R NAS, but this is happen when the sender machine lost his connection for a while and try to reconnect..... it is a sort of chain : computer + M8R server faults.
to keep connection alive, i think , you could keep open a ping response from M8R ip (ping mede8er ip -t).
i dont know if will work for you , cause dont know the particular problem of your system and most of time it is very hard to identifiy them. i was not forgot about M8R server fault , he is the big problem here : he cant be wake up after connection lost. so, a ping should keep alive