Working with AD

[rollo]

I've gone through the rather thorough documentation supplied with the unit and also available from thecus.com and I have been stumped on the process for AD authentication.

I went ahead and 'enabled' AD authentication via the web interface.

At this point I have no idea what to do. I have created shares, perhaps these need to be made 'public' in order to be seen in a windows environment?

I guess where I'm going with this is - how do I manage permissions on Windows shares?

I know everyone seems to have had issues at some point whilst getting started with one of these things but I still feel like this should be really obvious and I'm just not seeing it. Not a newb here either.

So even when you go into ACL's it's really confusing. You have the local users/groups and then ad users/groups. how the @#$ do you add an AD group here? or AD user?

gah...

thanks


*** update

Right, apparently when you configure AD though we have multiple DC's in the environment it only works correctly when pointed to the operations master. YMMV but this is what is happening in our environment. At this point all is as it should be with users and groups appearing properly in the ACLs.

[Arctra]

Cool! Glad you got it fixed. Do you want to maybe post something to that effect on the Wiki so others know in future? I would offer to post but what I know of AD is dangerous and it's always better to have someone that has the experience to write that stuff up anyway

Cheers

[rollo]

arbarbarb said:

Cool! Glad you got it fixed. Do you want to maybe post something to that effect on the Wiki so others know in future? I would offer to post but what I know of AD is dangerous and it's always better to have someone that has the experience to write that stuff up anyway

Cheers

Hi Arctra,

I've been keeping notes throughout this ordeal. I've got everything working again but I'm not anywhere near being satisfied. Once I get this cold I'll post everything up. There are too many little issues I keep coming across. I've started over, gone step by step through each, trying to nail down where the problems are coming from. I have to say, I am not terribly confident in this device just yet. I'd feel a lot better if the firmware version was .75 vs. 1.xx. As of yet I wouldn't recommend anyone get one of these and that's a shame because the potential is fantastic. Unfortunately my negative list is 10x longer than my positive one!

If not for this board.. *shudder*

Also - regarding my post above, I edited and added that to connect you must specify Operations Master. This doesn't seem to be the case, I've since been able to connect to multiple DC's but the connectivity is very buggy. Additionally, the release notes for .07 state:
If the ADS support is enabled, NAS will re-join AD when system (samba) service starts every time.
- Every time? Make sure the service is actually started (it may be enabled, but is it running?)
Fixed the problem that SMB/CIFS didn’t work after Load-Balance or Fail-Over enabled.
- Supposedly Load-Balancing and Failover aren't available on the N5200BR but they're available as an option on the LCD and when you enable either (if I don't do it now I'll just find out what happens when someone else does it later), guess what? SMB/CIFS does not function.