Hmmm... Nothing changed; I just woke my computer up and started the NAS. Ran the .cmd file created yesterday and now it's copying... Sigh. Thanks! :)
I did a fresh install last week (9.10). Yesterday I created a folder / share "M" for my Music. While I could read/write to the share with explorer, TeraCopy failed everytime without an error. So I tried to move the files with Robocopy, which failed too. Folders were created, but no files were transferred. Insisting it had no access to the folder (unsupported filesystem & error 1314 a required privilege is not held by the client). I looked at problems with /COPYALL or /B but had to rule them all out. I even re-took Administrators-group ownership on all local files, but nothing.
Command used:
C:\rktools\Robocopy "D:\shares\Music" "\\Bigcube\Muziek" /E /COPYALL /MOVE /R:10 /W:5 /REG /TBD /V /ETA
I tried /COPY: DAT etc., nothing changed. Explorer had no problems, Windows copy tools all failed. I tried both the share directly and through a mapped drive.
So I went to bed (often a succesful strategy) and shut-down my FreeNAS. I also gave my Windows Home Server (2003) a reboot.
This morning I powered on the NAS once more and I was denied access fully to my "M"-share, even with explorer. I wasn't even allowed to read! My mapped network shares were still operational. So I went to FreeNAS GUI and found that the permission group was reset from MyLAN to WHEEL. I fixed that, and now not only explorer had access once more but suddenly TeraCopy & my batch script above worked without problems.
I don't expect an answer to this problem, but I am curious if others are experiencing this weird behaviour too sometimes? Otherwise I'll have to take a closer look at my Windows Home Server :/
Peace!
Devnullius
PS: and if anyone knows of better trained hamsters... Do let me know ;p