I have a problem with personal shares on wd ex4 and user in active directory.
The join between nas and active directory goes successfully; I can see all a.d. users and groups in ex4 interfaces but when I share i folder with ad user or group, the user can’t access: wd ex4 request authentication (?) so I re-input my user and password but doesn’t work.
I verify:
→ Time
→ Map directly to “personal share” without open the public share
→ Samba version 2
→ Only one lan connected with static IP
→ Upgrade wd ex 4 firmware version (1.05)
→ Turn off all
→ Read forum and manual!
→ In wd ex4 log is registered the failed logon with mydomain\myuser
same here! what kind of test process has WD got if they only test a new firmware without testing upgrades? at least they solved my problem with AD and link aggregation in the latest firmware, took long enough. just another example of selling enterprise features which obviously have not been tested in combination at all.
apart from that, the latest upgrade duplicated all shares (*_2) to accomodate local as well as AD users, whereas previously only one of the two option was available at the same time. If you change such a feature please document it in the release notes, I couldn’t find it there! This is a security issue, suddenly my NAS allows more access by permitting AD+local than before (AD only). The local users on my NAS were testing users with generic passwords before joining AD.
I’m going to reset to factory and build the config from scratch hoping the workgroup-nonsense is gone and doesn’t reappear in my smb.conf after a reboot.
ok so, starting with a fresh configuration didn’t help, the workgroup line is still being put into smb.conf and causing the problem. I remember this line being there with the older firmwares as well, but never really caused a problem in the past.
anyways, to work around the problem, you can simply enable SSH and run the following commands on the EX4:
WD: please fix ASAP. I’m not sure if everyone using AD is affected (would somehow expect more complaints, but maybe “real” enterprise users also use real enterprise products…), or could there be something special about our AD configuration?