Path: utzoo!attcan!uunet!zephyr.ens.tek.com!uw-beaver!milton!dali.cs.montana.edu!uakari.primate.wisc.edu!zaphod.mps.ohio-state.edu!sdd.hp.com!hplabs!hpcc01!walasek
From: walasek@hpcc01.HP.COM (Arthur Walasek)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: IBM/HP-UX FTP session hangs on PORT command
Message-ID: <1530001@hpcc01.HP.COM>
Date: 27 Jul 90 00:18:36 GMT
References: <277@camdev.UUCP>
Organization: HP Corporate Computing & Services
Lines: 35

>/ hpcc01:comp.protocols.tcp-ip / sscott@camdev.UUCP (Steve Scott) /  8:10 am  Jul 19, 1990 /
>
>
>Steve, we have seen a problem for a long time where FTP sessions from IBM
>TCPIP to an HP node would fail when the FTP application issued a PORT command.
>
>Any ideas out there?

Well Steve,

	Here is what we have found out.  IBM starts using port address for normal
	communications starting at port 1000 and working its way up.

	HP reserves up to port 1024 or system utilities and makes available ports
	after 1024.

	Therefore, when you first bring up the IBM and try to start ftp sessions,
	you have to error on the first 24 protected ports before any data will
	actually go across.

	I believe that the standard is to start at 1024, and therefore it is
	possibly an IBM problem....

	We have this problem too, and we set up the IBM to 25 transfers that will
	error, when TCP/IP comes up....  (really poor fix).


  If you need anymore information, or if I was too unclear, please mail
	me....
		
Arthur Walasek
Hewlett Packard
------------------------------
Ideas expressed are my own and are no way the expressions of Hewlett
Packard.