Remoteshare and Windows file share

Hello,

I have installed the remoteshare plugin and connected that to a samba file share on a remote Windows XP machine. I have the share mounted/enabled within both the samba and FTP modules in OMV.
From remote machines connected to OMV I am able to view the files/folders on the remote XP share. However, I am unable to upload or change anything within the share without getting a permission denied error. I have the OMV users set for Read/Write access on the share within OMV. The XP File share is not locked down with any permissions. I can modify files on the share when logged into the OMV terminal as root, just not from the normal users using OMV services. I also tried resetting the shared folder permissions to give access but also got permission denied from there. This has me a bit confused. Any insight would be much appreciated.

Thank you.

:~# cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda1 during installation
UUID=3f0d32f4-c7ec-45d0-ba8d-99df5f88a971 / ext4 noatime,nodiratime,errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
#UUID=0dac67f8-8b2d-446d-a11b-84ddc40f277d none swap sw 0 0
/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/sda1 /media/usb0 auto rw,user,noauto 0 0
/dev/sda2 /media/usb1 auto rw,user,noauto 0 0
/dev/sda5 /media/usb2 auto rw,user,noauto 0 0
# >>> [openmediavault]
UUID=829e5277-8e9c-4353-aa5e-8cb125cdf0f9 /media/829e5277-8e9c-4353-aa5e-8cb125cdf0f9 ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
//10.10.46.60/test /media/829e5277-8e9c-4353-aa5e-8cb125cdf0f9/pool1 cifs username=PSAP_Lab,password=password,sec=ntlm,_netdev,iocharset=utf8 0 0
# <<< [openmediavault]

Hello,

I tried the steps above, I am still unable to write/modify any files on the share using OMV user accounts. I also tried rebooting afterwards and still was unable to.

:/media/829e5277-8e9c-4353-aa5e-8cb125cdf0f9/pool1# ls -la /media/829e5277-8e9c-4353-aa5e-8cb125cdf0f9/pool1/
total 164
drwxr-xr-x 1 root users 0 Apr 29 15:37 .
drwxr-sr-x 3 root users 4096 Apr 29 16:44 ..
-rwxr-xr-x 0 root users 163079 Apr 29 11:04 Rob-Zombie-Antyradio.pl2_.jpg
drwxr-xr-x 0 root users 0 Apr 29 15:37 test

That seems to kill the share altogether. When I do an "ls" command it shows as empty now. I verified the Windows host is still up and reachable. Does placement matter for that statement in the fstab?

Currently mine looks like this," //10.10.46.60/test /media/829e5277-8e9c-4353-aa5e-8cb125cdf0f9/pool1 cifs username=PSAP_Lab,uid=0,gid=100,file_mode=0775,dir_mode=0775,password=password,sec=ntlm,_netdev,iocharset=utf8 0 0"

Ok so I changed my statement to look like this, "//10.10.46.60/test /media/829e5277-8e9c-4353-aa5e-8cb125cdf0f9/pool1 cifs username=PSAP_Lab,uid=0,gid=100,file_mode=0777,dir_mode=0777,password=password,sec=ntlm,_netdev,iocharset=utf8 0 0"

I am now able to modify and upload files to the share through FTP and samba. However, from a windows machine connected to the samba share; if I try to create a new folder, it will immediately change into an unknown file that will not open. I don't have enough time to name the file before it changes to unknown.

I am able to create and enter folders using FTP without issue now.