Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

HELP! Windows 7 users can map shares but can't open files

I have a new installation of OS X Server Yosemite running for a dozen mixed Macs and PCs in an office. The Windows users (Win 7 64bit SP1) can all map the drives and see all the files. The Windows users CAN create folders, create files, and delete files and folders. But they can NOT open any existing files on the shares.


That's right - they can do everything except OPEN a file.


If they try to open an existing file, they get an error essentially telling them that the file is locked because its in use by another user. They are usually (except for PDF) given a choice to open the file as read-only.


Errors we are seeing:

For PDF files: "There was an error opening this document. This file is already open or in use by another application."

For Word files: "File in use: [filename].doc is locked for editing by 'another user'." (yes,it actually says "another user")

For Excel files: "File in Use: [filename].xls is locked for editing"

For image files (e.g. TIFF): "Windows Photo Viewer can't open this picture because the picture is being edited in another program."


This is very maddening - the weirdest thing about it all is that all these users belong to a group that has full access to the file system. If we're talking POSIX permissions, the share is set to 770. I also have an ACL set up on all of the server shares for their group giving them full read, write and the inheritance flag is set. These permissions have all been propagated.


Example of my permissions on each share in OS X Server:

mygroup [ ] Administration [X] Read [x] Write [x] Inheritance (Custom ACL)

owner: read & write

mygroup: read & write

others: no access


All office users are members of the mygroup group.


For the first 24 hours, it seemed as if people could access the files. That's what's throwing me really. Now no one can open any existing files on the server.


Troubleshooting steps I have tried:

1) rebooting the Windows clients

2) rebooting the Mac server

3) re-propagating the permissions on a share in OS X Server

4) setting the permissions on a share for "others" to full access (i.e. 777 permissions) and propagating it

5) some local policy editing on a Windows 7 machine

6) shutting down all clients except one - and closing all apps - then trying to open 1 file (to ensure no one else was logged in)


No success with any of these approaches. I'm at a loss. I am honestly considering shutting this server down and installing a Windows server. I think I'd have fewer problems...


I'm hoping some benevolent administrator here has seen this before and knows a work around. For now, clients CAN open files in "read only" mode and save a copy - but the staff is impatient and angry about this. The server has become useless to the office staff until I get this fixed.


If you have a solution - or a suggestion - I'm desperate. Thanks in advance and Happy New Year.

Posted on Dec 31, 2014 9:46 AM

Reply
25 replies

Jul 16, 2015 12:59 PM in response to Bryan Navarro

I am running into the same situation, There was no solution to this post.

I have a new Mac Mini installation of OS 10.10.3 Yosemite Server 4 running for Macs and PCs in an office. The Windows users (Windows 8, Windows 7, and XP) can all map the drives and see all the files. The Windows users CAN create folders, create files, and delete files and folders. But they can NOT open any existing files on the shares. If they try to open an existing file, they get an error essentially telling them that the file is locked because its in use by another user. They can only open as read-only. Tried editing the local policy on a Windows machines but if this was changed logging in authentication was rejected.

Mac's running OS 10.8, 10.9, and 10.10 have no issues.




Errors we are seeing:

For PDF files: "File in Use by another"

For Word files: "File in Use by another"

For Excel files: "File in Use by another"

Word Pad: "File in Use by another"


I formatted the server and then reloaded from scratch, only creating one user, Does not mater if it is the Administrator or the single network user. I get the same issue trying to login to a different computer, MacBook Pro running OS 10.3.3. so it is a Yosemite sharing issue not a server issue. When I reloaded the Mini Server I tried sharing before loading the Server 4 software and the issue was already there. Mac's running OS 10.8, 10.9, and 10.10 have no issues.


Example of my permissions on share:

User uploaded file

In this case I login as mark the administrator.



Troubleshooting steps I have tried:

1) rebooting the Windows clients

2) rebooting the Mac server

3) re-propagating the permissions on a share in OS X Server

4) setting the permissions on a share for "others" to full access and propagating it

5) some local policy editing on a Windows machines but if this was changed logging in authentication was rejected.

Jul 28, 2015 2:15 AM in response to flyboym535i

I have the same problem. Setup a share with the correct permissions. Users can mount to a shared share on the network.

When one user accesses the files on the share there is no problem but as soon as the second person accesses the file it will get all kind of errors because the file is locked.

Anyone have an idea what is going on? It seems to be a problem with file locking in SMB. In older versions there were some options on how to do file locking but in the latest version (4.1) they seem to have disappeared.

Jul 28, 2015 4:16 AM in response to vst2001

Doing a "Get Info" on the file is where the lock check box is. I have had this happen twice where all users, Mac and PC came up with the error that the file is read only because it is in use by another person, but I restarted the server and things went back to normal, which in my case the Mac's are all fine but all the PC's still come up with the error. XP/Wondows 7/Windows 8, they all fail even though they were able to authenticate/log in successfully. Once in they can save a file, delete a file, but can't open an existing file. Is this exactly the same or is yours different in some way? I also tested sharing to a Yosemite Mac without Server 4 loaded and had the same issue. If I go back and look at the permissions they look OK.

I can not believe more people are not screaming?

Aug 26, 2015 7:44 PM in response to orbitus.cz

Have you tried this, it seems to relate to your issue

https://support.apple.com/en-us/HT203574



Did you check if the file is, in fact, open ?

If the file is: /Volumes/Data/Share/Presentation.ppt

run

sudo lsof | grep -i "Presentation.ppt"


If you stop filesharing and start it, can the PCs open files (right away, before others have a chance to open them)?


You have AFP users.

AFP has some nasty default settings which will leave files open when you sleep/disconnect. Easy enough to fix, but want some more detail before posting the specifics. You would see those files as still open in the first suggestion above.



Hope something there helps.


Jeff

Sep 8, 2015 12:11 PM in response to flyboym535i

Ok I just came across this problem. I am using a new MacMini with just OS X 10.10.5. NON Server. When PC's using Windows 7 Tried to connect we had the same issue. Kept saying files were open. I found on another site it seems to be an issue with all anti-virus setup to scan your network drives on the Windows 7 machines! As soon as I turned this off, BAM!! It work!! This seems to be the only thing that has worked for us.

HELP! Windows 7 users can map shares but can't open files

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.