PureBasic Forums - English

i feel somwhat (a lot ) stupid...

the following worked once, but no longer works, and i cannot figure out why

2 machines, both running xp pro sp2 uk

on machine one i log in (locally) as admin, password, proper rights, i can locally create and delete files, copy rename you name it

on machine two i log in (locally) as a user with FULL admin rights, i can locally create and delete files etc.

if i am on machine two and log in to machine one (exploring a shared directory) i can properly browse all files, copy new files to that directory, read anything in there, but i CANNOT DELETE OR OVERWRITE any existing files

i have checked rights, passwords etc. they are all configured properly

(can't call myself an absolute beginner, but this got me stumped)

any help would be appreciated

some additional information:

if i copy a file to the shared dir (from the client to the server) that's fine

if i immediately delete that file from the shared dir (using the clinet) it deletes

if i try to copy something over the existing file, it will not copy

once i've tried such a copy action, nothing goes

i am strongly suspecting some sort of cache in winxp? interestingly, the problem appears not to happen in 'simple sharing mode' and does not happen on sp1

did m$ make some serious change between sp1 and sp2? did i kill of one service too many? help would be appreciated (this is extremely stressing... )

You might be better off asking in Usenet... I doubt there's many users in
here that have 2 x XP machines linked together that can test it for you.

i know, i did post the question elsewhere as well, so far the results were not ecouraging...

blueznl wrote:...

Just to give you some pointers; there are 2 security mechanisms.

1. File Security

Apply both when working locally as when working over shares.

2. Share security

Each share is associated with security attributes that can override file security. Usually for Microsoft, "Everyone" got "Read" access. Even if File Security is on read/write, the share security applies (does not work the other way round, btw. If File Security says "Read", full access in the Share Security does not make writing possible.).


What can also be your problem is the user, XP uses to connect. Best to do for your need is kind of (on command line for example):

1. On PC 1

net use z: \\PC2-Name-Or-IP\ShareName /User:PC2-Name\Administrator

2. On PC 2

net use z: \\PC1-Name-Or-IP\ShareName /User:PC1-Name\Administrator


so you cross-mapped the Shares on the drive letter Z:

Somewhat I guess that your prob is the share security though; might be that some service pack or hotfix changed the default "Full Access" you were used to to "Read".

Edit / as I read your follow ups:

- if there is any virus scanner running, disable it for tests
- don't use the detailed view in the explorer
- there was once a known bug in XP which lead to such a strange behaviour & got ironed out in SP2
- There is a setting in the options, first tab, not to use tasks but "regular windows folders" (sorry, no english xp avail at the moment).

BTW, are that specific files (like multimedia files) where this happens or just any?

happens on any file, i will try your suggestion with including the pc
s name together with the users name

Please try also to delete files from command line.

max, the point is not that i cannot delete them, well, it is, sort of

i *know* how to delete unwanted files, but i do not know how to share a directory in such a way that both pc's have access to it, and can overwrite and rewrite files

that's a different thing

blueznl wrote:max, the point is not that i cannot delete them, well, it is, sort of

i *know* how to delete unwanted files, but i do not know how to share a directory in such a way that both pc's have access to it, and can overwrite and rewrite files

that's a different thing

Yes, I know, but as this

if i copy a file to the shared dir (from the client to the server) that's fine

if i immediately delete that file from the shared dir (using the clinet) it deletes

it appearantly doesn't have anything to do with file & share security, but with how XP handles files (or it just is a corrupt installation).

There are several things that can lock files (and hence prevent altering/delete them). One is 3rd party software - virus software, another good ol' windows explorer. Depending on the selected view and/or selected file, the explorer opens the file to get additional information about it.

If you try to delete from command line (or via a selfwrite program) and it doesn't work either, it doesn't have to do with the "features" of the explorer, so one possibility to scratch.

Have a look at this utility. This might help you get more information to see what process actually accesses the file in question:

http://www.sysinternals.com/ntw2k/freeware/handle.shtml