Currently Being ModeratedJul 27, 2010 9:50 AM (in response to abner goodwin)Were you ever able to solve this problem. I'm having similar issues since upgrading to snow leopard. Four macs connect to a Windows Server 2003 for shared files. Each user has full permissions & when we "get info" it shows read & write permissions. Two of the computers were running 10.4, two were running 10.5. Everything worked properly until upgrading to snow leopard. Some files let me copy, move, delete. Others either just hang up or we get a "no permission" error. Also getting a "pdf is in use" error, even when the file/folder doesn't contain a pdf. We had our IT rep check the server who said everything is in working order. They don't represent macs any longer but feel that it's a mac problem. I would have to agree since this problem only started after the upgrade, and the one machine that was not upgraded (still running 10.5.8) is not dealing with these problems.
Lastly, I would install 10.5 back on all of the computers if I could, but the leopard disk that came with one of the computers wouldn't work with the 2 machines running 10.4 and I didn't see it available at the apple store. I'll buy it if it's still available, but why wouldn't the disks that I have work?
Thanks for any helpMac Pro
Currently Being ModeratedAug 9, 2010 6:11 AM (in response to abner goodwin)I'm also having a similar problem, but only with new folders created by the user on the Snow Leopard machines. We typically connect to the Windows shares via SMB or CIFS and I've seen the problem with both. Right now, we're working around it by having the users do a Get Info on the folder and unlocking the lock under Sharing & Permissions.Mac Pro, Mac OS X (10.6.4)
Currently Being ModeratedAug 18, 2010 11:48 AM (in response to Holly Anne Balish)Same problem here; only difference is we have a Linux Samba server rather than a windows server.
The Mac shows no locking or read-only tags, but windows users see the files as read-only. It generally just happens on directories that are created by the Mac.
Files and directories can be deleted from the Finder or SMBCLIENT on the Mac.iMac 27", Mac OS X (10.6.3), Smb file locking
Currently Being ModeratedOct 8, 2010 3:02 PM (in response to abner goodwin)I have the exact same problem. This has been going on for months now. My Snow Leopard machines try to copy working files up to a 2003 Windows SMB file server and they get a "no permission" response. This happens copying, moving, and renaming files on the server. It's not a 100% thing either, but it happens frequently. When it does happen, I notice through a Windows Free application called Unlocker identifies the files as having been locked by the SYSTEM process with PID 4. I can unlock the files and then the user can copy their data, but a few hours later it happens again with a different folder. There are posts all over the web with similar issues like this, but no one has any sure-fire solutions. My Mac users are beginning to lose patience. I need something soon. Any ideas would be appreciated.Mac Pro, Mac OS X (10.6.4)
Currently Being ModeratedNov 3, 2010 2:07 PM (in response to abner goodwin)We're getting the same thing. Our Windows server is 2008 instead of 2003, but otherwise the symptoms are identical. Dismounting the drive from the Mac running 10.6.4 closes the phantom file handle, but that's obviously not a long term solution since it interrupts work and requires closing any legitimately open files first.
Maybe 10.6.5 will improve the situation? I'm seeing rumors it should be out shortly.Mac OS X (10.6.4)
Currently Being ModeratedJan 7, 2011 9:29 AM (in response to abner goodwin)Hey Guys.
Try this/ go in to sharing and turned on file sharing then options....
Turned on Share files and foulders using AFP and SMB option on.
Give Users: read & write2x2.4 Q 12 GB 2T, Mac OS X (10.6.5), Happy Mac
Currently Being ModeratedJan 11, 2011 1:44 PM (in response to abner goodwin)Has anyone tried the above fix? (I will be trying it tonight on a few machines I'm having a simillar issue... (CIFS file share :/)
Here is another suggestion from a forum:
On the server share giving you problems in the security settings>advanced>owner select other user or group and type network service. Make the owner "NETWORK SERVICE" and check off replace owner on subcontainers and objects. I tried both xls and doc files and they both saved to the SMB directory and also to subdirectories of the shared directory after I made this change. I'm running 10.6.2 on the Mac and WinServer2003
Message was edited by: jg.gt11Fujitsu, Windows 7, MBP Intel Core 2 Duo SL
Currently Being ModeratedFeb 2, 2011 5:25 PM (in response to abner goodwin)We are having the same problem. The tough part is that it happens so randomly. It mostly happens when a file on the DC share is moved/edited. We will be moving the shares to a Mac-mini and sharing over afp. Our design group is wasting too much time with the current set up.imac, Mac OS X (10.6.5)
Currently Being ModeratedFeb 15, 2011 11:08 AM (in response to abner goodwin)Has anyone found a working solution for this yet, I have the same issue as Abner goodwin, and have not found a workaround yet, except if we wait a day or so, we are free to do with file/folder as we want. that is not feasible.
If anyone has found a working solution, please post.
ThanksMacBook Pro 17 Corei7 2.66, Mac OS X (10.6.6), imac 21.5 Core i3 3.2 & Imac 27 Core i5 3.2
Currently Being ModeratedFeb 21, 2011 1:06 PM (in response to MacMan08)I have Windows7 -server at home. I was just running to the same problem all the time.. couldn't rename or edit files... I surfed to my Win7 screen and took Indexing off from that external disk I'm accessing.
just unchecked 'Allow files on this drive to have contents indexed in addition to file properties' ... now it's working again!
Hope it helps somebody.
Br, Michael KiMac, Mac OS X (10.6.6), Win7
Currently Being ModeratedFeb 22, 2011 4:27 AM (in response to abner goodwin)For everything else then occasional ad-hoc file access from Macs, don't use CIFS, period. Use AFP with an AFP server of choice.
Currently Being ModeratedFeb 22, 2011 2:20 PM (in response to MacMan08)MacMac08,
The problem has to do with how the Mac OS does file open calls for things like quicklook. I used to run into this issue at a client site, before I was able to convince them to use Thursby's ADmitMac. Since getting them updated to the latest version, the errors went away.
If you don't need the full Active Directory package, they have another product, DAVE, that is just a replacement for Apple's SMB (and includes DFS support).
Just my $.02Imac Core 2 Duo, Mac OS X (10.6.6)
Currently Being ModeratedNov 1, 2012 10:31 PM (in response to jg.gt11)
Bingo! Thanks jg.gt11
This worked for me. I was getting permission errors when I tried to open files from Macs running Snow Leopard and Lion, that were stored on a Win2008 R2 server.
Interestingly, you do get some error messags but if you plow ahead it changes ownership to Networ Service and permissions are established for Mac