RE: Ftping large files w/o timing out -- MIDRANGE-L

I am not an ftp guru
.....I can only tell you this works for me
..........another company we are working closely with has the exact same
problem
.....and apparently several others

And obviously enough that it needed an article written about it
..................which describes my problem exactly
.....and there are others articles that lead me to this one
.....it is an industry wide occurrence whether iSeries or not

If something else solved the issue
.....why did it work when I changed this and only this
.....I had already tried changing timeout values and activity timers
.....that did not work

If yours works for you
.....that's great
.....this works for me

Terry Nonamaker

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Tim Bronski
Sent: Monday, January 28, 2013 9:32 AM
To: Midrange Systems Technical Discussion
Subject: Re: Ftping large files w/o timing out

That's where I don't see the PASV/EPSV being relevant. The doc you sent me
describes a problem that's relevant to establishing data connections.
Once a data connection is made then it's irrelevant which command was used.
So, if you're able to create a connection and send a file then whichever
passive command you used works. The issue with large files is due to
timeouts on the control connection when the transfer on the data connection
takes too long. Perhaps something else solved the issue.

On 1/28/2013 6:09 PM, Terry Nonamaker wrote:

Only when sending very large files
... in this case, one file that is 4.9gb and another that is 13.4gb
... otherwise, there is no problems

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jeff Young
Sent: Monday, January 28, 2013 8:47 AM
To: Midrange Systems Technical Discussion
Subject: Re: Ftping large files w/o timing out

Terry,
I this only an issue when sending very large files, or an issue in
general when this condition occurs?

Thanks,

On Mon, Jan 28, 2013 at 11:21 AM, Terry Nonamaker <
TNonamaker@xxxxxxxxxxxxxxxx> wrote:

So, attaching a document did not go so well .....so here's the info

IBM - Disabling EPASV/EPORT in the iSeries FTP Client at R610 and
above

www-01.ibm.com/support/docview.wss?uid=nas1dace92df240295dc86257425005
65275

1/2

Technote
At R610, the iSeries FTP client supports the EPASV (Extended Passive,
EPSV) command and EPORT (Extended Port, EPRT). The FTP client
defaults to this and, if the server we are connecting to does not,
the FTP client will fail over to Passive mode FTP. However, in some
cases, an

error

message is not returned. Most commonly, this is due to a firewall not
allowing or supporting the EPASV /EPORT command, and the
establishment of a data connection will appear to 'hang' with:

229 Entering Extended Passive Mode

In these cases, the EPASV/EPORT commands must be disabled.
The FTP client attempts data connections in the following manner:
Extended Passive
Passive
Extended Port
Port

As a result, if PORT mode is needed, the three preceding data
connection types must first be toggled off. This can be done in one of

two ways:

1. On a connection-by-connection basis using FTP client subcommands:
o SENDEPSV - Toggles Extended passive o SENDPASV - Toggles Passive
mode o SENDEPRT - Toggles Extended Port

Note: The data connection type can also be set (regardless of what
the default behavior is) by using the 0 or 1 switches with the above
3 commands. For instance:
SENDEPSV 1 - would toggle extended passive on SENDEPSV 0 - would
toggle extended passive off

2. On a system-wide basis with the use of data areas:
o CRTDTAARA DTAARA(QUSRSYS/QTMFTPEPSV) TYPE(*LGL)
AUT(*USE) - disables EPASV
o CRTDTAARA DTAARA(QUSRSYS/QTMFTPPASV) TYPE(*LGL)
AUT(*USE) - disables PASV
o CRTDTAARA DTAARA(QUSRSYS/QTMFTPEPRT) TYPE(*LGL)
AUT(*USE) - disables EPO RT with PTF SI33243 applied to the

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Terry Nonamaker
Sent: Monday, January 28, 2013 8:02 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Ftping large files w/o timing out

This is the IBM document I based it on ....sounds like my problem to
me ....and, as I said before, it now works just fine

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Tim Bronski
Sent: Monday, January 28, 2013 7:58 AM
To: Midrange Systems Technical Discussion
Subject: Re: Ftping large files w/o timing out

Well that's good...but it doesn't make sense unless we're talking
about a different problem than the one i assumed. PASV or EPSV set up
the data connection (EPSV is really just the ipv6 version of pasv).
Once the data connection is in place it doesn't matter which one was
used. If the

problem

was in establishing a data connection for a transfer then I can see
how perhaps the firewall had an issue but after that...

But hey, if it's working...

On 1/28/2013 4:46 PM, Terry Nonamaker wrote:

Switching to PASV mode did make all the difference ......it totally
works now

The EPSV has problems with firewalls .....PASV does not .....it is
working just like I want it to

Thanks

Terry Nonamaker

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Tim Bronski
Sent: Saturday, January 26, 2013 7:00 AM
To: Midrange Systems Technical Discussion
Subject: Re: Ftping large files w/o timing out

If the timeout is happening after it has been sending for a while
then I don't see any reason why a switch from EPSV to PASV would
have any effect whatsoever.

But, I had discovered in another post about using passive mode
(PASV) ......as opposed to the default of ... extended passive mode
(EPSV)

That seems to do the trick
....it does not have issues with the firewall now ....no time out

--
Need secure FTP? Forget PASE...get your FREE sFTP here
www.arpeggiosoftware.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please
take a moment to review the archives at

http://archive.midrange.com/midrange-l.

--
Need secure FTP? Forget PASE...get your FREE sFTP here
www.arpeggiosoftware.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at

http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/midrange-l.

--
Need secure FTP? Forget PASE...get your FREE sFTP here
www.arpeggiosoftware.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.