longjohns

since networking my 2 computers, (simple peer to peer with a crossover cable) i have had problems sharing files. i have set up a few different shares and can get files across the network, but:

1) i had to add full access for "everyone" in order to do it, and
2) new files i put in the share folders can't be accessed until i go into the security settings, check "replace permission entries on all child objects with entries shown here that apply to child objects", and say OK to the resulting dialog. so i have to do this every single time i drag a file into a shared folder, or i get 'access denied' when i try something from the other computer.

as far as 1 - it seems less than ideal from a security standpoint, although in my case it's not very important since it's just me. but i'd feel better about being on the net, even though i've got software firewall running that's hopefully keeping the nasties off the gateway and therefore off the client comp too. i haven't found any options for adding users of OTHER computers in the security settings, just for the computer i'm on at the time. hence needing to use "Everyone"

as far as 2 - i must be doing something else wrong, this isn't how it's supposed to work~!

helps??

thx

peacy

Try to use the same username/password on both machines.
(Don't have XP, but this works on NT4/2K...)

longjohns

ok i'll try that. thank you

longjohns

that did not seem to help. any other ideas?

bueller?

bueller?

;-)

rubicon

A few drinks tonight so pardon the clarity...

Windows networking has two levels of permissions: share and file level. The first, your #1, is the share level permission. This permission is the first "gatekeeper" that overrides all others. Thus, if you want to give someone Write access to a file, you _have_ to give that permission in the share. For almost all cases, you can give Full Control to Everyone in a share. If you give Read access to the share but Full Control to the file, you'll only have Read access because of the share permission.

The NTFS permissions at the file level will dictate what you can do with the files. Thus, you can give Full Control to the share yet Read-only on the file and Read-only is the resultant permission.

From a simplicity standpoint, you can give Full Control on the share and assign the exact permission you want on the files. If you like, use Authenticated Users instead of Everyone.

Lastly, your firewall will protect you because by default it doesn't allow access to the shares. Thus, you can create shares for you LAN but as long as you have a tight firewall you have nothing to worry about from the 'net.

__________________
How you do anything is how you do everything.

Peetster

You failed to mention (or I missed) the version of XP you are dealing with. XP Home Edition is not designed to, nor will it ever participate in a domain. I'm sure this is somehow important to your problem.

longjohns

xp pro

the thing that upsets me is that somewhere in windows, it says "to share this file, drag it to the shared documents folder" - but for me right now, it's more like "drag to the shared documents folder, then open the permissions page, hit 'advanced', click the checkbox, etcccc" EVERY TIME YOU ADD A FILE

this <i>can't</i> be the way it's designed to work. for one thing, nobody on a network could share new files they were creating, because (unless i'm wrong) only admins could be going in and setting these permissions. i guess i could test that by creating another user account without admin rights.

longjohns

so yes, what you are saying is exactly what is happening to me - the read-only nature of the file is overriding the share permissions. it just seems that there must (at least ought) to be a way to have the act of bringing a file into a shared folder to automatically change its permissions.

now that i'm thinking about this from an admin/ reg user POV, i can see how this would be problematic. but still! ;-)

rubicon

I have never used Windows' drag and drop into the Shared Documents folder. However, you're dealing with the inheritance issue of XP. NTFS handles a file copy differently than a move.

For example, if a folder has Full Control rights assigned to Everyone and you move a file with Read (only) permission into the Full Control folder, the file will remain as Read only. You must COPY the file to inherit the Full Control permission.

You see, if you move a file it will retain its original permissions. I always recommend copying the file instead. As well, you must have inheritance enabled in the destination folder, altough by default, it is.

__________________
How you do anything is how you do everything.

longjohns

you know, i'm starting to wonder if this stuff i remember reading about the shared documents folder was just a reference to sharing on a particular computer, i.e. between different users, and not between different computers on a network

and also, i just tried copying the files instead of moving them, and it seems to work!

thank you! :-)

rubicon

Good deal.

__________________
How you do anything is how you do everything.