I have two office locations, each of which has a ReadyNAS 2120 set up for storing location-based backups as well as serving up home folders for users. Both devices have been live for over a year and connected to our domain. For the sake of this discussion, Location A is where the primary DC (Server 2003) is located and Location B houses the secondary DC (Server 2008). Since Day 1, both NAS devices have pointed to the primary DC at Location A for the Directory Server Address. Time server and DNS settings were pointed to their respective DCs.
First-thing Monday morning, employees at Location B were unable to connect to their individual home folders. I reviewed the Accounts > Authentication page and it shows "Import error" under the "Authentication" heading. For the past two days, I have been trying to troubleshoot and resolve this issue, but to no avail.
Beyond what I know from working with these in the past, I've done quite a bit of searching online for answers to this problem and have tried all of the suggestions that I found, but nothing has gotten this issue fixed. Here is a list of things that I have tried:
- Location A's RN is working fine. So, I mimicked its DNS, time, and authentication settings.
- I removed the RN from the domain and then re-added it. It successfully joins the domain, but it fails while importing users and groups (i.e., "Import error")
- Instead of using information from the primary DC at Location A (i.e., original settings), I decided to use the secondary DC at Location B. So, DNS, time, and authentication settings all pointed to the secondary DC
- Everything in-between the three troubleshooting steps above
I also downloaded and reviewed the logs. I specifically focused on the ADS.log file. I believe the lines below are indicative of the problem, but I do not know where to go from here...
[16-05-24 11:48:12] 1918 rndb_account.c:963 info: 278 domain user found [16-05-24 11:48:15] 1918 rndb_account.c:989 info: 100/278 users imported so far [16-05-24 11:48:17] 1918 rndb_account.c:989 info: 200/278 users imported so far [16-05-24 11:48:19] 1918 rndb_account.c:1204 info: 278/278 users imported in 9104ms. [16-05-24 11:48:19] 1918 rndb_account.c:2262 error: Error. Fail to insert $home_folder/$user/$group/$group_has_user [16-05-24 11:48:19] 1918 rndb_account.c:2405 error: rndb_ads_account_import() ==> 3 (12360ms) [16-05-24 11:48:19] 1918 rndb_api.c:956 error: rndb_import_nolock() ==> 3 (12362ms)
At this point, I'm left scratching my head. I'm not sure what else to try other than backing up the data and doing a factory reset. Before I go that route, though, does anyone have any insight regarding additional troubleshooting steps I can take?
I appreciate any and all assistance. Thank you in advance and take care.
Hi, Im getting the same issue. The Nas was connected to the domain fine for a month or so, then we upgraded to Firmware 6.5.0 and how I cant import the Domain Users list any more. I get the same generic "Import Failure" error.
I've removed it from the Domain, re added it and all adds back fine but cant get it to Sync the User Accounts from AD/DC
Does anyone have a fix for this? I should mention the DC it based in the US and the NAS is in Australia. We have a direct VPN link to the DC/US Network
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?
It appears most of you have got current support warranty. I would suggest contacting support.
If you try leaving and rejoining AD then we won't be able to root cause what originally caused the issue in the first place until/unless we can reproduce this.
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.
I have an open support ticket with them now so hoping they can resolve the issue as staff havent been able to access it for over a week now and there are a lot of files on there that they need/
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.
Hello, i have got the same problem of everybody here on the same version (6.5.0).. I have got twice NAS 314, with the same configuration. In one all is ok, and in the second, same problem, it could not connect... It happen aftter the maj to the 6.5.0 all was ok before
If i try what you say, i have got an error from the sqlite commande:
"Error: no such table"
But in fact i have found a solution that work a time, but will not work if you refresh an other time the accout.
