Ownership of drives and folders

Had some trouble with files and folders either not appearing on a
networked system, or yielding a "System Error, Code 5" (no doubt
related to authorization). I thought I had traced it to a problem with
ownership and sharing on the source system. Started to check various
folders and drives to see how the working ones were set. Surprise!
There is seemingly no rhyme or reason to it. Some set to "System",
some set to the local user, some set to admin, and some set to a code
string that was generated by who knows?

Anyway, I'd like to make some sense of why this is so arbitrary. Also
tried to set ownership from the root folders, to propagate through all
subfolders, and ran into "permissions" errors on just certain folders
and files--usually just one or two. Haven't figured out the cause of
that either.

The odd thing about this is that sharing once worked perfectly between
the two systems. No missing folders or permissions problems. Something
else must be arbitrarily changing status, and it's tough to say why.

In news:,
Chris <> typed:
> Had some trouble with files and folders either not
> appearing on a networked system, or yielding a "System
> Error, Code 5" (no doubt related to authorization). I
> thought I had traced it to a problem with ownership and
> sharing on the source system. Started to check various
> folders and drives to see how the working ones were set.
> Surprise! There is seemingly no rhyme or reason to it.
> Some set to "System", some set to the local user, some
> set to admin, and some set to a code string that was
> generated by who knows?
>
> Anyway, I'd like to make some sense of why this is so
> arbitrary. Also tried to set ownership from the root
> folders, to propagate through all subfolders, and ran
> into "permissions" errors on just certain folders and
> files--usually just one or two. Haven't figured out the
> cause of that either.
>
> The odd thing about this is that sharing once worked
> perfectly between the two systems. No missing folders or
> permissions problems. Something else must be arbitrarily
> changing status, and it's tough to say why.

I can't recall the details, but since SP1 I have noticed some changes in
that stuff - increased security.