NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Lost AD Connection after updating to 6.5.0 on Readynas 516 #26926627
Hello,
after updating my Readynas 516 from firmware 6.5.0-T338 to 6.5.0 final release, I am getting 'Failed to sync ADS account information for the realm' messages.
In the past, there was...
DirkG, please don't run beta 6.5.0 firmware anymore. We are very limited in what we can do to help if you stay on that here and support won't be able to help with that firmware. Please update back to the 6.5.0 production release and open a support case, attach your logs to that case and let us know the case number. Thanks.
When users encounter this issue and do things to try to fix it themselves we lose the ability to get information that would help with identifying the root cause of the issue (so it's much harder to try to find a common cause that could lead to a fix in a future firmware release if that's needed).
Hello JennC,
please be aware, that there are more users with the same problem:
https://community.netgear.com/t5/ReadyNAS-in-Business/AD-DC-Import-Error/m-p/1091108#M4881
Moreover, I have already sent my logs.
In additon some observations:
- There was no problem with 6.5.0-T338
- The problem appeared after updating from 6.5.0-T338 to 6.5.0 final
- Downgrading from 6.5.0 final to 6.5.0-T338 has not restored the working conditon
- You can access folders after disabling AD caching on the Readynas and logoff/logon on your windows machine, but not the automatically created UserFolders, which already exists
- You have access to UserFolders, which are created automatically after the switch to 6.5.0 final
From my point of view, there was something mixed up with the management of the SID from the AD within the Readynas while upgrading to 6.5.0 final.
Best regards
Dirk
DirkG, please don't run beta 6.5.0 firmware anymore. We are very limited in what we can do to help if you stay on that here and support won't be able to help with that firmware. Please update back to the 6.5.0 production release and open a support case, attach your logs to that case and let us know the case number. Thanks.
When users encounter this issue and do things to try to fix it themselves we lose the ability to get information that would help with identifying the root cause of the issue (so it's much harder to try to find a common cause that could lead to a fix in a future firmware release if that's needed).
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
