RE: ftp problem

["Andy Nolen-Parkhouse" <aparkhouse@xxxxxxxxxxx>]

Jim,

In your script, are you explicitly specifying the port subcommand?  The
OS/400 FTP server will generally default to port 21, but not under all
circumstances.  The following is from the FTP manual:

Port (PORT)
Specifies the port number used for connecting to the FTP server.
Normally the "well-known" port value of 21 is used to connect to the FTP
server. Under some circumstances, the FTP server may be contacted at a
port other than port 21. In those situations, the port parameter may be
used to specify the server port to connect to.

Perhaps in one of four tries, your system is going to a different port
which is not allowed by your "network upgrade".  If that's the case and
you don't have a port subcommand in your script, you could solve the
problem by adding the subcommand.

Regards,
Andy Nolen-Parkhouse

> At V4R5 I have a site I FTP to from an offsite pc, using a batch file &
> WinXP, every week, 2 diff files.
> Working for years. After a "network upgrade", the FTP is sometimes
> "hanging" and won't work till i stop/start the FTP server. (have latest
> cume)
> ftp logs on
> 200 PORT subcommand successful    and hangs there...
>          never get 150 Sending file......
> 
> I can see FTP job QTFTPxxxxx and nothing odd in log.
> In exit program log i can see the SET and GET, just like successful one
> 
> Happens about 1 out of 4 tries, but once happens, must reset FTP
> server.
> Any ideas?
> jim franz