PROFTPD with MYSQL virtual users

[MisterVlad]

I have followed the tutorial for the Debian ETCH isntall (which i have done many times prior), and this time i have issues.

For some reason, no matter what I do, i cannot connect to the FTP.

the netstat shows it running, everything shows that it should be running and accepting connections, yet when i try to get there, i can't.

the log files show that there is a 'closed connection' every attempt i have tried, but yet there is no 'open connection'. I have followed the turotial over and over trying to figure out where i went wrong, but I can't seem to find anything!

Please help... maybe give me some direction... i am at a loss :(

Mistervlad

[falko]

Can you post the exact errors from your logs?
What's the output of netstat -tap and iptables -L?

[MisterVlad]

netstat -tap
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 *:20000 *:* LISTEN 2820/perl
tcp 0 0 *:225 *:* LISTEN 2167/sbadm
tcp 0 0 *:10246 *:* LISTEN 2823/perl
tcp 0 0 localhost.localdo:10024 *:* LISTEN 2221/amavisd (maste
tcp 0 0 localhost.localdo:10025 *:* LISTEN 2652/master
tcp 0 0 *:mysql *:* LISTEN 2283/mysqld
tcp 0 0 *:sunrpc *:* LISTEN 1937/portmap
tcp 0 0 *:auth *:* LISTEN 2590/inetd
tcp 0 0 *:ftp *:* LISTEN 2765/proftpd: (acce
tcp 0 0 *:56153 *:* LISTEN 2734/rpc.statd
tcp 0 0 *:smtp *:* LISTEN 2652/master
tcp6 0 0 *:imaps *:* LISTEN 2537/couriertcpd
tcp6 0 0 *:pop3s *:* LISTEN 2573/couriertcpd
tcp6 0 0 *:pop3 *:* LISTEN 2555/couriertcpd
tcp6 0 0 *:imap2 *:* LISTEN 2523/couriertcpd
tcp6 0 0 *:www *:* LISTEN 2797/apache2
tcp6 0 0 *:ssh *:* LISTEN 2682/sshd
tcp6 0 0 *:https *:* LISTEN 2797/apache2
tcp6 0 2668 etch.990webs.ca:ssh WNDSON12-12793800:61581 ESTABLISHED7079/sshd: *******


iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination



and on another note, I am not able to send email from my server from my outlook? I can do it through webmail (squirrelmail), but not through outlook. I have it set up as it is outlined in the tutorial 'Virtual Users And Domains With Postfix, Courier And MySQL (Debian Etch)'. I have it set to authorize using my name and password, but it doesn't like it :(

[falko]

netstat -tap
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 *:20000 *:* LISTEN 2820/perl
tcp 0 0 *:225 *:* LISTEN 2167/sbadm
tcp 0 0 *:10246 *:* LISTEN 2823/perl
tcp 0 0 localhost.localdo:10024 *:* LISTEN 2221/amavisd (maste
tcp 0 0 localhost.localdo:10025 *:* LISTEN 2652/master
tcp 0 0 *:mysql *:* LISTEN 2283/mysqld
tcp 0 0 *:sunrpc *:* LISTEN 1937/portmap
tcp 0 0 *:auth *:* LISTEN 2590/inetd
tcp 0 0 *:ftp *:* LISTEN 2765/proftpd: (acce
tcp 0 0 *:56153 *:* LISTEN 2734/rpc.statd
tcp 0 0 *:smtp *:* LISTEN 2652/master
tcp6 0 0 *:imaps *:* LISTEN 2537/couriertcpd
tcp6 0 0 *:pop3s *:* LISTEN 2573/couriertcpd
tcp6 0 0 *:pop3 *:* LISTEN 2555/couriertcpd
tcp6 0 0 *:imap2 *:* LISTEN 2523/couriertcpd
tcp6 0 0 *:www *:* LISTEN 2797/apache2
tcp6 0 0 *:ssh *:* LISTEN 2682/sshd
tcp6 0 0 *:https *:* LISTEN 2797/apache2
tcp6 0 2668 etch.990webs.ca:ssh WNDSON12-12793800:61581 ESTABLISHED7079/sshd: *******


iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination

Looks ok. Did you find any other errors in your logs?

and on another note, I am not able to send email from my server from my outlook? I can do it through webmail (squirrelmail), but not through outlook. I have it set up as it is outlined in the tutorial 'Virtual Users And Domains With Postfix, Courier And MySQL (Debian Etch)'. I have it set to authorize using my name and password, but it doesn't like it :(Are there any errors in your logs related to this?

[MisterVlad]

For some reason, it is working now... I dont know what happened, but it works fine now... go figure. If this was windows, then this would be understandable, but since this is linux (Debian Linux), there has to be SOME reason.