hi, this might have been asked before, but i have searched and havent seen anything that i can really use.

Anyway, i am running slack9.0 and i had proftpd working fine, until i updated but then the hd died, so i got a newer, bigger one (2.1gb, its an old computer - celery 500 or so, cat /proc/cpuinfo says 434 but anyway) so i installed slack9.0 again, this time with a bit more stuff since i have more room.

I try to get proftpd going again, but i get this error message:
WS_FTP Pro, Version 7.5, 2002.02.28
Connecting to 192.168.1.7:21
Connected to 192.168.1.7:21 in 0.015, Waiting for Server Response
Connection closed by remote host.


My proftpd.conf looks like this:

# This is a basic ProFTPD configuration file (rename it to
# 'proftpd.conf' for actual use. It establishes a single server
# and a single anonymous login. It assumes that you have a user/group
# "nobody" and "ftp" for normal operation and anon.

ServerName "Sgarrista"
ServerType standalone
DefaultServer on

# Port 21 is the standard FTP port.
Port 21

# Umask 022 is a good standard umask to prevent new dirs and files
# from being group and world writable.
Umask 022

# 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 under which the server will run.
User nobody
Group nogroup

# To cause every FTP user to be "jailed" (chrooted) into their home
# directory, uncomment this line.
DefaultRoot ~

# Normally, we want files to be overwriteable.
<Directory />
AllowOverwrite on
</Directory>

# A basic anonymous configuration, no upload directories. If you do not
# want anonymous users, simply delete this entire <Anonymous> section.
<Anonymous ~ftp>
User ftp
Group ftp

# We want clients to be able to login with "anonymous" as well as "ftp"
UserAlias anonymous ftp

# 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
<Limit WRITE>
DenyAll
</Limit>
</Anonymous>



I can ssh etc to it no problem, i was thinking maybe it was the firewall, but i have no idea about the firewall. Any help at all will be very very very much appreciated, it has me stumped, but then again im pretty newbie :P

*bump*

The firewall is my first suspicion, too.

You can check what firewall rules you have by "iptables -nL" (Drop the "n" if you want names instead of numbers. It's quite a bit slower that way, though.)

If it says "ACCEPT" as a policy on all chains, your firewall is "off", and it can't be part of the problem. I haven't set up a slackware system in quite a while, so I'm not sure exactly how you manipulate it, but on most distros, there will be a file like /etc/init.d or /etc/rc.d/init.d that will have all your startup/shutdown scripts. Say something like "/etc/rc.d/init.d/iptables stop", and that should turn it off (assuming it's on).

If you have the problem with the firewall up, and not with it down, the firewall's your problem. I can help some with the configuration to allow FTP through, but I don't want to try tackling that until I know that's actually the problem.

I would have said xinetd, but if you're running this as a standalone service, that's not going to be an issue.

One thought -- you did double check that proftpd was running when you were trying the ftp, right?

One thing you might try -- ftp to the machine from itself. If that works, that tends to point again at firewall issues.

Hope this helps,

CHL

P.S. "Bumping" might or might not be a good idea. I usually go through looking for things with 0 replies, and usually go back at least a day or two. 'Course, that presumes that some of my ramblings are going to help... <g>

Sorry, completely ignore my post. I thought ws_ftp was another server running on the same machine. Doh!

Thanks for your help, but i have reformatted today, and this time didnt install a firewall, to make sure that it wasn't this at all. It still happens. If i open an ftp connection to either Localhost or 192.168.1.7 it gives the same error message.

Any other ideas?

The only differences i have from the last time i had proftpd working fine was that i was using ext2 and now reiserfs. Also i have program development tools now and possibly some others in other catagories, but not too many.

Btw whats wrong with WS_FTP?

[edit]
I also have virtual server setup left on my router from the last working install, so i could get people other than myself to test it, i tried again, and they get the same message. Not really needed to post that, since ive tried 2 different clients, but just to solidify that fact :P
[/edit]

