Forum Discussion

jorn

Aspirant

Nov 14, 2019

Solved

Arbitrarily lose access to network shares from window, mac and terminal server.

ReadyNAS 3138

Firmware: 6.9.5 Hotfix 1

All users accounts on ReadyNAS are handled from Active Directory, except for local admin. There are several shares om the ReadyNAS.

Windows pc’s, mac and terminal server (windows server 2012 R2) lose arbitrarily connection to the shares. When accessing the shares, from windows, one of two things happen: There comes an error message “network share is not available….” or the login window pops up asking for a password. When typing in the password the same login window pops up again and again. From a mac the login window pops up and asking for a password. When typing in the password the same login window pops up again.

There is no entry in the log files on ReadyNAS that can explain why this happens.

The only way that resolves the issue is to reboot the ReadyNAS. This happens every other day. Needless to say that this is annoying.

Any suggestion to solve this problem is appreciated.

jorn
Nov 27, 2019
Upgrading to 6.10.2 seems to work. It’s been a week now without losing connection.
Thank you for helping out, StephenB.

4 Replies

Replies have been turned off for this discussion

StephenB
Guru - Experienced User
Nov 15, 2019
You might try 6.9.6 (even though the release notes don't include a bug fix for your issue). It is the current LTS version of the firmware, and you could downgrade back to 6.9.5 later on if you wished.
- jorn
  Aspirant
  Nov 19, 2019
  Thank you for the suggestion StephenB.
  I did upgraded to Firmware 6.9.6. Still the same problem with arbitrarily losing connection to the shares.
  - StephenB
    Guru - Experienced User
    Nov 19, 2019
    jorn wrote:
    
    I did upgraded to Firmware 6.9.6. Still the same problem with arbitrarily losing connection to the shares.
    
    Upgrading again to 6.10.2 might make a difference (or not). The auditing feature in 6.10 might also give some clues. But downgrading back to 6.9.x isn't supported.
    
    Paid support ( my.netgear.com ) might be able to figure out what is going on, so that is a possible next step. You could also send a private message to one of the mods ( JohnCM_S or Marc_V ) with a downloadable link to the log zip, and ask them to take a look.