P
peter
I'm asked by a friend to set up two PCs (a windowsXP Pro and a windowsXP
Home) to share files.
What I do is create two folders on each PC, an incoming and an outgoing.
Files dropped into the outgoing folder (a local shared folder) will be
visible in the incoming folder on the other PC (a network path shortcut).
Each person only has read permission on the incoming folder content.
The other alternative is to set up only one shared folder on one of the PC
and allow both PCs to have read/write permissions. Of course this PC needs
to be on at all times. In retrospect this simpler approach may be easier to
manage for the users (don't have to worry about different versions of the
same file). Is there a better way or a standard convention to do this?
This is on a domain-less network, and each PC has an account set up for the
other user with identical name/password, and guest account is off.
Anyway, I run into a minor problem. On the XP Pro PC, default file
permission do not allow the other PC user to read the file, so each time the
user of the XP Pro PC wants to share a file, he has to manually add read
permission to the file for the other user, after dropping it into the
outgoing folder.
Is there a way to eliminate this step? The only way I can think of is to
change C:\ to have read permission for the other PC user, so that any files
created under C:\ will also inherit this permission. But this seems like an
overkill. Is there a way to cause the file permission to change
automatically when it is dropped into the outgoing folder? Since inheritance
works during creation, if I create a new file *inside* the outgoing folder,
it will inherit the read permission for the other user. But dropping a file
created elsewhere into this folder does not inherit this permission.
I did not use any wizards and I turned off simple file sharing, because I
want to know what is going on.
Home) to share files.
What I do is create two folders on each PC, an incoming and an outgoing.
Files dropped into the outgoing folder (a local shared folder) will be
visible in the incoming folder on the other PC (a network path shortcut).
Each person only has read permission on the incoming folder content.
The other alternative is to set up only one shared folder on one of the PC
and allow both PCs to have read/write permissions. Of course this PC needs
to be on at all times. In retrospect this simpler approach may be easier to
manage for the users (don't have to worry about different versions of the
same file). Is there a better way or a standard convention to do this?
This is on a domain-less network, and each PC has an account set up for the
other user with identical name/password, and guest account is off.
Anyway, I run into a minor problem. On the XP Pro PC, default file
permission do not allow the other PC user to read the file, so each time the
user of the XP Pro PC wants to share a file, he has to manually add read
permission to the file for the other user, after dropping it into the
outgoing folder.
Is there a way to eliminate this step? The only way I can think of is to
change C:\ to have read permission for the other PC user, so that any files
created under C:\ will also inherit this permission. But this seems like an
overkill. Is there a way to cause the file permission to change
automatically when it is dropped into the outgoing folder? Since inheritance
works during creation, if I create a new file *inside* the outgoing folder,
it will inherit the read permission for the other user. But dropping a file
created elsewhere into this folder does not inherit this permission.
I did not use any wizards and I turned off simple file sharing, because I
want to know what is going on.