OrbusLLC
asked on
Macs (10.8) writing to Windows 2012R2 Shares
Hi,
We are having a real issue with our Macs writing to our new Windows 2012R2 file share. We recently moved it from 2008R2 and never had these issues. Basically I installed Windows 2012R2 and made the D: drive a share called Marketing. The file permissions are Everyone (Full), Domain Users (Full), etc. Basically, at this time everyone is Full to try to get this working.
Our users are using Photoshop and a few other Adobe products on their Macs. They can open the files fine, but when they save the file after an update (overwrite), they'll get errors like, "Could not save because write access is not granted."
Now if they save the file to their desktop and then copy it to the share (overwrite), it works! But that wastes time, etc.
We've tried everything from Full Access on everything for everyone to creating a second userid for her with Domain Admin rights. Same thing.
Any help would be appreciated!!
We are having a real issue with our Macs writing to our new Windows 2012R2 file share. We recently moved it from 2008R2 and never had these issues. Basically I installed Windows 2012R2 and made the D: drive a share called Marketing. The file permissions are Everyone (Full), Domain Users (Full), etc. Basically, at this time everyone is Full to try to get this working.
Our users are using Photoshop and a few other Adobe products on their Macs. They can open the files fine, but when they save the file after an update (overwrite), they'll get errors like, "Could not save because write access is not granted."
Now if they save the file to their desktop and then copy it to the share (overwrite), it works! But that wastes time, etc.
We've tried everything from Full Access on everything for everyone to creating a second userid for her with Domain Admin rights. Same thing.
Any help would be appreciated!!
ASKER
I will try and let you know! Thanks!
ASKER
It still happened, BUT I noticed the file was in Finder with a preview. I had her click off the file and save again and it worked! Maybe Finder preview was holding it opened?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I found that Yosemite fixed most of the SMB issues on Mavericks, but introduced some video driver and Finder issues that could be "fixed" with PRAM and SMC resets.
We had this problem as well and turns out to be a problem with Apple's implementation of the SMB 2.X/3 and Microsoft's implementation. Using CIFS forces the MAC to connect using SMB 1 and has solved this issue for all of our clients with the same problem.
** More information: It comes back to the the file locking mechanism and the way the MAC client holds the lock open on the file even after it has been closed. Again this is a known issue and the only workaround we have found is using the CIFS to access the share.