A little history here: my ISP blocks access to port 80, 21, and others that are unknown. Now, as a little sysadmin practice (I'm about as geeky as they come
), I decided to set up a webserver, FTP server, and eventually a POP3/SMTP server. So, I configured Apache, and got it working with a Port 80 Redirect (courtesy of no-ip.org) and got my proftpd server running on port 21000. As of yesterday, eerything was running flawlessly. Now, proftpd is not accepting connections. When I try to connect using:
ftp 127.0.0.1 21000
it works without a hitch. I can login, do everything without a problem. Now, if I use my global IP, we'll say www.example.org,
it won't work. I get this error message:
This is my /etc/proftpd.conf file:
# This is a basic ProFTPD configuration file.
# It establishes a single server and a single anonymous login.
# It assumes that you have a user/group "nobody" and "ftp"
# for normal/anonymous operation.
# ServerType inetd
# Port 21 is the standard FTP port.
# Umask 022 is a good standard umask to prevent new dirs and files
# from being group and world writable.
# To prevent DoS attacks, set the maximum number of child processes
# to 30. If you need to allow more than 30 concurrent connections
# at once, simply increase this value. Note that this ONLY works
# in standalone mode, in inetd mode you should use an inetd server
# that allows you to limit maximum number of processes per service
# (such as xinetd)
# Set the user and group that the server normally runs at.
# This next option is required for NIS or NIS+ to work properly:
# Normally, we want files to be overwriteable.
Any ideas on this? As the server yesterday was working without a hitch...
More info: The port is allowed both locally and globally (enabled access through port 21000 in GuardDog for both Network and Internet