Consider using TDSLink from www.tdslink.com if you need to see a packet trace.
>>> [EMAIL PROTECTED] 3/1/2006 3:51:04 PM >>> On Wed, 1 Mar 2006 14:03:15 -0600, Chase, John <[EMAIL PROTECTED]> wrote: >... >regular production FTP job gives a corrupted ASCII file about 40% of the >time. > >This is going to be one of those "fun" problems to document.... :-( >... Can you run a packet trace during every transfer until you've traced a failure? It sure sounds like you might have a bug in the the client or server or TCP/IP stack, and it's a good bet that the bug makes itself felt during exceptional conditions - retransmissions, duplicate ACKs, etc. The file would not be corrupted unless you ran into one of those exceptional conditions. I don't know of any way to trap this except to have the packet trace of each transmission. Pat O'Keefe ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
