Active Directory Acces

[janekk]

Hello

After firmware update of my Ready NAS 102 from 6.1.9 to 6.2.2. My domain computers have no longer access to NAS via SMB. When i try to explore my NAS root folder via Windows Explorer windows ask me for user name and password, and unfortunately domain credentials doesn't work. Only NAS admin has access (user: NAS-NAME\admin password: admin) password.

How to resolve this bug?

[StephenB]

The NAS was using Active Directory before?

[janekk]

Yes without problems. I've click update OS in admin panel, NAS reboot and after this domain computers has no access to NAS via SMB.

[erosenberg]

Did you get this resolved? I am having similar issues

[Nhellie]

erosenberg wrote:
Did you get this resolved? I am having similar issues

did you try disconnecting from the AD, rebooting the NAS and re-establishing connection from the AD again?



http://kb.netgear.com/app/answers/detai ... -system%3F

[EskenderNG]

Hello,

A couple of individual things to check:

• Could you please try to reset the password for one of the users and try to connect again with this users credentials?


• Is the system time of the ReadyNAS still correct and equal to you AD server system time?


• Could you please check if the FW update changed your ReadyNAS DNS settings?


• In the ReadyNAS local admin page please head to Accounts >> Authentication and change the mark at “Do not cache the ADS accounts locally”

Bye,
Eskender

[funat120mph]

Has anyone found a solution to this? I have the same problems after updating to 6.2.2.

[EskenderNG]

Hi,

funat120mph and erosenberg,

could you please confirm that none of the steps above solved the problem.

Thank you,

Eskender

[savalentini]

I have the same issue with 6.22. I even tried downgrading to 6.21 and it didn't work.
When I try to integrate the ReadyNAS with AD it says "import error". The logs say there are a bunch of winbind parameters that are put in the wrong section "services" instead of "global".
Any idea what could be wrong?

[savalentini]

here's what the logs are showing:

Global parameter winbind enum users found in service section!
[2015/04/08 15:40:41.268476, 0] ../lib/param/loadparm.c:1662(lpcfg_do_service_parameter)
Global parameter winbind enum groups found in service section!
[2015/04/08 15:40:41.268559, 0] ../lib/param/loadparm.c:1662(lpcfg_do_service_parameter)
Global parameter winbind nested groups found in service section!
[2015/04/08 15:40:41.268636, 0] ../lib/param/loadparm.c:1662(lpcfg_do_service_parameter)
Global parameter winbind use default domain found in service section!
[2015/04/08 15:40:41.274086, 0] ../lib/param/loadparm.c:1662(lpcfg_do_service_parameter)
Global parameter winbind enum users found in service section!
[2015/04/08 15:40:41.274217, 0] ../lib/param/loadparm.c:

and it goes on and on....