Hi,

In message <_A3584@delegate-en.ML_> on 12/01/06(00:01:56)
you Steve Brown <ps4gabdyi-mxhgu47aqh3w.ml@delegate.org> wrote:
 |Yutaka Sato wrote:
 |> Seeing what the difference is between the case of the failure and the
 |>  success will be helpful.
 |
 |Please find the following two logs that hopefully will start to explain
 |what I'm troubled with. I'm pretty sure the problem _only_ occurs when
 |Delegate negotiates a TLS FTP session with the remote. It doesn't seem
 |to happen if the remote is plain FTP. The IP addresses have been
 |sanitised; hopefully they still make sense.
...
 |and here is the extract from ftp.qinetiq.com which _does_ have TLS support.
...
 |11/30 12:46:59.41 [29960] 1+0/5/2: ## viaCFI [mkPASV]: fileno(ts)=19 ToSX=20
 |11/30 12:46:59.41 [29960] 1+0/5/2: ## viaCFI [mkPASV]: fileno(ts)=19 ToSX=20
 |11/30 12:46:59.41 [29960] 1+0/5/2: ftp_conndata: connection refused 192.168.2.17:2403->ftp.qinetiq.com/192.168.1.14:48632, errno=111

The problem seems not in SSL but in TCP/IP level.
DeleGate says that it simply failed to establish TCP connection to the
port on the server which was shown in the response for a PASV command.
You can get detailed log with "-vd" option which shows the dialogue
between the DeleGate ant the server including the PASV command/resopnse.
Seeing the log of the FTP server and "netstat -an" on the server's host
will be helpful.

By the way, are you sure that your FTP server (what is it?) works without
problem with FTPS clients other than DeleGate?

Cheers,
Yutaka
--
  9 9   Yutaka Sato <pfqcabdyi-mxhgu47aqh3w.ml@delegate.org> http://delegate.org/y.sato/
 ( ~ )  National Institute of Advanced Industrial Science and Technology
_<   >_ 1-1-4 Umezono, Tsukuba, Ibaraki, 305-8568 Japan
Do the more with the less -- B. Fuller