flyboym535i
Level 1
(2 points)
Q: 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:47 AM
