I was thinking on this. IPv6 is expected to be able to be enabled and not interfere. It doesn't say how you resolved it, but it sounds like it was done by disabling IPv6 based on your words. If so, that would not be a correct fix.

I fully expect that you have some other networking problem going on.

More or less, as I previously replied above, am adding this as future reference to any who see this and are trying to find an answer. The user here feels its resolved. But, possibly at the loss of IPv6.

Yes, found out that my network setting had IPV6 enabled which was blocking my continuous connection to the target host server. Resolved it by myself. You can close this topic. Thanks.

It looks like a network outage.
Does the file upload using any other SFTP client?

please see the attached log file, thanks

@cswamy: Please attach a full session log file showing the problem (using the latest version of WinSCP).

As there's 2.7GB+ that transfers, its very unlikely to be the client. You really need to look at logs from the client and from the server to maybe see what might be going on

To have bytes stop in the middle of a code transfer loop, its expected (by me) to be a connection based issue.

There are things that won't be normal, like not seeing storage is out of space, or a number of other things.

You can see what Martin thinks since he's not replied yet =)

The transfer of a large file of 3GB+ file fails while uploading from Windows 11 to Linux 64 server requesting target server credentials again. This results in not completing the file transfer. It failed after completing the transfer of about 2.7GB in 3.11 minutes. Anyway to remediate this interruption? Thanks.