I mean the NAT router that is closest to the server.
Alun.
~~~~
--
Software Design Engineer, Internet Information Server (FTP)
This posting is provided "AS IS" with no warranties, and confers no rights.
[quoted text, click to view] "felix" <felix(NO-SPAM)@eastop.com> wrote in message
news:%23LSA3Wr$EHA.936@TK2MSFTNGP12.phx.gbl...
> Thanks for your reply. However, there shouldn't be any NAT settings on the
> server as it just has a private IP address and that's it.
> Or do you mean I need to contact my ISP for the NAT router settings?
>
>
> "Alun Jones [MSFT]" <alunj@online.microsoft.com> wrote in message
> news:e37QhRk$EHA.3700@tk2msftngp13.phx.gbl...
>> "felix" <felix(NO-SPAM)@eastop.com> wrote in message
>> news:uha6kzd$EHA.1296@TK2MSFTNGP10.phx.gbl...
>>>I have configured FTP service on IIS 6.0, and I can connect to it by PORT
>>>mode.
>>>
>>> However, if I connect by PASV, I will be stuck on the "PASV" command.
>>> What is strange is that, if I change the listening port from 21 to
>>> something else(I tried 22 and 5000), I will get a message of "Private IP
>>> address returned by the server in response to PASV command. Converting
>>> private IP address 192.168.X.X(my server priv IP) to public IP address
>>> X.X.X.X(my server pub IP)", and I will be able to connect and LIST. I am
>>> trying to connect outside office via public IP, and I use FTP Voyager as
>>> my client program.
>>>
>>> DMZ has been set to forward all traffic from the my server's public IP
>>> to my server's private IP. What else can go wrong in this situation?
>>
>> This indicates that the NAT router at the server is converting the
>> private IP address to a public IP address - but the wrong public IP
>> address. Check the server's NAT configuration.
>>
>> Alun.
>> ~~~~
>>
>
>