07-02-2012 09:53 AM - edited 03-04-2019 04:51 PM
I have been trying to get my FTP server working for months with no joy. It works when I connect to it internally but not from outside. If I do a port scan, I can see that port 21 is open. I tried it with disabled firewalls and also checked with ISP that nothing is being blocked. I have attached the config file. Would appreciate any help on this as it is driving me crazy. I used several differnet FTP servers such as CoreFTP, Wing FTP etc. Thanks, Simon
07-02-2012 10:17 AM
Can you open port 21 from the router? From the CLI of the Router enter this command and hit enter. What happens?
telnet 192.168.1.250 21
James
07-02-2012 12:15 PM
Hi Pompeychimes,
Yes that works.
DISEEM#telnet 192.168.1.250 21
Trying 192.168.1.250, 21 ... Open
220 Wing FTP Server ready... (UNREGISTERED WING FTP SERVER)
Simon
07-02-2012 12:22 PM
Now source it from the outside interface of the Router...
telnet 192.168.1.250 21 /source-interface atm0.1
what happens?
07-02-2012 12:30 PM
Same thing, seems to be fine.
DISEEM#telnet 192.168.1.250 21 /source-interface atm0.1
Trying 192.168.1.250, 21 ... Open
220 Wing FTP Server ready... (UNREGISTERED WING FTP SERVER)
07-02-2012 12:35 PM
OK, from device on the Internet or a site like this http://ping.eu/port-chk/ try to open ftp. Meanwhile on the router look at the output of the "sh ip nat trans" command. Do you see a translation for your ftp attempt?
07-02-2012 01:03 PM
This is what I got:
(I changed my ip address)
tcp 198.200.18.60:51006 192.168.1.39:51006 77.238.187.43:80 77.238.187.43:80
tcp 198.200.18.60:51007 192.168.1.39:51007 77.238.187.43:80 77.238.187.43:80
tcp 198.200.18.60:51008 192.168.1.39:51008 77.238.187.43:80 77.238.187.43:80
tcp 198.200.18.60:20 192.168.1.250:20 --- ---
tcp 198.200.18.60:21 192.168.1.250:21 88.198.46.51:35611 88.198.46.51:35611
tcp 198.200.18.60:21 192.168.1.250:21 88.198.46.51:35627 88.198.46.51:35627
tcp 198.200.18.60:21 192.168.1.250:21 --- ---
tcp 198.200.18.60:22 192.168.1.250:22 --- ---
tcp 198.200.18.60:51521 192.168.1.250:51521 76.164.220.46:80 76.164.220.46:80
tcp 198.200.18.60:51522 192.168.1.250:51522 76.164.220.46:80 76.164.220.46:80
Pro Inside global Inside local Outside local Outside global
tcp 198.200.18.60:65163 192.168.1.250:65163 77.234.43.55:80 77.234.43.55:80
tcp 198.200.18.60:65168 192.168.1.250:65168 208.43.71.133:80 208.43.71.133:80
tcp 198.200.18.60:65169 192.168.1.250:65169 184.169.78.96:80 184.169.78.96:80
tcp 198.200.18.60:65170 192.168.1.250:65170 184.169.78.96:80 184.169.78.96:80
tcp 198.200.18.60:65171 192.168.1.250:65171 184.169.78.96:80 184.169.78.96:80
tcp 198.200.18.60:65172 192.168.1.250:65172 173.194.41.174:80 173.194.41.174:80
07-02-2012 01:12 PM
I'll assume these are your attempts...
tcp 198.200.18.60:21 192.168.1.250:21 88.198.46.51:35611 88.198.46.51:35611
tcp 198.200.18.60:21 192.168.1.250:21 88.198.46.51:35627 88.198.46.51:35627
If so it looks good.
Is your FTP Server's DFG 192.168.1.254?
What actually happens when you attempt the FTP. Does is just hang, do you get a header, a prompt for credentials maybe, etc...
James
07-02-2012 01:18 PM
Hi james,
Yes.
It gives me :
500 Connection refused (Winsock error #10061) which is odd, because it works from inside to username and password definitely correct.
How does one do PMs in here? Maybe I can give you access and you could try from your end?
Thanks,
Simon
07-02-2012 01:34 PM
I was able to login. I replied to your PM.
07-02-2012 01:40 PM
its so bizzare, I still can't. I tried with FTP Commander and filezzila and a different internet line. I am using windows 7. Could windows block something? Although I can log onto other FTP servers. So odd
07-02-2012 09:32 PM
hi,
could you re-configure static NAT to use the WAN IP instead and try again from outside? make sure FW/AV are disabled when doing your test.
no ip nat inside source static tcp 192.168.1.250 21 interface ATM0.1 21
ip nat inside source static tcp 192.168.1.250 21 198.200.18.60 21
07-03-2012 04:21 AM
Hi John,
I have done this but still now joy. same problem. I did check the port is open etc.
Thanks,
Simon
07-04-2012 03:56 AM
hi simon,
i guess your config should be ok. i think your next option would be an IOS upgrade.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide