I've setup using the howto for a ubuntu 6.06 setup. I can access the ftp service via the web interface however when i use an ftp client i get a timeout that occurs while waitng for the welcome message. This occurs whether i use the domain name or internal LAN address. I don't know where to look next Status: Resolving IP-Address for adm-computers.co.uk Status: Connecting to 88.212.178.62:21... Status: Connection established, waiting for welcome message... Error: Connection timed out Error: Could not connect to server I have tried with both passive and active modes and even added extra lines i've found in other forum posts in /etc/proftpd.conf. Heres my proftpd.conf file # # /etc/proftpd.conf -- This is a basic ProFTPD configuration file. # To really apply changes reload proftpd after modifications. # UseIPv6 off ServerName "Debian" ServerType standalone DeferWelcome off UseReverseDNS off IdentLookups off ServerIdent on "FTP Server ready." MultilineRFC2228 on DefaultServer on ShowSymlinks on TimeoutNoTransfer 600 TimeoutStalled 600 TimeoutIdle 1200 DisplayLogin welcome.msg DisplayFirstChdir .message ListOptions "-l" DenyFilter \*.*/ # Uncomment this if you are using NIS or LDAP to retrieve passwords: #PersistentPasswd off # Uncomment this if you would use TLS module: #TLSEngine on # Uncomment this if you would use quota module: #Quotas on # Uncomment this if you would use ratio module: #Ratios on # Port 21 is the standard FTP port. Port 21 # 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) MaxInstances 30 # Set the user and group that the server normally runs at. User nobody Group nogroup # Umask 022 is a good standard umask to prevent new files and dirs # (second parm) from being group and world writable. Umask 022 022 # Normally, we want files to be overwriteable. AllowOverwrite on # Delay engine reduces impact of the so-called Timing Attack described in # http://security.lss.hr/index.php?page=details&ID=LSS-2004-10-02 # It is on by default. #DelayEngine off # A basic anonymous configuration, no upload directories. # <Anonymous ~ftp> # User ftp # Group nogroup # # We want clients to be able to login with "anonymous" as well as "ftp" # UserAlias anonymous ftp # # Cosmetic changes, all files belongs to ftp user # DirFakeUser on ftp # DirFakeGroup on ftp # # RequireValidShell off # # # Limit the maximum number of anonymous logins # MaxClients 10 # # # We want 'welcome.msg' displayed at login, and '.message' displayed # # in each newly chdired directory. # DisplayLogin welcome.msg # DisplayFirstChdir .message # # # Limit WRITE everywhere in the anonymous chroot # <Directory *> # <Limit WRITE> # DenyAll # </Limit> # </Directory> # # # Uncomment this if you're brave. # # <Directory incoming> # # # Umask 022 is a good standard umask to prevent new files and dirs # # # (second parm) from being group and world writable. # # Umask 022 022 # # <Limit READ WRITE> # # DenyAll # # </Limit> # # <Limit STOR> # # AllowAll # # </Limit> # # </Directory> # # </Anonymous> DefaultRoot ~
It seems i have found the culprit on my machine after looking at this thread http://www.howtoforge.com/forums/showthread.php?t=6447&highlight=windows+firewall however if i disable windows firewall it works but if i enable it and open the ports mentioned I still get the same problem. Anyone have a work around? Maybe install zonealarm or another recommended firewall in place of the windows crap!!
I used the free firewall from comodo which works a treat but i'm not sure how customers will take it if they use windows firewall and won't switch to something else. What other ports would the FTP possibly use apart from 21. I read somewhere that the passive mode also may need other ports open!! Could anyone give advice on this
