NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
dday1
May 30, 2017Aspirant
Cannot Access ReadyNAS 2100 shares on a domain
Hi I'm using a ReadyNAS 2100 [X-RAID2] using RAIDiator 4.2.15 firmware. I have it set up to use ADS and it was working great. Whenever I try to browse to the NAS using windows explorer, I get "Window...
JennC
Jun 05, 2017NETGEAR Employee Retired
Hello dday1,
You may need to provide complete information/details for the 2 concerns you have raised. Browsing to the shares of the NAS via CIFS/SMB first needs to have that protocol enabled and since you are planning to associate your NAS to the AD, make sure you have no permissions set on the shares. Maybe you can try going back to permission setting of the share you are having trouble with then Reset permission instead and see if that will help, here's how:

As for joining the NAS to AD, it would help giving us idea of the error and the settings you made that fails.
Welcome to the community!
Regards,
- mdgm-ntgrJun 05, 2017NETGEAR Employee Retired
There should be some clues in the logs zip download.
Btw RAIDiator-x86 4.2.15 is extremely old firmware. We're up to RAIDiator-x86 4.2.31 now.
The very next firmware release after the one you're running, namely RAIDiator-x86 4.2.16 added support for disks larger than 2TB.
- dday1Jun 08, 2017Aspirant
Hi mdgm,
It was working fine on that old firmware. Each disk in the nas is about 1TB. Would you still recommend updating the firmware?
I uploaded the logs to my dropbox here
- mdgm-ntgrJun 08, 2017NETGEAR Employee Retired
I would backup your data before updating the firmware. The remote updates would show the recommended firmware update path.
There have been heaps of changes since the firmware you're running. I wouldn't recommend sticking on such old firmware.
- dday1Jun 08, 2017Aspirant
Hi JennC,
The CIFS protocol is definitely enabled and it used to be joined to my domain, but now it isn't for some reason. The problem occurs for all shares and I can currently only access them using HTTP. I tried reseting the permission like you suggested, but that didn't change anything. I also made sure that there are no permissions on the shares
When joining to AD, the error is what I've stated above: "Unsuccessful joining the domain". Nothing in the logs and no other errors. The settings used are as follows:
Domain type: ADS
Netbios name: My domain name
Domain Name (FQDN): My full domain name (company.com)
New object OU: blank
Restrict accounts to OU: blank
Domain Controller: autodetect (I still get the error if I type in my DC IP address)
Domain administrator/Password: Domain admin credentials
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!