Turns out our FTP problem was due to the FTP processes being launched from the xinetd process. There's a default limit to the number of processes that will get started from xinetd. When we started an FTP server on it's own, the problem went away. We have since gone back and modified the xinetd limit and put the FTP server processes back under its control for the enhanced security it offers.
Thanks for the help. Chuck Gowans USDA - Nat'l IT Center -----Original Message----- From: Ward, Garry [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 07, 2003 7:36 AM To: [EMAIL PROTECTED] Subject: Re: FTP Failures to Linux Guest Sounds familiar; we had a client that was doing FTP transfer into and out of our "DMZ" from a MVS system and would randomly get sessions resets. Firewall folks said that the FTP sessions were getting their ports shifted into ranges that the Firewall considered hacker attacks and shut them down. Firewall folks had to make some changes (kicking and screaming about security) to make sure the ports were not denied. Been some months ago, and not sure if it was our firewall around our "DMZ" or the client's firewall around their system. -----Original Message----- From: Gowans, Chuck [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 07, 2003 8:17 AM To: [EMAIL PROTECTED] Subject: FTP Failures to Linux Guest We have a customer who's transferring approximately 200 files nightly from an OS/390 2.10 guest to a RedHat Linux 7.2 at the 2.4.9-38 kernel level. The files vary in size but are generally always smaller than 600k. The FTP process fails 99% of the time after transferring anywhere from 20 to 150 of the files. We can recreate the problem on another Linux guest running the same version of RedHat. We can successfully transfer the files from the OS/390 system to other OS/390 systems as well as to Windows based PC platforms - all of which complete successfully. The only difference is the Linux guest is in the DMZ while the other S390 systems and the PC's we've tested to are in our Intranet. When it fails the only message we see is from the OS/390 side which indicates the session has reset. Any ideas on how to determine what's going on when transferring to the Linux guest that may be causing the session to fail? Chuck Gowans USDA - Nat'l IT Center <font size="1">Confidentiality Warning: This e-mail contains information intended only for the use of the individual or entity named above. If the reader of this e-mail is not the intended recipient or the employee or agent responsible for delivering it to the intended recipient, any dissemination, publication or copying of this e-mail is strictly prohibited. The sender does not accept any responsibility for any loss, disruption or damage to your data or computer system that may occur while using data contained in, or transmitted with, this e-mail. If you have received this e-mail in error, please immediately notify us by return e-mail. Thank you.
