Re: Ownsership and Rights

I have Everyone, Full Controll set up for bothe the NTFS and for the share.

Also, when I am logged into the server as Administrator, and I check the
properties of a file created in the share I'm having trouble in, I get

"you do not have permission to view or edit the current permission settings
for {filename}, but you can take ownership or change auditing settings."

Why as administrator can I not check the rights of a file? Advanced,
Effective Permissions does not work as well.

-vern-

"Lanwench [MVP - Exchange]" wrote:

Vern <Vern@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Thanks for engaging...

I have a partition thatis set up for all of the shares... and the
shares are set up to reflect the original Novell Server. The share
That I'm working on has share rights of Everyone, Full control...
obviously not a long term solution, but for now I just want it to
work.

Everyone = full control is fine, for the share. A lot of people leave their
share permissions wide open that way. They will be trumped/superseded by the
NTFS permissions.

There are a number of other rights set up on this folder, but
currently Everyone, Full Control is specifically set, and rights are
inheritable in the folder.

For NTFS, or for the share? The latter is what really matters.



-vern-

"Lanwench [MVP - Exchange]" wrote:

Vern <Vern@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
I've implemented a SBS 2003 in a small Land Surveying company... I
migrated their data via backup over from Novell, and the entire
server seems to work well.

The problem is a rights problem. I have defines a Security Group
that all the drafts people are part of, and sharing files works
fine, except when a person makes a new file. They are the owner by
default, and no one can access the file on the share until I force
ownership to Administrator or to one of the other users. Once I've
forced ownership, the shared file works fine. Even when I browse to
the file on the server to check ownership, I am forced to take
ownership before I can do anything with the file. Obviously this is
not a workable scenario... I can't tell the users... "OK, here's how
it works, make a new file, then call the Network Admin and have him
change the rights on the file, and voila, it'll be sharable." I'm a
tad frustrated.

Why does this happen? Is there a default policy somewhere that
precludes others from seeing the file? I can accept that the ID10T
problem is sitting in my chair, but I simply can't seem to find
resolution.

Ownership shouldn't make a lick of difference here.

Where's the folder? What're the share permissions, and what are the
NTFS permissions explicitly set and/or inherited from the parent?




.

Relevant Pages

  • Re: Utility/report for effective NTFS rights for a single user/group?
    ... that can determine the effective NTFS rights for a user or a group? ... Technically Rights and Permissions are two distinct things in NT-class ... simplistic in that you have to evaluate each folder individually. ...
    (microsoft.public.windows.server.general)
  • Re: Problem sending emails
    ... you may want to review the security you've put into place and undo it to see ... The 5.7.1 event you're seeing is usually a permissions related issue on the ... SMTP virtual server. ... This posting is provided "AS IS" with no warranties, and confers no rights. ...
    (microsoft.public.exchange.connectivity)
  • Re: Corporate File control
    ... How often are you finding you need to change permissions? ... do this - I set up the permissions on the folders when I set up the server, ... > minutia of NTFS permissions would be challenging. ... > find good documentation on NTFS settings? ...
    (microsoft.public.win2000.file_system)
  • Re: Corporate File control
    ... How often are you finding you need to change permissions? ... do this - I set up the permissions on the folders when I set up the server, ... > minutia of NTFS permissions would be challenging. ... > find good documentation on NTFS settings? ...
    (microsoft.public.security)
  • Re: appears to loose authentication
    ... me to think that there are security and permissions issues. ... to any shares below is baffling and also suspectable to incorrect NTFS ... an invalid DNS server in the Tcp/Ip settings. ... I checked the share and ntfs permissions on the goldmine share, ...
    (microsoft.public.security)