...Basically, the copy failed as the remote FS doesn't support EA's, but the plugin must have had EA Support ticked (please confirm).
When the EASet failed, it returned a return code which was passed back to Netdrive, which didn't understand the rc, so basically just said the copy failed, hence the SYS0266.The code is now modified such that if the EAset fails, an appropriate rc is returned which says that EA's aren't supported.
OK, I tested this using the ndpsmb.dll plugin that was provided.
So the results are:
1) with the share defined as supporting EXT attributes the behaviour remains the same, the copy/paste operation still produces a SYS0266 and fails, there is a file created in the remote directory but it is of 0 (zero) bytes
2) with the share defined as NOT supporting EXT attributes the copy/paste completes successfully
For comparison, I executed the same "test.cmd" file copy/paste against other shares on my network, they were:
1) Windows XP - worked successfully with EXT ATR = Y
2) Windows Pro - worked successfully with EXT ATR = Y
I've attached the new log.ndpsmb debug output. So it appears the changes made did not have an impact.
To make sure I was using the correct DLL I used "repmod ndpsmb.dll -u" to un-load the DLL before un-zipping the new DLL into the destination directory. Once un-zipped I confirmed the size/date/time stamp reflected the new DLL.
I updated the ticket with exactly the information stated here and I attached the new log.ndpsmb file.