Files and folders appear to be read-only in a shared folder (Windows 2003 Server)

I have a file server (2003 Storage edition). There are a few shares. Setup with Full control as Shared persmissions and Modify on NFTS for a security group.
Almost from day one, users complaint that, once in a while, they get a message similar to this:"File has been modified by another user, would you like to save a copy or overwrite? when they work with file like Excell 2003.  In Access 2003 database, a message may appear Could not save; currently locked by another user. Similar behariour occurs with folders.
I would blame Access internal settings if the issue did not span other files
It is a small office, so there is no change that the file/folder/database are opened by someone else. That includes me checking Shared Folder Management utility.
Any suggestions are appreciated.
Who is Participating?

Improve company productivity with a Business Account.Sign Up

pfarber22Connect With a Mentor Author Commented:
It appears that removing Mac sharing from a folder in question resolved the issue. I am waiting on the end users to test it.
Abhay PujariCommented:
My suggestion is just modify your shared and NTFS permissions again. Instead of granting everyone full shared permissions, add individual user and then grant required permission. Similarly repeat this for NTFS permissions.
Not a solution but we have the same problem when working with larger Excel files - this appears to be a file locking problem that has developed as our server has become older and computers faster. It seems to mostly affect the fastest PCs (and certainly my quad core).

As I said, this is not a solution but I would suggest that it is a functional problem (related to server capacity and PC speed) rather than a settings issue in Access or a permissions problem.

For us, since it mainly affects the two most technically savey people we tend to just live with it (I find that the files usually unlock after a short while anyway).
Building an Effective Phishing Protection Program

Join Director of Product Management Todd OBoyle on April 26th as he covers the key elements of a phishing protection program. Whether you’re an old hat at phishing education or considering starting a program -- we'll discuss critical components that should be in any program.

pfarber22Author Commented:
This approached recently worked for me, so I just did it and asking people to test it.
pfarber22Author Commented:
I my situation, it is a brand new Dell server and a Dell Optiplex 750, and relatively small files, so it shouldn't be a communication issue.
Thanks for a reply.
I think the problem is, folks move files to the DFS share rather than copy these files to them. What happens is they end up in the DFS space with the permissions of the file creator. So, the editor has no ownership of the file and therefore no control over it. I have thought about this from time to time on how ownership and file permissions are not followed with someone who moves files directly into the share. If this is a single folder, use things like "append these attributes to all child objects" and "allow all child objects to accept permissions from the parent folders".

pfarber22Author Commented:
I will check andapply your suggestion  if they are not there which seems very logical. Just for the record, there was no creation or copying. All issues occured on the pre-existing files.
I had this same issue and was able to overcome it. When building the DFS namespace, the default share permission for the entire namespace is Read Only. So, you may have to rebuild the namespace and when selecting the folders that your going to be using in the namespace, makesure you edit thes to grant either full control or read, write and modify.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.