|
Try using QUOTE TIME 3600 3600 This will set bot the inactivity and transfer timeouts to one hour. - Larry Jay Peasley wrote: > > Mark/Brad, > > Yes I set the session to Binary with the BIN command prior to the GET. > > I forgot to mention that it occurs on a 56k line and it happens on both > ISP's that I use, and I can duplicate the problem on Win95 and Win98 also. > > The only commonality I can find is the slow line(56k) and as/400, but more > importantly the 400. > > I haven't experienced the PUT problem. Last night I PUT a 36 meg file on one > 400 and couldn't GET a 5 meg file from the same 400. > > It is very frustrating, cause I am up to my ears in alligators on a data > conversion project and I can't get the data off to send them. > > I was hoping the PTF meister, Neil, would have one handy to list. ;-) > > Jay > > ----- Original Message ----- > From: "Mike Shaw" <mshaw@ncal.verio.com> > To: <MIDRANGE-L@midrange.com> > Sent: Friday, December 01, 2000 9:57 AM > Subject: Re: FTP GET Failing on Large Save Files > > > Jay, > > > > Save files have to be transferred via FTP as a binary file. Before > issuing > > the GET, did you use the BINary FTP subcommand? > > > > Regards, > > > > Mike Shaw > > Senior AS/400 Technical Support Specialist > > North American Mortgage > > Santa Rosa, CA > > > > ----- Original Message ----- > > > > > Morning, > > > > > > Has anyone had a problem with a DOS issued FTP GET failing on large save > > > files from AS/400's? I am having a problem with 2 different 400's, both > on > > > v4r4. One I am connected via an Intranet and am behind a fiewall, and > the > > > other through the Internet. The amount of data transfered each time > before > > > it hangs is variable, anywhere from 500K to 5 meg. Most of the time the > > > error is 'Connection closed by remote', though once in a while it is a > 426 > > > error. My client is a Win2K machine. I FTP GET large files all the time > > with > > > GUI clients from other platforms and never have a problem. > > > > > > I have searched the midrange list and the only similar hit I got was a > HUB > > > causing an error on a PUT operation. > > > > > > Thanks, > > > > > > Jay Peasley > > > > > > > > > +--- > > | This is the Midrange System Mailing List! > > | To submit a new message, send your mail to MIDRANGE-L@midrange.com. > > | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. > > | To unsubscribe from this list send email to > MIDRANGE-L-UNSUB@midrange.com. > > | Questions should be directed to the list owner/operator: > david@midrange.com > > +--- > > > > > > +--- > | This is the Midrange System Mailing List! > | To submit a new message, send your mail to MIDRANGE-L@midrange.com. > | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. > | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. > | Questions should be directed to the list owner/operator: david@midrange.com > +--- -- Larry Bolhuis Arbor Solutions, Inc. (616) 451-2500 (616) 451-2571 -fax lbolhuis@arbsol.com +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.