qazmlp1209@rediffmail.com wrote:
Possible causes are:
o How the remote drive is being shared ("Read Only" access flag set? "Allow everyone" to write enabled?)
o The kind of OS your colleague is using ("Home Edition" has limited share abilities vs. "Pro")
o The ACLs on the directory(s) and/or file you created
o Are you and your colleague's logins both in the same 'Group'?
Depending on how the remote drive is shared, that may affect
the write access available to other users.
If your colleague is running 'Home Edition' of one of the Windows OS's,
they might have problems with access that you don't have with eg. Win2K or "XP Pro".
The ACLs (Access Control List) on the dirs and files control how
read/write access permissions are enforced. Among other things,
the ACLs on the directory(s) the file is in can affect the perms
assigned to files written in those dirs via 'inheritable' permissions.
See the docs on how ACLs work.
I like to use the DOS 'cacls' command (Change ACLS) to look at the ACLs
of files and directories; if you only supply a pathname as an argument,
it will print out the ACLs for the specified file or directory. eg.
from your colleague's machine:
cacls \\path\to\remote\file
..and look closely at what the ACLs indicate. See 'cacls /?' for help
on the command's usage.
Part of Window's security mechanism is based on group memberships.
See if both you and your colleague share membership of the same group.
Note that the ACLs on the directory above can indicate 'inheritable'
permissions, so that eg. when a file is written to the drive, it is
only writable by its owner.
There might be other reasons, but those come to mind almost immediately.
Best thing is to look at the ACLs, and your login group memberships.
