> On Wed, 1 Jun 2005 17:45:17 -0700, "Jeff Steinmetz"
> <(E-Mail Removed)> wrote:
>
> >I am using Windows Server 2003, with IIS 6.0 enabled for FTP.
> >It works fine in Active mode (non-pasv). Actually, PASV works fine when
> >using an internal IP address or name for the initial connection.
> >
> >When connecting externally, I have the ports open on my NAT/firewall
> >required for PASV, only problem is IIS returns the "internal" ip address
of
> >its network card when responding to PASV commands.
> >
> >Any way to get around this?
Probably not with your NAT Device. The NAT Device probably has no "filter"
to monitor the PASV Port Information and then translate it to the public
IP#. But you could check the documentation,..maybe you'll get lucky and it
does.
ISA Server can do it with PASV because it has a lot more ability than a
typical NAT Device.
Publishing Secure FTP Servers behind ISA Firewalls
http://www.isaserver.org/tutorials/P...P-Servers.html
The article also indicates that some FTP Servers can allow you to specify an
IP# to use for the Passive Mode data transfer "Source IP", but I don't think
the IIS based FTP can do that.
--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
Similar Threads
Linear Mode
