Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Active Directory Acces
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2015-01-17
07:59 AM
2015-01-17
07:59 AM
Active Directory Acces
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?
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?
Message 1 of 10
Labels:
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2015-01-17
08:20 AM
2015-01-17
08:20 AM
Re: Active Directory Acces
The NAS was using Active Directory before?
Message 2 of 10
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2015-01-17
08:40 AM
2015-01-17
08:40 AM
Re: Active Directory Acces
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.
Message 3 of 10
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2015-02-26
04:57 AM
2015-02-26
04:57 AM
Re: Active Directory Acces
Did you get this resolved? I am having similar issues
Message 4 of 10
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2015-02-26
09:11 AM
2015-02-26
09:11 AM
Re: Active Directory Acces
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
Message 5 of 10
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2015-02-26
10:01 AM
2015-02-26
10:01 AM
Re: Active Directory Acces
Hello,
A couple of individual things to check:
Bye,
Eskender
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
Message 6 of 10
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2015-03-09
12:08 PM
2015-03-09
12:08 PM
Re: Active Directory Acces
Has anyone found a solution to this? I have the same problems after updating to 6.2.2.
Message 7 of 10
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2015-03-09
01:00 PM
2015-03-09
01:00 PM
Re: Active Directory Acces
Hi,
funat120mph and erosenberg,
could you please confirm that none of the steps above solved the problem.
Thank you,
Eskender
funat120mph and erosenberg,
could you please confirm that none of the steps above solved the problem.
Thank you,
Eskender
Message 8 of 10
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2015-04-08
02:42 PM
2015-04-08
02:42 PM
Re: Active Directory Acces
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?
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?
Message 9 of 10
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2015-04-08
03:44 PM
2015-04-08
03:44 PM
Re: Active Directory Acces
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....
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....
Message 10 of 10