This has been covered a few times before, but I'll try and explain again. One can use Windows Explorer to MOVE files from one physical disk to another within the "Shares" share. The move is internal to NASLite and files do not route through the client PC. Windows thinks that it's moving files within a single drive so expectations are that the move will take a short amount of time. Since internally to NASLite, the move is between physical drives, moving can take longer than Windows expects. Especially when moving large files, Windows Explorer sometime times out and reports an error.
The above is true only when moving to/from the "Shares" share where windows thinks it's a single drive. Copying files on the other hand will route through the client regardless of source or destination.
Hope the above clears things up a bit and explains what you are experiencing.
|