File sharing between server 2003/08 and osx
I have 2 servers, 1 running Server2003 R2 SP2 and the other running Server 2008 SP2. We have 30 Mac users (mixture of Leopard (10.5.8 and Snow Leopard 10.6.7) who connect to shared folders on both servers and the problem they are having is that once they open up a file from within a sub folder on either server, close the application and attempt to move the parent folder (i.e. as it shouldn't be that folder, it should be located in another section on one of the shares) it will not move as the folder is showing as open in "open files".
I have tested with both servers, created a test share, duplicated some of the data and completed my testing from there. I have used multiple versions of OS X 10.5 and 10.6.
I have tested with both servers, created a test share, duplicated some of the data and completed my testing from there. I have used multiple versions of OS X 10.5 and 10.6.
I had another thought here: Mac OS is still a "dirty" OS in that it tends to leave hidden "turd" files when it access a directory, files like ".AppleDB" and ".AppleDesktop" for example. I also note some other invisible files that appear in the directory as well, all of which may be held open.
If the Mac is still connected to the server and has that directory window open, these files are may still be active, so the folder cannot be moved because there is still an active file reference.
Try having the Mac user(s) close the open directory window and then see if the folder can be moved. Not sure how long the OS holds on to those files.
If the Mac is still connected to the server and has that directory window open, these files are may still be active, so the folder cannot be moved because there is still an active file reference.
Try having the Mac user(s) close the open directory window and then see if the folder can be moved. Not sure how long the OS holds on to those files.
ASKER
Errubin,
I am testing it myself and the same thing happens when you either quit the application or just close the file.
Seems to be mainly caused by Adobe InDesign (have not tested any other Adobe applications) CS3, CS4, and CS5 have all been tested and the same thing happens. If the network share is disconnected then the folder becomes usable again - The "turd" files you are relating to will most likely be the resource fork which can be deleted, I have tested this but it again makes no difference.
Any other thoughts?
I am testing it myself and the same thing happens when you either quit the application or just close the file.
Seems to be mainly caused by Adobe InDesign (have not tested any other Adobe applications) CS3, CS4, and CS5 have all been tested and the same thing happens. If the network share is disconnected then the folder becomes usable again - The "turd" files you are relating to will most likely be the resource fork which can be deleted, I have tested this but it again makes no difference.
Any other thoughts?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
It might help to know what app(s) are causing this problem.