I like your thought. This might point to a firewall somewhere that constrains the number of ports to a small range. PC people have a very hard time understanding why you need more than one port for anything.
No doubt they simply observed the number of ports in use and used that to configure the firewall constraints. I am a bit reluctant to blame all such problems on network appliance configurations, but they seem to be at fault more often than not. More, they seem to lack tools to discover these kinds of issues. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Hunkeler Peter (KIUK 3) Sent: Friday, October 20, 2006 7:27 AM To: [email protected] Subject: Re: Multiple FTP Problems I may be on the wrong track again, but anyway I can't get rid of the thought about "not enough TCP ports" available. - You define the ephemeral port range in TCPIP's profile - Each transfer of a file needs a new port. - A TCP connection stays in Close-Wait state for some time (2 minutes?) after the close, so the port is still blocked Too many file transfers in a short time and too small an empeheral port range might lead to no port available. Glad if someone corrects me if I'm mixing up things again. Peter Hunkeler CREDIT SUISSE NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. ---------------------------------------------------------------------- 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
