10-04-04 11:01 PM
"Elga" <Elga@discussions.microsoft.com> wrote in message
news:FE39B014-931F-44A7-9325-4CA6FA04B8E2@microsoft.com...
> You can keep your firewall up if you configure it to forward ftp ports (20
> and 21) to your server IP.
No. That's not correct, and could potentially cause harm, as it opens up an
incoming channel that will not be used by the component you are trying to
enable.
Port 21 - yes, this one does need to be allowed for incoming connection
requests.
Port 20, however, needs to be allowed for _outgoing_ connection requests -
the FTP server, in active mode, will bind to its port 20 before connecting
out to the client's random ephemeral port.
In passive mode, the FTP server will listen for incoming connections on a
range of ports, by default from 1024 - 5000 (that can be changed to a
different range) - it is that range that you will need to forward incoming
requests through.
As Bernard has also posted, the page at
http://support.microsoft.com/?id=283679 gives you more detail on this.
> If you want to make your ftp server accesible for external users, you need
> to get an static IP address from your ISP.
... or a dynamic DNS listing for a name. I've run my home connection using
a dynamic IP address quite successfully for many years, just by using one of
many dynamic DNS services. [Look up "dynamic DNS" in your favourite sea
rch
engine to find several]
Alun.
~~~~
[ Post a follow-up to this message ]
| 
