RN 2120 Active Directory "Import Error"

Can you send in the logs zip files (see the Sending Logs link in my sig)?

Same problem and the same behavior with any domain of Windows 2003, 2008, 20008R2

sent logs.

I apologize for the delayed response.  I was traveling for the day and have been effectively "off the grid" until now.

I've e-mailed the logs per your request.  If there is any additional information that you need, please let me know.  I appreciate your assistance.

When the issue originally started, my ReadyNAS 2120 was running firmware v6.4.2.  In an attempt to resolve the "Import error" issue, I upgraded to v6.5.0, but that did not make a difference.

Furthermore, the RN 2120 at my other location (i.e., Location A) is working fine.  It, too, was running v6.4.2 and continued working after updating it to v6.5.0.  Both devices are connected to the same domain.  However, I've been tweaking the AD settings within the NAS, specifically time server, DC, and DNS for troubleshooting.  Initially, though, the settings were almost identical between the two devices aside from DNS.

I've been told that Netgear's engineers are reviewing the logs that I sent in.  I will report back with their findings if they can be of assistance to others.

Dirk, when you suggest turning off AD account caching, are you referring to the "Do not cache ADS accounts locally" checkbox on the Authentication admin page of the RN or a GPO change for the domain?

The engineers reviewed my logs.  However, they could not determine a root cause because I had removed the ReadyNAS from my domain, which muddied up the logs.

As of right now, all of my users and groups are appearing and the "Import error" is no longer a thing.  Refreshing the ADS accounts results in the "Import was successful" message.  I will confirm with my users that they can successfully access their home folders and other shares when they return after the holiday weekend.

I am waiting to hear back regarding what fix was implemented in the event that it can help others with the same or similar issue.  However, try to avoid removing the RN from the domain as a troubleshooting step and contact support first.  That way, they stand a better chance of determining a root cause.

- Chris

Just to reiterate, if you're experiencing the "Import error" issue, do NOT attempt to remove the ReadyNAS from the domain and then readd it.  This action prevents support from being able to find a potential common root cause.  If one does exist, a firmware update could likely be developed and released to prevent this from happening in the future.

Ultimately, support was able to remote into my ReadyNAS and resolve the problem.  The actions taken involved resetting a couple of things, which is why performing a factory reset appears to be resolving this issue for users.  So, save yourself the time and aggravation, contact support, and let them remote in.

- Chris

I don't recommend leaving/rejoining the domain... You could just have something strange cached. 

This might help from SSH -- use at your own risk.

# systemctl stop readynasd

# sqlite3 /var/readynasd/db.sq3 'delete from "$home_folder";'

# net cache flush

# systemctl start readynasd

Hi

I fixed this issue on my Ultra2-plus (unofficially running OS6). I upgraded from 6.4.2 to 6.5 last week and had the same import error.

On checking some of the posts in this thread it was mentioned about purging the contents on the db.sq3 database. On my system when I ran a select from the $home_folder table I found I had 1 entry which didn't match the $users table.

cd /var/readynasd/

sqlite3

sqlite> .open db.sq3

sqlite> select * from "$home_folder";

I had 4 entries of which one didn't match - the first field is user_id

32768|0|0||1

I confirmed that by using

sqlite> select * from "$user" where id = 32768;

if you have a dodgy entry or 2 then just use sql delete

sqlite> delete from "$home_folder" where user_id = <dodgy_id>;

ctrl-d exits the sqlite3

restart readynasd process using the commands from a previous post.