Using curl

I'm running smbclient version 4.9.4 trying to transfer a 97 MiB file from Arch Linux to Windows. Following the recommendation of user bsd, I called smbclient using

--socket-options='TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALIVE SO_RCVBUF=131072 SO_SNDBUF=131072'

But this still failed with cli_push returned NT_STATUS_IO_TIMEOUT.

Fortunately, since version 7.40, curl supports the smb protocol version 1.

Thus, I used this to upload the moderately_sized_file from Linux to the service OurRemoteDirectory on the Windows machine at 172.16.17.52:

curl --upload-file /home/me/moderately_sized_file --user "OurWindowsDomain/MyUserName:MyPassword" smb://172.16.17.52/OurRemoteDirectory/Path/To/Dir/

For me, curl has uploaded the file reliably each time and also displays upload progress, which is nice.

Create the remote directory

Note that curl doesn't yet support creating directories on the remote host.

Consequently, you might need to create /Path/To/Dir/ using the following smbclient command:

smbclient //172.16.17.52/OurRemoteDirectory/ -U MyUserName%MyPassword -W OurWindowsDomain -c 'mkdir Path/To/Dir/'

In contrast to uploading the file with smbclient, smbclient mkdir has worked without an issue so far.

I had the same issue that download always failed, I was able to resolve the "parallel_read returned NT_STATUS_IO_TIMEOUT " problem using these options:

smbclient -m SMB2 ... -c 'timeout 120; iosize 16384; ...'

Example: from the file path "//server/share/My Files/More Files/version_1/file.txt"

smbclient -m SMB2 -N '//server/share' -c 'timeout 120; iosize 16384; get \"My Files\More Files\"\version_1\file.txt' -U <username>

Without these settings download failed 100% of the times and with these seetings it worked 100%.

I also had OP's issue using smbclient and the suggestions to use "--socket-options=" and "-t" didn't help.

I found the solution, for my use case, on a Google translated French site that suggested issuing the "iosize" command before issuing the "put" command.

In my scenario I'm piping data to smbclient through a fifo and using the -c switch to execute the "put" command. My code changed from:

smbclient \
        --socket-options='TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALIVE SO_RCVBUF=16777216 SO_SNDBUF=16777216' \
        -E \
        "//${smb_endpoint}" \
        "${smb_password}" \
        -U "${smb_username}" \
        -c "put /dev/fd/0 ${index}.json.lzo"; echo $? >"${exit_file}"

to

smbclient \
        --socket-options='TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALIVE SO_RCVBUF=16777216 SO_SNDBUF=16777216' \
        -E \
        "//${smb_endpoint}" \
        "${smb_password}" \
        -U "${smb_username}" \
        -c "iosize 16384; put /dev/fd/0 ${index}.json.lzo"; echo $? >"${exit_file}"

Note: iosize 16384; added before the "put" command.

I hope this saves someone some time.

Maybe you can install a ftp server on your linux server, and ask Windows admin to send it the file nightly ?

FTP has a some useful functions for transferring big files and a pause/resume mechanism. For file this big, you should take care to not have a network hardware shutting down inactive connections too early. It can close your control connection before transfert ends.

if

smbclient --socket-options='TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALIVE SO_RCVBUF=131072 SO_SNDBUF=131072'

still returns cli_push returned NT_STATUS_IO_TIMEOUT

just add a timeout option -t <timeout in seconds>

It helps me to copy huge files ( > 200 Tb ) of virtual machines