Perryg: Thanks for responding. I'll try to answer your questions, but in the past 24 hours, I've found a thread (bug) that describes this to a tee, with more information and an interesting work around that might shed light on it. See http://www.virtualbox.org/ticket/3340
for this thread. I'll try to answer your questions:Folder deletion works as it should. Can you tell me a little more about the folders. Are they created from the guest or the host?
The folder file permissions seem fine (same as the r+w and owner access is enabled. It doesn't seem to matter if they are created by the guest or host. If the guest creates the file in a sub-folder, it cannot delete it (but the host can). I do have write permission turned on for the share (i.e. Read Only is not selected), which is verified because the guest can create the file in the first place - it is just that it cannot delete it afterwards.The part about not being able to delete a folder using a full network share connection indicates a permission problem on the host. Can you verify this?
The share looks fine with same permissions on sub-folders as the share root. I thought about windows Long Filenames possibly being related, but have ruled it out. From the guest, I can create a folder (called test) on the Shared Folder on the host and then inside it create a file (called test.txt) - no LFNs used. Properties in Windows shows not read only. Linux Host shows ls -al for test and test.txt as follows:
drwxr-xr-x 2 chuck chuck 4096 2010-02-14 14:02 test
-rw-r--r-- 1 chuck chuck 0 2010-02-14 14:02 test.txt
So it does look like when the guest creates the file, the group or others do not get write permission when VirtualBox puts it on the Host. This may be significant.Look at the share and see if it is full or read only.
Full.What mode are you using for the network in the guest?
Machine folder (not transient), Full access.
Have a look at http://www.virtualbox.org/ticket/3340
. I'll monitor both threads and be happy to post logs, etc if you wish.