PDA

View Full Version : proftpd connection problems



dec
07-21-2004, 09:21 PM
Hi ..

One of my clients is complaning about connection to my ftp server been dropped. This is the message he gets:

An established connection was aborted by the software in your host machine. Connection closed

Any ideas?

Please help!

Dec

dec
07-22-2004, 11:46 PM
Any Ideas? Help

Dec

jmstacey
07-23-2004, 01:13 AM
If no other users are experiencing this problem, I would say its something with the users isp.
Have him try creating another account to see if he experiences the same problem or using his ip address to test.

Reyner
12-07-2006, 07:00 PM
I just got this problem after renumbering one of our servers with new IP. Here is the error message I had:

[17:45:47] Connecting to <IP address> Port: 21
[17:45:47] Connected to <hostname>
[17:45:48] An established connection was aborted by the software in your host machine.
[17:45:48] Server closed connection

and

Connection to <hostname>
Connection closed by remote host.

Problem:

In /etc/proftpd.vhost.conf, I found out:

<VirtualHost *.*.*.*>
ServerName "ProFTPd"
ExtendedLog /var/log/proftpd/*.*.*.*.bytes WRITE,READ userlog
AuthUserFile /etc/proftpd.passwd
</VirtualHost>

where *.*.*.* is the main server IP

Solution:

Comment this section and do:

service proftpd restart

Hope this helps for those who has similar issue.

Best regards,

Reyner Natahamidjaja
reyner@globalcon.net
http://globalcon.net

gcypher
12-07-2006, 11:56 PM
I dont think commenting out the proftpd.passwd file will help you (or your clients).!!!!!!!!!!!!!!!!!!!!!

Reyner
12-08-2006, 06:09 AM
Originally posted by gcypher
I dont think commenting out the proftpd.passwd file will help you (or your clients).!!!!!!!!!!!!!!!!!!!!! Hello,

You're right, commenting out proftpd.passwd file will not help. However, the post above was regarding /etc/proftpd.vhost.conf and not proftpd.passwd file.

Best regards,

Reyner Natahamidjaja
reyner@globalcon.net

gcypher
12-08-2006, 06:39 AM
Yeap i guess i understood you're post wrong then .. :D

Best Regards

Michel

nobaloney
12-08-2006, 02:08 PM
Can anyone explain why this helps? Why it would help?

Jeff

DirectAdmin Support
12-08-2006, 09:46 PM
THe main server IP should not be in the proftpd.vhosts.conf.
This is because it's loaded as the default (what the hostname resolves to) in the "base" setup with the basic /etc/proftpd.conf file. If it's in the proftpd.vhosts.conf then it would be loaded into proftpd twice, thus breaking it and not allowing proftpd to start (which is bad).

The cause of this is usually the server IP not being set as the server IP in:
/usr/local/directadmin/data/admin/ips/1.2.3.4

where 1.2.3.4 would be the server IP. In that file, there should be a line that says:

status=server

if it's set to shared, owned or free.. then it's wrong and should be set to "server". There should be exactly 1 IP file with status=server in it, no more, no less.

John

Reyner
12-08-2006, 10:20 PM
John,

Thank you for the crystal clear explanation. You guys are the best!

Regards,

Reyner Natahamidjaja
reyner@globalcon.net