i have proftpd set up behind a linksys router and configured the port fowarding and ranges per the documents on the proftpd web site. (NAT configuration). The problem is that when logging in, it seems a little slow and when it authenticates... it hangs while trying to list the directories???

any ideas??

Thanks..

Wel since it's able to connect you've got the setup for the control connection done right. For listings of directories it tries to open a data connection to send the listing across. Well some allow listings for directories with very few entries to go across the control connection. But most likely this connection is not allowed or blocked somewhere. You mentioned the linksys router forwards the range of ports, so I assume you've got that part setup properly. It could still be a local firewall blocking it or maybe some errors you made in the configuration.
Could you post the relative parts of your configuration file?

About the slow login, my guess would be that it's slow because it's trying to do either a reverse dns lookup which fails or an ident request. So you might want to disable those or set them up to work properly. Ofcourse there could be other reasons, are you using any other type of authentication protocols?

Well I had this issue for a while, I don't know what caused it, but it degraded into not having any shells in the /etc/passwd, try doing a chsh *user* /bin/sh if it just refuses logins from the start

otherwise, it can be caused by not allowing passive mode, so try try turning it off client side

I'm not to clear on the shells solution and passive mode is set on the client side ftp programs. Here is my conf file. If you see any error in why it will not list my directories, please post...

I have even put the ftp server computer on the dmz so as to eliminate any firewall config problems. The client is still inside the router and still the same results....login ok....freeze up on listing directories........time out......

ServerName "Mine"
ServerType inetd
DefaultServer on
Port 21
Umask 022
MaxInstances 30

User me
Group me
AllowStoreRestart on

<Directory /home/me>
AllowOverwrite on
</Directory>

PassivePorts 51200 51299

If you're running passice mode you need your firewall to allow TCP ports 1024 -> 65535 to be open for inbound connections.

Read up on 'passive' vs. 'active' FTP sessions. Give yourself a good scare and then look at proxy ftp. ( I see that Debian has a package for it so it looks to be generally available.)

So your saying I will have to allow the client to recieve all those open ports?

I followed the directions here....http://proftpd.linux.co.uk/localsite...nked/x861.html
in learning about what ports needed to be open. I just assumed that they were talking about the ports for the server.

But, anyway, I put the ftp server outside the router firewall, (dmz) so I am assumming i have eliminated any port problems with the ftp protocol??

I have even gone as far as to foward ports on the client!! But that hardly makes any sense because I can ftp into other ftp servers correctly with no port fowarding on this client machine!! Still, no workey.

To recap, my ftp server machine is in the dmz of a linksys router....i know this is working because i have apache up and running and can log into my website. ALSO, i have no trouble listing direcotries or any other command when i ftp from the server to localhost, ie. ftp...open ....localhost...it works fine. BUT when i try to use my laptop from INSIDE the router with ws_ftp set to use passive or active mode.....no workey.....hangs while trying to list directories.

Still trying but running out of ideas...

UPDATE

After hours of goofing with every configuration I could think of, I at least got it to work....kinda a.....

I believe the problems I'm having is the router/firewall stuff. I changed the settings on ws_ftp to active mode and I can connect with that setting from a client computer inside the network....but not with any browser...netscape or ie....

Therefore....I still have work to do....

Thanks for all replies......

If I remember correctly there where issues with connecting to a ftp server from behind a firewall if the client is also behind the firewall. It had to do something with both sides being masqueraded. I don't remember the exact cause of why it happened. It's an old problem and has been fixed, at least it doesn't occur anymore with the linux router I use. I don't know about your firewall though.
But you could test this by trying to connect to your ftp server from outside of your network.
Sorry for the vague answer, but I'm sure a search on google will get you a bit more information.