| ||||
What exactly is the problem you are having? BTW, you DO realize that FTP uses <2>ports, right? |
| ||||
I thought FTP was port 21, and I need to run a second FTP server on the one public address. Problem I'm having I have a two FTP servers, one configured on standard port 21, and a second on port 24. Same address but one is public and one is private. What is happening is the 21 port FTP server works perfectly. Using the website Open Port Check Tool to see what ports are blocked. Port 24 still appears blocked even though I have named the port, NAT'ted it, opened it through the firewall, but still appears blocked. Sorry for long winded response. Does this give you more details? |
| ||||
FTP uses ports 20 and 21. FTP has two different modes of operation: active and passive. In active mode (the default type), the SERVER listens on port 21 (the control channel) for an incoming request. When it receives a request, it responds using port 20 (the data channel) back to the CLIENT, using whatever port the CLIENT indicated when it sent a transfer request to port 21. In passive mode (activated by the client sending the PASV command), the SERVER still listens on port 21 for an incoming request. When it receives one, it responds by telling the CLIENT what port to connect to. The CLIENT then connects to the designated port to finish the transfer. Active transfer mode was the original mode. Because of how it works, it causes heartburn for firewalls and such at the client side (essentially, the firewall has to allow a connection that is initiated from OUTSIDE the firewall to access an arbitrary address and port INSIDE the firewall. For simple packet filters, this is a problem). As a result, passive FTP originated, which allows the server to tell the client to connect to an arbitrary port on the server. This means that the server has to now allow connections to arbitrary ports from the outside world. My point in describing all of this is just this: I suspect that your line class-match type inspect match-any FTP May in fact be smart enough to handle the port 20/21 requirements of FTP, whereas the equivalent line for ftp24 is only handling port 24, not ports 23/24 (which is what you actually need for active FTP). |
| ||||
Well there you. You learn something new everyday. I ended up cheating a little bit, changed the FTP so there is only one server on the default port and it has anon access, but there is a folder contained in there with usernames and passwords applied so anyone can access the first layer, but needs to login to get to any additional layer. Problem solved. Thanks for the info though, I will have to test this at a later date. |
![]() |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Rate This Thread | |
| |
![]() | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Looking to Buy HP/IBM/Sun/Dell/Emulex/Qlogic/Cisco... | PorPorMe | Online Deals, and Steals | 3 | 15th October, 2009 05:47 PM |
Cisco 678 being hammered by a virus today? | cloasters | Mobile Devices and Networking | 0 | 9th October, 2003 08:26 PM |
Cisco Aironet 350 | Samuknow | Mobile Devices and Networking | 5 | 10th July, 2003 05:30 PM |
Dsl and A Cisco 675 | The Spyder | Mobile Devices and Networking | 9 | 4th October, 2001 12:30 AM |