×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
From: Jon Paris
Anyone got a suggestions as to where to look next?
Okay, seriously, stick a packet sniffer on the network. Find a client
machine that works with one iSeries and not the other, and stick the sniffer
on that client.
Among the leading possibilities is that the iSeries is sending the wrong
acknowledgement message and FileZilla is being very picky (and not terribly
helpful). I know that IBM has in the past used FTP return codes that, while
technically correct, didn't match the du jour standards and so caused grief.
They may have "fixed" them between releases (in fact, I'm pretty sure they
did change some).
The packet sniffer (something like Ethereal) is your best fried when trying
to identify protocol errors like this.
Joe
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
