05-07-2009 05:55 AM - edited 03-06-2019 05:35 AM
I've configured my Router but I'm not able to get FTP working. I've NAT setup to IP address of FTP Server for port 20 & 21. Do I need to do more to get FTP working on Router?
Solved! Go to Solution.
05-12-2009 02:50 PM
on web browser
tools-internet options- advanced tab- uncheck passive FTP box
05-07-2009 06:45 AM
Paste in your config...
05-07-2009 06:59 AM
05-07-2009 08:11 AM
Is any traffic working to 213.94.226.58?
05-07-2009 08:24 AM
Hi, I think I need to put in a ACL forwarding or allowing ftp traffic. Not what Rules are required.
My FTP server is a windows sbs 2003
05-07-2009 11:56 AM
I bet the problem is with high port numbers. Add this to your CBAC inspect list:
ip inspect name SDM_HIGH ftp
05-08-2009 05:55 AM
I don't think this is the issue as I've not set the firewall to low so the config now has the line ... ip inspect name SDM_LOW ftp
05-08-2009 08:17 AM
I know its obvious but is the FTP Server up and running and can you connect to it from inside your network.?
05-08-2009 11:07 AM
Denis,
Is your ftp server running with passive mode? If so, You may need a static NAT to accomplish this. Because the server will tell you to randomly use a range of udp ports(1024-65535) to send data. It's not easy to define NAT statement including udp ports.
HTH,
Toshi
05-11-2009 12:59 AM
The FTP Server is running as I'm able to access the FTP Server from inside the Network.
I have nat in place
ip nat inside source static tcp 10.10.10.10 20 xxx.xxx.xxx.58 20 extendable
ip nat inside source static tcp 10.10.10.10 21 xxx.xxx.xxx.58 21 extendable
05-11-2009 03:51 AM
I believe IIS uses Active FTP by default.
05-11-2009 09:22 AM
Denis,
what's the exact error you got? Did you pass the authentication process? Can you send/receive any data to/from the server?
Toshi
05-12-2009 02:50 PM
on web browser
tools-internet options- advanced tab- uncheck passive FTP box
05-13-2009 12:39 AM
This is the answer but it came a day late as I had to pay 75euro for the answer.
There was I thinking it was a cisco problem but it was an IE issue.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: