"Alun Jones [MSFT]" <alunj@online.microsoft.com> wrote in
news:edaZQ9yyEHA.2012@TK2MSFTNGP15.phx.gbl:
[quoted text, click to view] >> Here are the dumps of manual FTP (1st from LAN and 2nd from WAN):
>>
> ...
>> ftp> quote "pasv"
>> 227 Entering Passive Mode (192,168,11,1,33,141).
>>
> ...
>> ftp> quote "pasv"
>> 227 Entering Passive Mode (80,135,202,31,240,234).
>
> The first "227" response comes from the FTP server unfiltered, and as
> you note, it satisfies your passive port settings.
>
> The second "227" response started at the FTP server, and was changed by
> your firewall. Your firewall is obviously not just a firewall, but is
> also a "NAT" router - Network Address Translation. That name, although
> common, doesn't describe the full function of the device, because a NAT
> must also translate ports - some people have even tried to get the term
> NAPT to be used as a result, to express that ports and addresses are
> translated.
You're right there is a NAT router (with port forwarding for incoming PASV
port range) connected to bring the whole LAN into the internet ...
But I'm sure that the NAT router doesn't change the FTP response showing in
the 2nd answer. Certainly the router will dynamically map in/out TCP ports
of all packets to match the 1:n relation for WAN access but if the router
handle FTP access explicity the external connections should work fine but
in real-life the data connections couldn't be established as mentioned
before.
[quoted text, click to view] > If you can run a Network Monitor capture on the side of the network
> inside the firewall, you should find that the ports are being correctly
> requested in the range you have asked for. Your router may be
> configurable to choose what range of ports to map PASV responses into.
I will check the port range by installing ethereal on the NAT router ...
--
cu
o.pfeiffer
ICQ# 84320006
eMail oliver.pfeiffer@gmx.net
--------------------------------------------