I have a stable server running Mandriva 2009.1 in a typical LAMP configuration with a few other things. I have ProFTPd running on there with no problems, and it's set up so each user can login and read/write their home directory. Everything is setup out of box as much as I can remember - it's been a long time since I set it up.
So I built an identical system for another guy except for hardware and a few other utilities he's not going to use and cannot for the life of me get read/write access to anything from ProFTPd. As far as I know everything is the same - I located and compared all proftpd files that mattered and they are all the same. The port's open in shorewall, everyone has permissions on their own directories, etc.
I can connect to the box and login. When I login (FireFTP) it shows the login and password prompts, etc, and the last command is (from memory) LIST -al or something like that which I assume is supposed to display the directory contents - then it just sits there, times out after maybe a minute and then does a "reconnecting in 10 seconds" bit.
It displays the home base directory and the user's directory beneath it and shows that it's selected, but does not display the rest of the tree under the user's directory or any of the other contents. If I select a file on my PC and try to upload it just sits there and does nothing, times out and reconnects.
I am at a loss as to why my identically configured system works and this one doesn't. I haven't modified the OOB proftpd.conf file at all - haven't even removed the comment tick from the 'DirectoryRoot' (sp?) argument that is supposed to lock users into their own directory.
Any suggestions would be appreciated.
My current line of thought is that my working system is configured static and direct to the outside, and this system (right now) is configured as 192.168.1.100 (static) behind a Linksys consumer router that has is listed as the DMZ host and additionally has ports 20 - 22, 80 and 10000 routed to that box. He is in the process of getting a few more static IP's from Comcast and then the box will be on a dedicated 'real' IP. Do you think the Linksys is interfering with the file transfer stuff somehow, even though I can connect and login?
So I built an identical system for another guy except for hardware and a few other utilities he's not going to use and cannot for the life of me get read/write access to anything from ProFTPd. As far as I know everything is the same - I located and compared all proftpd files that mattered and they are all the same. The port's open in shorewall, everyone has permissions on their own directories, etc.
I can connect to the box and login. When I login (FireFTP) it shows the login and password prompts, etc, and the last command is (from memory) LIST -al or something like that which I assume is supposed to display the directory contents - then it just sits there, times out after maybe a minute and then does a "reconnecting in 10 seconds" bit.
It displays the home base directory and the user's directory beneath it and shows that it's selected, but does not display the rest of the tree under the user's directory or any of the other contents. If I select a file on my PC and try to upload it just sits there and does nothing, times out and reconnects.
I am at a loss as to why my identically configured system works and this one doesn't. I haven't modified the OOB proftpd.conf file at all - haven't even removed the comment tick from the 'DirectoryRoot' (sp?) argument that is supposed to lock users into their own directory.
Any suggestions would be appreciated.
My current line of thought is that my working system is configured static and direct to the outside, and this system (right now) is configured as 192.168.1.100 (static) behind a Linksys consumer router that has is listed as the DMZ host and additionally has ports 20 - 22, 80 and 10000 routed to that box. He is in the process of getting a few more static IP's from Comcast and then the box will be on a dedicated 'real' IP. Do you think the Linksys is interfering with the file transfer stuff somehow, even though I can connect and login?