I'm having a Network Share provided by a Mac OS X Lion Server on a recent Mac Mini Server (CIFS / SMB); mounting the share in Windows (XP) is no problem, reading and writing neither. But when ever I try to execute an executable .exe, Windows complains that it's not a valid win32 executable.
Copying the file from the network share to the desktop or some other local location, allows the file to be subsequently executed.
Pointers to what the root cause of this problem may be are greatly appreciated.
Windows XP cannot execute binary file on Network Share
mac-osxmac-osx-servernetwork-shareserver-message-blockwindows
Related Solutions
Best way I've found so far is that you can browse the snapshots from Finder:
- Open finder & navigate to the share
- Click Go, Go to Folder, & type .zfs
- Click into "snapshots"
- From there you can drag & drop the files back to the share.
The problem with this is a lot of times Finder will kick you out of the .zfs folder back into the top level directory of the share. I'm not sure how to get around this. I'd also like to see a better way.
edit
Just realized you can set the zfs snapdir to visible & Finder won't kick you out:
zfs set snapdir=visible your/zfs/file/system
If it works the way that Office does on Windows, which I'm assuming it does...
This file is essentially the temporary file that holds current edits and details in the event that the program or computer crashes mid-edit. Like you said, it also contains locking information for multi-user environments. In Windows it works the same way but the file is marked as a hidden/system file so it doesn't appear to the majority of users unless they are displaying hidden files.
This is a function of the Office suite and not the operating system so there really isn't any way to turn the functionality off. There may be an Office setting to disable the backup function but I'm still not sure that will remove the file entirely.
This may end up being more of a training issue than something that can be handled through software. Is there a reason your users disconnect from the VPN before saving and closing?
You could also try to edit the Auto Recovery options seen below to see if that helps:
Best Answer
How are you connecting to the server? Since the program works when you copy it locally, you might want to add the server to the Intranet security zone.
See: http://support.microsoft.com/kb/303650