Secure FTP, Port ?

    also secure ftp (sftp) ist normalerweise nur gerade port 22 und läuft über ssh. ich denke du meinst irgend etwas anders.


    ganto


    "Computer games don't affect kids, I mean if Pacman affected us as kids, we'd all run around in a darkened room munching pills and listening to repetitive music."


    Kristian Wilson

    ok, das was du meinst nennt sich ftps (ftp over ssl). aber offenbar wird das auch des öfteren secure ftp genannt. leider ist es nicht ganz so simpel das in einem nat-netzwerk einzurichten.


    The problem is that the FTP protocol is really not too friendly with many firewall/proxy configurations. The problem is that there's two connections between the client and server (the control connection and the data channel) and the data channel is established using commands (PORT and PASV) that communicate IP addresses. Computers behind a NAT have IP addresses that only make sense in the Internal network and not the Internet.


    This is not usually a problem with unencrypted FTP because most NAT's will fix the connection by opening random ports and changing values being communicated in the PORT and PASV commands. Unfortunately, SSL makes it nearly impossible for a NAT to make such a correction.


    If you must use a FTP server using SSL behind a NAT, you should do the following:


    1. Configure your NAT to forward a range ports to your server.
    2. Specify that port range with PASVBoundPortMin and BoundPortMax properties.     [wird wohl beim serv-u etwas anders heissen]
    3. Set the IP address given in PASV replies to your NAT's external Internet IP address using the OnPASVReply event but do not change the IP address for clients that are also on the internal network.


    quelle: http://www.indyproject.org/KB/…l?howdoiuseftpwithssl.htm



    hmn, hier auch noch was (von serv-u):


    NOTE: if your FTP Client can connect with a regular session, but not with SSL enabled then we would recommend checking if there are any NAT enabled device between the FTP Client and Serv-U. The NAT translation is not able to understand the encrypted data being sent between the client and server and thus corrupts the data connection. Currently the only work arounds are to disable the NAT functionality or move Serv-U or the FTP Client in front of the NAT enabled device.


    quelle: http://www.administrator.de/Se…_Hardware-Router-NAT.html


    ich hoffe das hilft dir was.


    ganto


    "Computer games don't affect kids, I mean if Pacman affected us as kids, we'd all run around in a darkened room munching pills and listening to repetitive music."


    Kristian Wilson

    2 Mal editiert, zuletzt von Ganto ()