Author Topic: TeraStation Pro 2 + Active directory groups  (Read 3282 times)

yttrium

  • Calf
  • *
  • Posts: 2
TeraStation Pro 2 + Active directory groups
« on: May 13, 2009, 09:15:31 AM »
   

Hello,

 

Sorry for my english, because I'm french...

 

I've got a big probleme with my TS2, working with Active directory (2003 domain), with the last FirmWare

 

If a user belong to 2 groups : "readers" and "writers" .

For a directory named "foo", if I set the read right for "readers" and the read/write rights for "writers", the user who belong to the 2 groups cannot write.

It seems like the read right was most important than the read/write : if you arein the same time in a read group and in a read/write group, you can only read...

 

Not the same that on a windows 2003 server.

 

Is there a solution to my big problem ?

 

 

Thanks, regards.


Jason

  • El Toro
  • ****
  • Posts: 315
Re: TeraStation Pro 2 + Active directory groups
« Reply #1 on: May 13, 2009, 10:10:20 AM »
Like most linux boxes, if a user in two groups, the more restrictive permission applies. So what you are experiencing is normal and to be expected. You would either have to create local users, or alter your groups, at least in regard to the terastation, there really is no way around this. It will ALWAYS apply the more secure, or lower level, restriction.

yttrium

  • Calf
  • *
  • Posts: 2
Re: TeraStation Pro 2 + Active directory groups
« Reply #2 on: May 14, 2009, 01:48:47 AM »
   Ok, so, anybody have an idea on how to solve this problem ?

davo

  • Really Big Bull
  • VIP
  • *
  • Posts: 6151
Re: TeraStation Pro 2 + Active directory groups
« Reply #3 on: May 15, 2009, 02:53:10 AM »
   Yeah only have the user in one of the groups, if you have it in one group with read/write and one with read only it will always drop down to read only!
Message Edited by davo on 05-15-2009 08:53 AM
PM me for TFTP / Boot Images / Recovery files  LSRecovery.exe file.
Having network issues? Drop me an email: info@interwebnetworks.com and we will get it fixed!