I was able to connect to my z/OS v1r9 system with FileZilla just fine.
Something you'll want to do is to go into your FTPDATA configuration, and
set:
debug sec
debug CMD
debug soc(3)
debug flo
You can also add a parm to the FTPD (I believe) setting:
ENVAR("GSK_TRACE=0XFFFF")
It may be exclusive to the FTP Client, but I don't think so. So, give that
a shot and you can e-mail the results privately to me, if you don't want all
of that detail to be published on the list.
This will let you see what the server thinks about the connection that's
being established.
Also, can you provide the TLS-relevant configurations, from your FTPDATA?
My retarded blog (inherentlylame.com) covers how I've set it up in the
past--and it worked with FileZilla.
Another thing: Is there a firewall between your computer and the Mainframe?
That's also very important.
Scott
On Thu, Dec 3, 2009 at 12:24 PM, Gibney, Dave <gib...@wsu.edu> wrote:
> Thanks, UK43295 (APAR PK77240) is on my 1.9 system.
> I'll give TLSRFCLEVEL RFC4217 a try and report back.
>
> This is my third trip to this well on this issue. May be the charm :)
>
> Dave Gibney
> Information Technology Services
> Washington State University
>
>
> > -----Original Message-----
> > From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On
> > Behalf Of Richard Peurifoy
> > Sent: Thursday, December 03, 2009 12:06 PM
> > To: IBM-MAIN@bama.ua.edu
> > Subject: Re: Filezilla, was Ipswitch WS_FTP Pro 12 not displaying OMVS
> > directories correctly
> >
> > Gibney, Dave wrote:
> > > I must have something wrong. I just installed the latest. 3.3.0.1
> > and
> > > I still get:
> > >
> > > Trace: CTransferSocket::OnReceive(), m_transferMode=0
> > > Trace: GnuTLS error -9: A TLS packet with unexpected length was
> > > received.
> > > Status: Server did not properly shut down TLS connection
> > > Error: Could not read from transfer socket: ECONNABORTED -
> > Connection
> > > aborted
> > > Trace: CTransferSocket::TransferEnd(3)
> >
> > We had a similar problem some time ago.. With help from the
> > IBMTCP-L list I found:
> >
> > http://trac.filezilla-project.org/ticket/3626
> >
> > which seemed to match the problem. Nothing I tried at the time got
> > around this problem. My next thing to try was switching to AT-TLS
> > which someone said fixed the problem, but I have been too busy to
> > get it set up.
> >
> > However I now see:
> >
> > http://trac.filezilla-project.org/ticket/3684
> >
> > which sounds like there might be a fix without AT-TLS.
> > I am going to try this this weekend.
> >
> > Steve Bireley of Bluezone helped in looking at some of my traces,
> > and also suggested I try the Bluezone client which is free.
> >
> > http://www.bluezonesoftware.com/
> >
> > Richard
> >
> > ----------------------------------------------------------------------
> > For IBM-MAIN subscribe / signoff / archive access instructions,
> > send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
> > Search the archives at http://bama.ua.edu/archives/ibm-main.html
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
> Search the archives at http://bama.ua.edu/archives/ibm-main.html
>
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
