Snow Leopard and File Locking on Windows Server 2003 Shares.
Background:
I work for the Help Desk at a medium sized company. We have a small group of Mac users who are scattered between a couple of departments. Recently, we replaced about 7 user's old iMacs that ran Leopard with new ones that run Snow Leopard.
These users connect to a network share on a Windows Server 2003 file server and work with various files and folders. They have They have full access on the share permissions and read and write access in the NTFS permissions for the files and folders that they work with on the share. Up until they started working with their new computers, they had no problems.
_The Challenge:_
The users have started having issues when they're moving, deleting, renaming, or performing some other action to a folder or files in a folder that had been previously worked on by themselves or someone else at some point that day. When they try to complete the action, they'll either get prompted for the credentials of a local user with administrator rights, or they'll just get an error stating something like the following: +"You don't have permission to rename the item "foo"."+ If administrator's credentials are provided, they get the error anyway.
When I look at the open files listed on the share in the server, I see that the files and folders in question are locked by the last user who worked on them. So now when a user is unable to work with certain files or folders on the share, I have to have the last person who worked on the file or folder log out of their machine, or I have to manually release the lock from the server side. This is not an ideal solution for this issue. Does anyone have any suggestions that they could offer to resolve this?
_Extra Info:_
The Macs are bound to an AD domain.
The new Macs are all running Adobe Creative Suite 5.
Files are created, edited, and manipulated by a user, THEN moved on to the share.
All of the new iMacs are Late 2009 models and their OS is up to date.
The user's local accounts are not administrators.
_Stuff I've tried to resolve this:_
* Replacing the smb.conf file from Snow Leopard with the one from Leopard.
* Testing using an iMac that is not bound the domain.
* Using different shares than the one that the issue was first observed on.
* Testing using a local administrator's account on the iMac.
* Enabling/Disabling streams on the iMac.
* Contacting an Apple "Genius" who told me that it was a Windows problem.
I work for the Help Desk at a medium sized company. We have a small group of Mac users who are scattered between a couple of departments. Recently, we replaced about 7 user's old iMacs that ran Leopard with new ones that run Snow Leopard.
These users connect to a network share on a Windows Server 2003 file server and work with various files and folders. They have They have full access on the share permissions and read and write access in the NTFS permissions for the files and folders that they work with on the share. Up until they started working with their new computers, they had no problems.
_The Challenge:_
The users have started having issues when they're moving, deleting, renaming, or performing some other action to a folder or files in a folder that had been previously worked on by themselves or someone else at some point that day. When they try to complete the action, they'll either get prompted for the credentials of a local user with administrator rights, or they'll just get an error stating something like the following: +"You don't have permission to rename the item "foo"."+ If administrator's credentials are provided, they get the error anyway.
When I look at the open files listed on the share in the server, I see that the files and folders in question are locked by the last user who worked on them. So now when a user is unable to work with certain files or folders on the share, I have to have the last person who worked on the file or folder log out of their machine, or I have to manually release the lock from the server side. This is not an ideal solution for this issue. Does anyone have any suggestions that they could offer to resolve this?
_Extra Info:_
The Macs are bound to an AD domain.
The new Macs are all running Adobe Creative Suite 5.
Files are created, edited, and manipulated by a user, THEN moved on to the share.
All of the new iMacs are Late 2009 models and their OS is up to date.
The user's local accounts are not administrators.
_Stuff I've tried to resolve this:_
* Replacing the smb.conf file from Snow Leopard with the one from Leopard.
* Testing using an iMac that is not bound the domain.
* Using different shares than the one that the issue was first observed on.
* Testing using a local administrator's account on the iMac.
* Enabling/Disabling streams on the iMac.
* Contacting an Apple "Genius" who told me that it was a Windows problem.
iMac Late 2009
