On Linux, it could be called ip_conntrack, nf_conntrack, nf_conntrack_ftp or nf_conntrack_proto_ftp depending on the version. Check if you don't have them blocked in the firewall and if the FTP shim is even loaded. That said, the FTP shim in the NAT should create that port mapping automatically as a RELATED connection. The reason being that the "lower" numbers in the thousands get used by other traffic a lot whereas the higher ones tend to remain quiet. The tutorial linked shows 6001-6001, but I recommend that you do something like 60000-61000. Then forward that same range on the NATing router to the internal IP of your server. The better way is to find a way to limit the range of passive ports used and forward that range to your server. I think that if you just made a DMZ and let everything through, it would start working. The most likely cause is you not letting the ephemeral ports through. I understand you have NAT going on and the server has a private address. Response: 200 OPTS UTF8 command successful - UTF8 encoding now ON.Įrror: Failed to retrieve directory listing Response: 211-Extended features supported: Status: Connection established, waiting for welcome message. On my network firewall (Cisco), I added a rule to forward port 21 traffic to FTP Server. I testing with Windows Firewall Turned off and on (I added windows firewall rule for port 21). I set up basic authentication, non-ssl, not allowing anonymous.
I did not configure FTP Wirewall Support on the FTP site. Note FileZilla resolved domain name and authenticates.
Using FileZilla, I get the following messages. Page eventually times out and I get "Internet Explorer cannot display page". From the outside, IE FTP prompts me to enter my username/pwd, but nothing happens. On the outside, I am testing with FileZilla and IE FTP. On the inside I tested using cmd prompt and IE FTP. I am able to connect from the inside, but not from the outside. I configured FTP Service/Role on my Windows Server 2008 R2 machine.
0 kommentar(er)
