NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
chriswe5t
Jul 17, 2015Aspirant
AD and occasional lockout on shares
Hello Long-time user and fan of ReadyNAS, but I'm wondering if the creeks are coming in a bit. I hope someone here can point me in the right direction. Problem- I have my ReadyNAS 314 (OS 6.2....
- Jul 27, 2015
JUST AN UPDATE FOR ANYONE INTERESTED :-)
I was performing some minor maintenance on the domain which basically entailed shutting down the backup secondary AD server.
I noticed that during this downtime the READYNAS locked me out of the shares despite the primary AD server still up and running. [As a reminder the Readynas was pointing to both primary for AD Sync and Time Sync and the secondary not even reference in the NAS admin]
From a server I typed in NET TIME and then I realised the the domain time was pulling from the secondary and not the primary DC.
As as short-term remedy (trial) I've pointrf the READYNAS to the secondary AD for both sync and time. So far it's held well and I think I might have stumbled across the answer.
I am by no-means an ADS guru but I need to understand how ADS roles differ and how a time drift can occur.
During a lock-out I'd even got the point of watching READYNAS time and Windows time and it seemed to be exactly the same. So not entirely sure how this might be the fix, but I suggest it an avenue to look at if anyone else is in a similar boat.
Cheers
Chris
chriswe5t
Jul 27, 2015Aspirant
JUST AN UPDATE FOR ANYONE INTERESTED :-)
I was performing some minor maintenance on the domain which basically entailed shutting down the backup secondary AD server.
I noticed that during this downtime the READYNAS locked me out of the shares despite the primary AD server still up and running. [As a reminder the Readynas was pointing to both primary for AD Sync and Time Sync and the secondary not even reference in the NAS admin]
From a server I typed in NET TIME and then I realised the the domain time was pulling from the secondary and not the primary DC.
As as short-term remedy (trial) I've pointrf the READYNAS to the secondary AD for both sync and time. So far it's held well and I think I might have stumbled across the answer.
I am by no-means an ADS guru but I need to understand how ADS roles differ and how a time drift can occur.
During a lock-out I'd even got the point of watching READYNAS time and Windows time and it seemed to be exactly the same. So not entirely sure how this might be the fix, but I suggest it an avenue to look at if anyone else is in a similar boat.
Cheers
Chris
BrianL2
Jul 28, 2015NETGEAR Employee Retired
Hi chriswe5t,
Hopefully it won't lock up again using your backup or secondary AD server. It seems that the you have isolated the issue. Please continue to monitor it.
Kind regards,
BrianL
NETGEAR Community
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!