Core FTP

... a further update.

I installed CoreFTP on my laptop and dialled up my ISP via a 56k modem connection, thus getting the router & NAT out of the picture.

Unfortunately the result was the same

I have tried the other flavours of SSL, but it appears the server is not set up to accept them. Do you have a test server that I could try out against, please (PM me if so)? I don't know of anyone running a non-routed www connection that I could try from, but I could temporarily set up my connection...

Thanks for that - I may be confused here, but I thought that since this was an active mode connection, the PORT command was issued by the client to tell the server what IP & port to connect back to the client on :?. The IP address in the PORT command is the same as the address of the client end ...

.. One other thing I've noticed is that when the connection does work the second time, the server IP address for the data connection is different from the primary connection: C:>netstat -a Active Connections Proto Local Address Foreign Address State ... TCP ferrari:2169 x.y.127.126:990 ESTABLISHED ....

No, sorry - changing the starting port number does not seem to have any effect. I've also tried a totally different port range just in case. Good thought though! It could also be a problem on the server end, or even a router microcode issue too - is anyone else out there using implicit SSL + active ...

I am trialing CoreFTP (LE 1.3c buid 1437) to connect to a site that has set its security standard requiring SSL and active mode client connections (yes, I know :shock: ...). I have made sure that my router and software firewall cope with the active port range (50100 - 50200) I have defined within Co...