Access Denied Error Sharing Some Files

[PXA]

I have a client who has two newer systems, both running
XP Home Edition with all the latest updates (I'll refer
to them as systems A and B.) Both systems have folders
shared using simple sharing. Copying and accessing stuff
from system A on system B works fine, but not the other
way around. Most of what my client accesses is stored on
system B. Some files work, but most of them will only
open as read-only and trying to copy them from system B
to system A results in an Access Denied error. These
documents all open fine on the local system. None of
these files are set as read-only and do not use any
special characters in their filenames. I have never seen
this before and nothing I have tried to resolve the
problem has worked. Does anyone know what can cause this
and what can be done about it? Thanks all!

 

[PXA]

After doing some further research, I am going to try a
solution that's a bit radical (and well, that I shouldn't
have to in the first place), but that might work.
Everything I've managed to find that even remotely sounds
like this problem seems to be tied to issues with NTFS
file permissions. Now, you aren't supposed to be able to
change these under XP Home, but problems can still arise
from them. Using PartitionMagic 8.01, I am going to
convert the drives FROM NTFS BACK to FAT32. This
eliminates all the security credential nonsense that is
for now, the only thing I can blame this on. FAT32 is a
lot less stable, but my client is willing to use it if it
fixes the problem. Maybe once all the security
information is cleared out, the drives can be converted
back and all will be fine. This is ridiculous though,
that I should have to downgrade to an inferior file
system simply because of further bugs that
security "patches" create. Regardless, I will report in
once I've tried this. Here's hoping...

-----Original Message-----
It would be really nice if someone would come up with an

explanation for this. I have a client with a similar
problem except that both A and B have the same problem.
If a file has been opened and closed on one machine then
the other machine can no longer access it. Even stranger
is the fact that they can't even open a file on the other
machine with a similar name. (e.g. if Stevens-Bob.wpd has
been edited, they can't open Steven-Bob.rpt either - even
if the latter hasn't been edited!). Attempting to copy
the file somewhere else results in an 'insufficient
rights' message, clearly a ludicrous message since they
can copy other files in the same directory.

It seems to me that every 'security' patch issued by MS

is generally accompanied by a deterioration in network
manageability/performance. I have had clients who found
that after an update all other computers in their
workgroup disappeared and/or somehow their workgroup had
mysteriously reverted to MSHOME.

 

[PXA]

Hmm...that's not the exact problem I am having, but it
looks close enough. I'll definitely try out the
workaround. Of course, the REAL fix is one of those
things you have to get from Microsoft directly. I've
tried those before and the reps on the phone do everything
they can to try and still get a per-incident fee out of
you, even though they are supposed to waive it if the fix
is applicable to your situation. I will try this solution
out before my other one and report back my results on both.

 

[Guest]

I don't have access to the client's machin(s) at the moment but I will check this. I notice that on my own machine this regkey does not exist. (of course this doesnt mean that there isn't a default value for it in the OS somewhere!)
I do a great deal of database programming and the newsgroups that I haunt are filled with messages outlining problems with opportunistic locking. In my personal opinion, caching lock tables is like saying 'I hope this gun isn't loaded'.