Apache2Triad Help, Support and Development

[Tyrant_Dictator]

Yes I'm back. Good news is, I've got everything running great on my system. Very pleased with performance and amazed with the simplicity up to this point. My only problem and it's more of a hope than anything else is this.

My Apache installation is located on my D:\ drive (200GB) and I want to have my slimFTP point to my E:\ Drive for the FTP directory. IS there any way to accomplish this? I tried editing my slimftp.conf to look like this, but to no avail:

<User "root">
Password "pass"
Mount / E:\FTP
Allow / All
</User>

What else can I try? Thanks in advance!

[Vlad Alexa Mancini]

That configuration is correct , E:\FTP should be mounted , can you give some details on your problem ? what does the log say when you start the server , what does it say when you conect to it , can you start it ?, can you connect to it ? .. etc

[Tyrant_Dictator]

vlad alexa mancini wrote: That configuration is correct , E:\FTP should be mounted , can you give some details on your problem ? what does the log say when you start the server , what does it say when you conect to it , can you start it ?, can you connect to it ? .. etc

When I try to log into the FTP server, I first try with all the defaults:

<User "root">
Password "pass"
Mount / C:\apache2triad\ftp
Allow / All
</User>

This setup let's me log in fine, it gives me a file list and allows download. But once I switch the directory, it stalls at retrieving the file list. Here is the FTP Client log:

STATUS:> Connect: Sunday 13:54:50 05-01-2005
STATUS:> Connecting to dicksplayground.com
STATUS:> Connecting to dicksplayground.com (ip = ***.***.***.***)
STATUS:> Socket connected. Waiting for welcome message...
220-SlimFTPd 3.16, by WhitSoft Development (www.whitsoftdev.com)
220-You are connecting from ***-***-***-***.dyn.grandenetworks.net:*****.
220 Proceed with login.
STATUS:> Connected. Authenticating...
COMMAND:> USER root
331 Need password for user "root".
COMMAND:> PASS ********
230 User "root" logged in.
STATUS:> Login successful
COMMAND:> TYPE I
200 TYPE command successful.
COMMAND:> pwd
257 "/" is current directory.
COMMAND:> TYPE A
200 TYPE command successful.
STATUS:> Retrieving directory listing...
COMMAND:> PORT ***,***,*,**,*,***
200 PORT command successful.
COMMAND:> LIST
150 Opening active mode data connection for listing of "/*".
425 Can't open data connection.

Hope this helps you help me! Thanks for your a dedicated guy!

--Rick

[Rlyeh]

Some moths ago I had exactly this same problem you have now, and I solved it by...
checking for correct slashes
Yes, it's weird, but it worked for me.
i.e.
Mount / C:\apache2triad\ftp
Mount / C:\apache2triad\ftp\

[Tyrant_Dictator]

Well crud...

Now that I've been playing with it more and more I've noticed something. Eachtime I try to connect using a FTP client, since it's set to active the client picks random ports for the DATA connection. It makes the COMMAND (Port 21) connection, but it stalls out at DATA (Port ?)connection. I think it's work for me out of pure luck before, but now I can see more of a port issue. Can anyone tell me what ports should be open on my firewall for this server to work in ACTIVE mode? Oh and by the way I did check the slashes and it does like them with the slash at the end, Thanks! (I check by logging in locally).

--Rick

[LiquidSnake]

from /apache2triad/ftp/slimftpd.conf

Code: # The BindPort directive specifies which TCP port should be used to listen for
# incoming connections. The standard FTP port is 21.
#
BindPort 21

#
# The CommandTimeout directive specifies how many seconds to wait for a
# connected client to issue a command before dropping the connection. The
# default is 300 (5 minutes).
#
CommandTimeout 300

#
# The ConnectTimeout directive specifies how many seconds to wait for a data
# socket to connect with a client. This value applies to both active- and
# passive-mode connections. The default is 15.
#
ConnectTimeout 15

SlimFtp uses port 21, for all connections ... However some ftp's use both 20 and 21 ...

You may be able to change your ConnectTimeout to a higher time, since that seems to control data sockets. SlimFtp work's flawless out of the box. You may have a winsock problem ... Also, if you use a virus/firewall combo you may want to keep an eye on it, SlimFtp causes some bells and whistles to go off on some virus scanners and it may shut it down, or close the port mistakenly. Read this

I'm not saying this is the case, but a possibility.

[looka]

hey guys!

i found this at brief google search:

http://slacksite.com/other/ftp.html

so, that is the difference and some answers why use that sftp on passive mode.

but it is true, that i did not encounter this error, until i used port 31 to bind (for some stupid purposes...)