Re: ftp problem -- MIDRANGE-L

It's the "sometimes works" "sometimes fail" that gets me.
Fantastic article at slacksite!
I've emailed it to the network admin to check out.
jim

----- Original Message -----
From: "Andy Cranston" <a.cranston@xxxxxxxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
Sent: Tuesday, July 29, 2003 10:17 AM
Subject: RE: ftp problem


> Hello Jim,
>
> The symptom of an empty file being created but no data ever getting into
the
> file does sound like a port blocking issue.  Perhaps the network upgrade
no
> longer allows active ftp sessions but instead only allows passive ftp
> sessions?  If that is the case then either get the network admins to lift
> this restriction or get hold of a passive ftp client and see if that
> improves the situation.
>
> This page:
>
>   http://slacksite.com/other/ftp.html
>
> has a good explanation of the differences between active and passive ftp
and
> the issues you might encounter.
>
> HTH.
>
> Regards,
>
> Andy Cranston.
>
> -----Original Message-----
> From: Jim Franz [mailto:franz400@xxxxxxxxxxxx]
> Sent: 29 July 2003 15:03
> To: Midrange Systems Technical Discussion
> Subject: Re: ftp problem
>
>
> I failed to fill in one point. An empty file is created.
> The batch file later has a remote command (which runs fine)
> and processes the empty file. I have verified the
> particular file is not damaged (after reset of FTP server-same
> file processes fine).
> So FTP logs on, and from the PUT command, creates
> an empty file, but stops on sending the data.
> I like the idea of a port being blocked by the network, and
> will have to investigate.
> jim
>
> ----- Original Message -----
> From: "Andy Nolen-Parkhouse" <aparkhouse@xxxxxxxxxxx>
> To: "'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
> Sent: Tuesday, July 29, 2003 9:37 AM
> Subject: RE: ftp problem
>
>
> > 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
> >
> >
> >
> > _______________________________________________
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/midrange-l.
> >
> >
>
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>
> _____________________________________________________________________
> This message has been checked for all known viruses by the
> Selway Moore Ltd (www.selwaymoore.com) scanning service, powered by
> MessageLabs. For further information visit
> http://www.messagelabs.com/stats.asp
>
> ________________________________________________________________________
> ** Please note our new address for all correspondence and deliveries: **
>    Selway Moore House   169 Basingstoke Road    Reading    RG2 0DY
>
>    Selway Moore Solutions      t +44(0)118 903 7907 f +44(0)118 903 7908
>    Selway Moore Limited
>      Recycle division sales    t +44(0)118 903 7903 f +44(0)118 903 7904
>      Corporate and admin       t +44(0)118 903 7900 f +44(0)118 903 7901
>
> For our latest news http://www.selwaymoore.com/modules/news/index.cfm
> ________________________________________________________________________
> This message has been checked for all known viruses by the Selway Moore
> scanning service powered by MessageLabs.  For further information and
> statistics on current viruses visit http://www.messagelabs.com/stats.asp
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>