Re: FTP Fails with "426 Transfer cancelled"

Scott, thanks for the reply.

Yes, I guess we are running the client on the iSeries.

Our current setting is:
TCP time-wait timeout . . . . . TCPCLOTIMO 120

That's two minutes, which is a long time as I see it. The help for this parameter says:

TCP time-wait timeout (TCPCLOTIMO) - Help

This parameter indicates the amount of time, in seconds,
for which a socket pair (client IP address and port,
server IP address and port) cannot be reused after a
connection is closed.

If I read your comments correctly, there would be a socket error and FTP (or TCP) would try to re-establish the connection and find that it could not for the next 120 seconds and so give up? So should the value be increased or decreased?

Our transmission are short, rarely more than 1 or 2 a day, rarely fail and have gone through when I retried them. So I'm thinking that if it fails I just do a DLYJOB of 30 seconds and retry 3 or 4 times before I finally give up and log an error for the support people (who in the end will probably be me anyway.)

Sam

On 1/17/2012 1:53 PM, Scott Klement wrote:

hi Sam,

Correct, 10054 is Windows Sockets error code WSAECONNRESET, which does
indeed mean "Connection reset by peer".

Typically, this error message ("connection reset") implies that the
socket was disconnected in a way that would lose data. So data may have
been sent (by one side or the other) and never received. That's the
difference between "connection reset" and other methods that indicate
that the connection has ended.

Our network guy suggests that we are timing out somewhere in the
transfer because the remote system isn't getting back to us quickly
enough.

Errr... It seems rather unlikely that a timeout would generate a
WSAECONNRESET. Bear in mind that the error is occurring during the
transfer of data on the data channel -- it's not occuring in the command
channel. (If the command channel had been reset, you couldn't receive a
"426 Transfer Cancelled" message.) Since the data channel has no user
interaction, it's purely a program-to-program transfer of file data, I
don't see how it could time-out?

I guess a time-wait timeout might cause this. Take a look at the value
you have for CHGTCPA TCPCLOTIMO(xxx).