[edit2]
I just JOE'd my proftpd.conf, and it has lighter white M's at the end of lines. I edited the script on my xp comp (this one) and put it accross on disk. I did this last time and i didn't see the M's. It doesnt come up on vi, however. Also if i execute proftpd with the test config file option it comes back alright.
[/edit2]

Initially it appeared to me that ws was another ftp server runnin on the computer. I guess it looks that way when you read the post at 1 in the morning. You need to watch out when you edit files on windows machines. Some editors will alow you to save files in unix form so that you can directly upload it without any modification. I use EditPad Lite and it works just well. From the unix box, you can run dos2unix and it will convert the file for you. I assume that it works now, right?

I downloaded this conf: http://proftpd.linux.co.uk/docs/configs/basic.conf
and copied it accross, Joe shows none of those white M's, but i still have the same problem!

I tried connecting before i typed proftpd into the machine and i got the same error message. I then logged on, and type proftpd -d 9 to see what was happening:

root@sgarrista:~# proftpd -d 9
- parsing '/etc/proftpd.conf' configuration
- FS: using system open()
- FS: using system read()
- dispatching auth request "getpwnam" to module mod_auth_file
- dispatching auth request "getpwnam" to module mod_auth_unix
- dispatching auth request "getgrnam" to module mod_auth_file
- dispatching auth request "getgrnam" to module mod_auth_unix
- FS: using system read()
- <Directory />: adding section for resolved path '/'
- FS: using system read()
- FS: using system close()
sgarrista.sgarrista -
sgarrista.sgarrista - Config for ProFTPD Default Installation:
sgarrista.sgarrista - ~ftp/
sgarrista.sgarrista - Limit
sgarrista.sgarrista - DenyAll
sgarrista.sgarrista - UserName
sgarrista.sgarrista - GroupName
sgarrista.sgarrista - UserAlias
sgarrista.sgarrista - MaxClients
sgarrista.sgarrista - DisplayLogin
sgarrista.sgarrista - DisplayFirstChdir
sgarrista.sgarrista - Umask
sgarrista.sgarrista - /
sgarrista.sgarrista - AllowOverwrite
sgarrista.sgarrista - Umask
sgarrista.sgarrista - DefaultServer
sgarrista.sgarrista - Umask
sgarrista.sgarrista - UserID
sgarrista.sgarrista - UserName
sgarrista.sgarrista - GroupID
sgarrista.sgarrista - GroupName
sgarrista.sgarrista - dispatching auth request "getgroups" to module mod_auth_file
sgarrista.sgarrista - dispatching auth request "getgroups" to module mod_auth_unix
sgarrista.sgarrista - SETUP PRIVS at main.c:2618
sgarrista.sgarrista - ROOT PRIVS at main.c:1909
sgarrista.sgarrista - RELINQUISH PRIVS at main.c:1915
root@sgarrista:~#



i think ill try another server service, apache for instance, just to see if its more widespread than ftp. Any more ideas are greatly appreciated.

Ill also add the output from a netstat -a after a failed attempt, might be useful:

root@sgarrista:~# netstat -a
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 *:time *:* LISTEN
tcp 0 0 *:submission *:* LISTEN
tcp 0 0 *:finger *:* LISTEN
tcp 0 0 *:auth *:* LISTEN
tcp 0 0 *:ftp *:* LISTEN
tcp 0 0 *:ssh *:* LISTEN
tcp 0 0 *:smtp *:* LISTEN
tcp 0 0 sgarrista.sgarrista:ftp 192.168.1.2:1700 TIME_WAIT
tcp 0 0 sgarrista.sgarrista:ssh 192.168.1.2:here-lm ESTABLISHED
udp 0 0 *:biff *:*
udp 0 0 *:ntalk *:*
udp 0 0 *:time *:*
Active UNIX domain sockets (servers and established)
Proto RefCnt Flags Type State I-Node Path
unix 6 [ ] DGRAM 236 /dev/log
unix 2 [ ] DGRAM 341
unix 2 [ ] DGRAM 270
unix 2 [ ] DGRAM 264
unix 2 [ ] DGRAM 239

Is proftpd running when you do ps -A? Which version of proftpd are you running? Did you download the rpm or compile it from source?