NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RN 2120 Active Directory "Import Error"
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...
Think I've managed to fix this on my readyNAS. Granted it was a bit of a belt and braces approach based on google searches I did. Also I installed a vm edition of readynas os 6.5 and confirmed the file I delete is not on the base install after adding to AD domain.
so
1. cd /var/lib/samba
2. mkdir backup
3. cp -p *.tdb backup
4. confirm files in backup : ls -l backup
5. rm winbindd_idmap.tdb
6. reboot
After the reboot I used the GUI to redo my Accounts and they imported fine. I then rebooted and it still worked.
However I think my permissions on /home/<DOMAIN>/users are a little screwed as the idmaps have changed. so it's just a matter of running...
cd /home/<DOMAIN>
chown <user> <user>
cd <user>
find . -exec chown <user> {} \;
perhaps also need to do the same for chgrp too. Fixing file perms is easy peasy compared to the import issue.
Fixing permissions using SSH is not something we would support end users doing and if you encounter problems with that support may be unable to help. You can obviously compare with another NAS (if you have one configured and in a working condition) and if it works for you then good for you.
If you contact support and if required purchase support (if your unit is out of entitlement) then support can probably fix this in a way that the ownership is what it was before the problem (obviously this is not possible if you try doing your SSH changes you mentioned above).Finally support "kinda" got it working.
Not entirely sure what was done but I'm able to use AD..
Caveat:
- Can't see any of the users & groups through the device's ui
- Can't set permissions through the device's ui (which was the case before). All permissions must be set on the network share.
This gets me going for now BUT don't like it.
mdgm wrote:Fixing permissions using SSH is not something we would support end users doing and if you encounter problems with that support may be unable to help. You can obviously compare with another NAS (if you have one configured and in a working condition) and if it works for you then good for you.
If you contact support and if required purchase support (if your unit is out of entitlement) then support can probably fix this in a way that the ownership is what it was before the problem (obviously this is not possible if you try doing your SSH changes you mentioned above).Hello
Is it that the support of netgear?
A bug made by a firmware that is marked to "stable" on an original series that support 6.X and we should purchase support to correct this????I am a little bit disapointing...
The question is more: Do you plan to release a firmware to correct this????
I totally agree, expecting customers to pay to fix something that a Netgear firmware bug has caused is completely unacceptable and I am appalled by your approach. Especially if you're saying that a manual fix renders the devices unsupportable.
Netgear, you need to do one of three things:
- Issue a firmware update to resolve the issue
- Provide a supported manual fix
- Provide free support to fix the units that you have broken
And you need to do one of these pretty darn quick please, as it is becoming a major problem.
YOU have bricked these devices, YOU have a responsibility to fix them.
After applying SSH changes, I was able to sync with AD. However, when trying to connect to share, I am prompted for the password even after it is entered which I know is accurate.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
