Re: folder & file permissions isue
From: Bobby (bobby.creech_at_rauland-fl.com)
Date: 05/12/04
- Next message: Phillip Windell: "Re: unable to connect DSL to router WAN port - error 678."
- Previous message: Neil: "IP Routing & Subnetting"
- In reply to: Roland Hall: "Re: folder & file permissions isue"
- Next in thread: Roland Hall: "Re: folder & file permissions isue"
- Reply: Roland Hall: "Re: folder & file permissions isue"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 12 May 2004 08:57:51 -0400
OK, I think I got it working yesterday
I set the share permissions to Read/Change for everyone
Then went into security and took away everything but read for everyone
(don't want them creating dir/files in the root of Public, then went into
the REEVE folder and gave the accountting group full control. Seems to be
working. Quite a bit different than Novell rights...
guess I'm going to need to read the white papers or a book on Windows rights
management
thanks
"Roland Hall" <nobody@nowhere> wrote in message
news:Obbj4YAOEHA.3988@tk2msftngp13.phx.gbl...
> "Bobby" <bobby.creech@rauland-fl.com> wrote in message
> news:ez%238EI1NEHA.3312@tk2msftngp13.phx.gbl...
> : the root of the share \Public has everyone group with Read/File
> Scan/Execute
>
> Ok, perhaps we have a misunderstanding in terms. The confusion could be
on
> my end but I want to make sure you're answering what I'm asking so perhaps
> I'm not asking it correctly. So, I'll start over.
>
> File System Rights (Security Tab in Explorer)
> \public - assumes this is the folder name - has RX rights EVERYONE.
> \public\share - no inherited rights. accounting (global group) has full
> rights
>
> Share Rights (Share Tab in Explorer)
>
> What are the names of the shares? Do they duplicate the folder names?
>
> If I access the public share remotely using UNC and it is named public, I
> would use \\server\public. If this share only offers Read rights, then
file
> system rights are useless to me when accessing data via this share if I
need
> to make modifications. Consider the share as an outer layer to the file
> system level. It also works in reverse. If I have full rights at the
share
> but Read rights at the file system level, my EFFECTIVE rights are only
Read
> or LCD (Least common denominator).
>
> Have you set rights at the file system level AND at the share level?
>
> Another Ex.
> Can I have Read rights at \public, Modify (change) rights at \public\share
> (share denoting folder name and not variable) (BTW...I would not call a
> folder share but rather accounting in this case) and allow users to modify
> files in \public\share? The answer is it depends on how the access the
> data. If they come through a share called \public which only has Read
> rights, the answer is no. If they connect through a share called
> \accounting that has Modify rights, then the answer is yes. Also, a share
> called public could have modify rights that would allow this but that is
> poor design since public has a default of Read rights at the file system
> level.
>
> HTH...
>
> --
> Roland Hall
> /* This information is distributed in the hope that it will be useful, but
> without any warranty; without even the implied warranty of merchantability
> or fitness for a particular purpose. */
> Online Support for IT Professionals -
> http://support.microsoft.com/servicedesks/technet/default.asp?fr=0&sd=tech
> How-to: Windows 2000 DNS:
> http://support.microsoft.com/default.aspx?scid=kb;EN-US;308201
>
>
- Next message: Phillip Windell: "Re: unable to connect DSL to router WAN port - error 678."
- Previous message: Neil: "IP Routing & Subnetting"
- In reply to: Roland Hall: "Re: folder & file permissions isue"
- Next in thread: Roland Hall: "Re: folder & file permissions isue"
- Reply: Roland Hall: "Re: folder & file permissions isue"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
