Here is the log of what happens
Welcome to Core FTP, release ver 1.3b, build 1375 (U) -- © 2003-04
WinSock 2.0
Mem -- 916,976 KB, Virt -- 2,097,024 KB
Started on Wednesday September 01, 2004 at 22:51:PM
Resolving thehairshow.co.uk...
Connect socket #452 to 66.98.164.61, port 21...
220 Microsoft FTP Service
USER thehairshow.co.uk
331 Password required for thehairshow.co.uk.
PASS **********
230 User thehairshow.co.uk logged in.
SYST
215 Windows_NT
Keep alive off...
PWD
257 "/thehairshow.co.uk" is current directory.
CWD /thehairshow.co.uk/
250 CWD command successful.
PASV
227 Entering Passive Mode (66,98,164,61,4,183).
LIST
Connect socket #496 to 66.98.164.61, port 1207...
timeout
425 Can't open data connection.
QUIT
221
XP Pro client machine sharing internet connection from another machine using 602 Lansuite. Zone Alarm on client machine with no ports blocked AFAIK. XP firewall is off on both client and host machine.
no directory listing in passive mode (602 Lansuite/proxy)
Sorry I misunderstood. That is what I have tried already.
I presume by "internal ip" you mean NAT? All internet use programs are currently accessing via 602 proxies. It is possible this is a Windows problem as the machine that connects directly is setup for Microsoft Internet Connection Sharing. Then we have 602 with NAT (does that make two implementations of NAT?). Anyway all other programs on all clients work fine with proxy. The 602 NAT implementation makes no difference if it is on or off except for CoreFTP, which gets further if setup not to use proxy but with NAT turned on.
I presume by "internal ip" you mean NAT? All internet use programs are currently accessing via 602 proxies. It is possible this is a Windows problem as the machine that connects directly is setup for Microsoft Internet Connection Sharing. Then we have 602 with NAT (does that make two implementations of NAT?). Anyway all other programs on all clients work fine with proxy. The 602 NAT implementation makes no difference if it is on or off except for CoreFTP, which gets further if setup not to use proxy but with NAT turned on.
I have IE proxy settings that way. This is what I got from IE pointing to my ftp hostname;
220 Proxy602 Gateway ready, enter user@host[:port]
500 Host not found
It doesn't get past the proxy. I don't know where I could enter login details.
With Windows FTP I just get "Unknown host" but it does not provide a commentary on where it failed.
I know this isn't a problem caused in any way by CoreFTP so thanks for your help.
220 Proxy602 Gateway ready, enter user@host[:port]
500 Host not found
It doesn't get past the proxy. I don't know where I could enter login details.
With Windows FTP I just get "Unknown host" but it does not provide a commentary on where it failed.
I know this isn't a problem caused in any way by CoreFTP so thanks for your help.
Using FTP proxy "transparent" I get this;
Resolving thehairshow.co.uk, via proxy ...
Connect socket #612 to 192.168.0.1, port 21 (to 21)...
USER thehairshow.co.uk
220 Proxy602 Gateway ready, enter user@host[:port]
There are no further messages after a couple of minutes waiting.
With Socks 4a or 5 I get this;
esolving thehairshow.co.uk, via proxy ...
Connect socket #656 to 192.168.0.1, port 1080 (to 21)...
Can't establish connection --> thehairshow.co.uk:21 @ Thu Sep 02 21:59:50 2004 (122-38)
Resolving thehairshow.co.uk, via proxy ...
Connect socket #612 to 192.168.0.1, port 21 (to 21)...
USER thehairshow.co.uk
220 Proxy602 Gateway ready, enter user@host[:port]
There are no further messages after a couple of minutes waiting.
With Socks 4a or 5 I get this;
esolving thehairshow.co.uk, via proxy ...
Connect socket #656 to 192.168.0.1, port 1080 (to 21)...
Can't establish connection --> thehairshow.co.uk:21 @ Thu Sep 02 21:59:50 2004 (122-38)