Windows XP pro SP2 marks folders as read only (when they are not!)

[jereviscious]

Hi all,

I've encountered this new problem on my network:

Windows XP shows certain folders as read-only (when they are not)

I can run ATTRIB on the folder, and the read only attribute doesn't show up.
But when I view the properties of the folder there it is!

I un-check the read only backs and apply it to all folders and sub folders.
No luck. the damn thing re-appears.

When I log into the server and look at the folder, the folder does not have
the read only attribute checked.
Also, The Macs on my network have no problem.

I have to end up giving my Windows XP users full control of the entire
folder in order for them to save their files. I need to be able to control
the folder on a file-by file basis

I've also read this article http://support.microsoft.com/?kbid=326549 and
took all of the steps to resolve the problem. Nope..

THIS IS REALLY P*SSING ME OFF! I hope you understand.

Network file server is Windows 2000 SP4.

 

[Jim]

Hi all,

I've encountered this new problem on my network:

Windows XP shows certain folders as read-only (when they are not)

This topic has been done to death. The read-only marking of folders is well
known and wide spread.
The marking is perhaps the result of a bit somewhere in the header for the
folder that means one thing for files and another for folders.
Jim

 

[jereviscious]

Jim, thanks for your response.

Yes, I've seen that this topic has been done to death. I've seen several
threads which have mentioned that the read only folders mean "nothing", that
it is "By Design". I dispute this claim because of the following situation
that is occurring on my network:

One of the file servers on my network is totally locked down,
allowing domain users -Read and Execute, -Read only, and -List Folder
Contents. I need to give specific users -Modify permissions, so that they
can go in and change specific files.

So, the user with -Modify permissions, attempts to write to the
file. The user get's the error. "Cannot Write to File, The FOLDER MAY BE
MARKED AS READ ONLY!!!.

The only way I have of getting around this problem is to
give -FULL ACCESS to the entire folder to the user who only needs to modify
one (1) file in that directory.

I believe a recent security patch has caused this problem. Has
*Anyone* else encountered this?