[K12OSN] 2nd Attempt: Having trouble getting write access to a Win2k drive...

["Terrell Prudé, Jr."]

Here's the way I handle this at work.

smbmount //winsrv/winshare /mnt/mymountpoint -o fmask=777 dmask=777 \
  username=mywindowslogon password=mywindowspassword

The security-conscious will say, "Hey, whassup with the 777 
permissions?"  Essentially, what you're doing is opening an unrestricted 
door to the Windows share, from the point of view of the GNU/Linux 
server.  This is not so from the point of view of the Windows server.  
Remember that the Windows share itself has permissions on it (you do 
have your NTFS and share permissions properly set, right?  :-) ), and 
the Windows server will say yay or nay to access based on its own 
permissions settings.

Now, this assumes that you want to use a common security context for 
your K12LTSP users to hit this Windows share.  This won't work so well 
if you need each user to be able to hit his own individual Windows share 
from the K12LTSP server, which is why most folks (including me) do it 
backwards--have Windows clients hit a Samba/NFS server running GNU/Linux 
or *BSD.

HTH,

--TP

Rob Owens wrote:

>Steve,
>
>I'm not sure about this, but do you have to change the
>permissions on the mount point itself?
>
>-Rob
>
>--- Steve Hargadon <steve.hargadon at gmail.com> wrote:
>  
>
>>Still crazy over this one.
>>
>>Here is my command:
>>
>>mount -t smbfs -o
>>
>>    
>>
>rw,username=student,password=abc123,uid=210,gid=200,umask=002
>  
>
>>//wind2ksrv/Students /S-Drive/
>>
>>When I "ll" the directory I get
>>
>>drwxr-xr-x  1  aharrington  students  ... S-Drive
>>
>>So it seems like everything is working except the
>>permissions.  And if
>>the root can get write permissions, I figure that
>>has to mean that
>>there is nothing from the Windows side getting in
>>the way here?
>>
>>Any help greatly appreciated.
>>
>>Steve
>>
>>-- 
>>Steve Hargadon
>>916-899-1400 direct
>>    
>>