[quoted text, click to view] "Tom Allen" <tsa68@[removethisfirst]verizon.net> wrote in message
news:%231f8khgOFHA.1040@TK2MSFTNGP12.phx.gbl...
> Hopefully this one will be easy......
>
> I added a couple ftp sites to my SBS 2003 Std server
>
> If I connect to them with IE 6, it will only work with PASV disabled,
> Active ftp enabled.........
>
> If I connect to them with ws_ftp or filezilla, I can use PASV just fine.
Some clients will ignore the IP address specified in the PASV response, and
will connect to the port number that the PASV response gives, at the IP
address of the server. This is unreliable behaviour - it might result in
your client connecting to a socket that doesn't map through to the same FTP
session, because the NAT router that is causing the problem in the first
place will be translating ports as well as IP addresses, some of the time.
It's a design decision, whether to go with "works most of the time, but
might be unsecure" or "either works securely or not at all". The method
that the Internet Explorer FTP client code uses is the latter - it either
works securely or not at all.
The solution to this is to make sure that all of your FTP sites run on port
21, or to configure your NAT to recognise FTP traffic on ports other than
21. At present, I'm not aware of any consumer NAT routers that can be
configured in such a manner - but if you pester your NAT router vendor, they
may eventually implement such a feature.
Alun.
~~~~