![]() | ||
|
|
Snap Server / NAS / Storage Technical Goodies The Home for Snap Server Hacking, Storage and NAS info. And NAS / Snap Classifides |
![]() |
Thread Tools |
![]() |
#1 |
Cooling Neophyte
Join Date: Mar 2008
Location: Santa Cruz, CA
Posts: 2
|
![]()
I'm planning on using the Snap Server 520 we acquired to host home directories that will be mounted by network of RedHat Linux servers set up to authenticate against ADS, and which are simultaneously accessible from Windows.
Any suggestions on how I go about this? The ReadyNAS 1100 I have set up at another site makes this super-easy, by autocreating NFS exportable home directories the first time a user accesses the server from Windows. Do I need to manually create home directories in a particular share for each and every user? How do I set them up so that they're only accessible by the user in question? Feedback? Thanks! |
![]() |
![]() |
![]() |
#2 |
Thermophile
Join Date: Jul 2005
Location: Plano, TX
Posts: 3,135
|
![]()
Welcome to the ProCooling Forum. The home of the unofficial Snap Support. From what users have said this is it for the www. If your unit is new you have a 90 days free software support if you did not but a service contract with it. I suggest that you use it, and share your knowledge so others can learn. We have 1 users in particular that is mainly Hardware, Phoenix32. I try to cover the Snap and Guardian OS software side, but I feel I'm forgetting all of the SnapOS stuff to Guardian os stuff.
Someone with AD knowledge will have to answer that. But on the Guardian OS you need to be aware of 1 thing. Any, ANY user who has ROOT level files/folders/directories can browser the full server, whether they actually have admin rights or not. The def main share is setup that way. What you need to to is use the Security guide and create a new share that has the restricted access. Then you add users to a sub directory of the new share. Like I have a share called FTP, Inside thae FTP I have sub flolders with the users shares. So this prevents access to the root inturn can not browse. I did the same thing for my home users. Created a share called Users, add users subflolders, now there resticted. I have found that using the Security Guides work very well, once it is completed the shares are active. The Guardian OS supports MS AD, I do not have any experience in it, for mine is for home use. There are users here that do use it. The Help that buillt in is pretty good, though. I think all you have to do is add the AD server info in for it to authenicate users.
__________________
1 Snap 4500 - 1.0T (4 x 250gig WD2500SB RE), Raid5, 1 Snap 4500 - 1.6T (4 x 400gig Seagates), Raid5, 1 Snap 4200 - 4.0T (4 x 2gig Seagates), Raid5, Using SATA converts from Andy Link to SnapOS FAQ's http://forums.procooling.com/vbb/showthread.php?t=13820 |
![]() |
![]() |
![]() |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|