NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Encountered issue with 6.9.2
Been using RN314 for over a year, It has been working fine until this update. Noted that users were having issues with shares previously mounted after a few days, or could not mount them again aft...
I understand the "Underscore" issue but I have been using it in Unix based systems for about 30 years and It worked fine in the previous firmware 6.9.1 and there was no mention of the changed behavior in the change notes. It would have been nice to know before implementing the new version.
Also that does not explain the other issue of the "swap" space crash and log space rotation issue.
And the fact that group access no longer works after the update, All the group access information seems to be intact and no signs of corruption, it just stopped working.
wrote:
I understand the "Underscore" issue but I have been using it in Unix based systems for about 30 years and It worked fine in the previous firmware 6.9.1
Actually Netgear started enforcing the RFC character limits last April (in 6.7.1). Are you sure you upgraded from 6.9.1?
I agree it should have been in the release notes (and wasn't).
wrote:
Also that does not explain the other issue of the "swap" space crash and log space rotation issue.
And the fact that group access no longer works after the update, All the group access information seems to be intact and no signs of corruption, it just stopped working.
Understood. I think you'll need some analysis from Netgear on those.
I have been unable to find a way to report the issue of Groups no longer working on 6.9.2 firmware update. Do you have to purchase support to report an issue???
Anybody know how to submit a bug report??
Thanks
Which services are you running?
Which protocol are you using?
It would have been helpful to be able to have a look at the system before you reconfigured things.
When the problems started a few days after the upgrade from 6.9.1 to 6.9.2, and yes I am sure of the previous version. I tried a few time to rename the ReadyNAS by removing the underscore. Each time I made the change and rebooted it after confirming the change was made, it reverted back to the original name after the restart. Thats when I realized something was wrong and I used an ssh login to start looking at what problems were occuring and found that there were the errors described in my original post.
The group logins that were failing are all using SMB and running windows 10, I looked at the logs thru an ssh login while trying to login with a group account and it showed a successful login for the user account and then a failure to login to mount the group share.
The only changes made were to add share access for each individual account to be added to each share since the group logins no longer worked.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
