This is definitely not a problem with Nautilus as it can be seen by all file browsers, including using the command line gvfs-copy as can be seen in the strace output below from running 'gvfs-copy <source file> smb://<windows server>/<share>/<directory>'.
For the same reason it is also very likely not a gvfs problem as I'm seeing the exact same issue with Dolphin on KDE that is using a different network file system implementation. The only thing common to both implementations is using libsmbclient as the underlying protocol implementation.
I've also seen that using the gvfs-fuse mount (at ~/.gvfs) works, and I don't know how to account for that. But besides this bizarre condition, this all seem to me like bug #393012 that came to bite us again.
This is definitely not a problem with Nautilus as it can be seen by all file browsers, including using the command line gvfs-copy as can be seen in the strace output below from running 'gvfs-copy <source file> smb://<windows server> /<share> /<directory> '.
For the same reason it is also very likely not a gvfs problem as I'm seeing the exact same issue with Dolphin on KDE that is using a different network file system implementation. The only thing common to both implementations is using libsmbclient as the underlying protocol implementation.
I've also seen that using the gvfs-fuse mount (at ~/.gvfs) works, and I don't know how to account for that. But besides this bizarre condition, this all seem to me like bug #393012 that came to bite us again.