Lyle.,
You're plenty of help. I noticed that using netscape was fine as well,
however the downloads seemed to stop with one kbyte left in the transfer..
i've always had problems transferring files with netscape so i'm steering
clear of it :) Per your advice, I'll turn on debugging and see which port
it wants, my ipfwadm setup is set to masquerade to ports 1024:65535, so it's
probably asking for something lower..
Jim
[EMAIL PROTECTED]
> It's not a problem specific to IE5.0. I get the same error running the
> normal ftp client on my OpenLinux 2.2 machine which is routed through
> an OpenLinux 1.3 machine using diald 0.16 and ipfwadm. FTP normally
> establishes a connection on a specified port and talks using that port,
> but transfers data using a different port. My guess is that that
> different port is one of the ports that you have blocked using ipfwadm.
> I have found that using Netscape's ftp client, I don't run into that
> problem. I think the only way you're going to get around it would be
> to either enable all traffic on all ports to pass through, or find out
> if it is trying to use a specific port somehow and then enable traffic
> to pass through on that port. In order to get Netscape's ftp to work,
> I enabled only a select few ports under 1024, but everything above it,
> since FTP can use any port to transfer data. It may also depend on the
> site you connect to. For example, I often run into problems using IE
> 4.5 on my iMac, but not always. It varies from site to site, but
> always works the same at any particular site (i.e., if it didn't work
> once at this.domain.com, it never does).
>
> I know that's not much help, and I could be wrong on a couple points,
> but for what it's worth...
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
