Re: File Share permission / read-only attribute

Tech-Archive recommends: Fix windows errors by optimizing your registry

On Wed, 15 Jun 2005 05:33:01 -0700, Damian Jones <DamianJones@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

>Hi Everyone,
>I've read some posts on this subject before this and I still comprehend so
>I'm writing to you.
>
>I'm from a netware background and now I'm migrating from novell to windows
>server2003. Right now the users are map to drive M: and from there the file
>permissions take over to allow access. ie. on the data volume there are subs
>for user directories, application data and forms. Is there a way to imitate
>this architecture? If not what is the best way to set up the file system?
>I'm pretty sure I can implement whatever as management is pretty easy going
>as long as I can train the users.
>
>Basically what I need to to make sure only the group defined is only group
>that can read or change the data.
>
>
>On the other front I am trying to create a DSN and get an error which I
>suspect is because the directory is marked read only even after I have change
>the file share permissions and the security to full control. The question is
>why does it still show the read only?? and how can I have this set to write
>able?


Windows Server 2003 with Service Pack 1 support Access Based Enumeration.
See the following tips in the 'Tips & Tricks' at http://www.jsifaq.com

JSI Tip 9231. Windows Server 2003 SP1 supports Access-Based Enumeration of a shares sub-folders?

JSI Tip 9441. Windows Server 2003 Access-based Enumeration tool.

.