Can't login to FTP

hehe sure its a server side problem afterall it happens when a server is running win xp :bleh: btw tht 24 online has some serious issues with "kerio firewall" and a bunch of progs i designed tht whole network in my town just be careful while choosing firewalls and stuffs.
 
QF, in the same vein, take a snapshot of cuteftp's and firewall settings, would come in handy for future refrence :)

Dont think anything is changing the setting, must be the ISP then, maybe they are blocking the incoming stream from the FTP ports.

Next time lets not reset anything wait for about 24hrs and check it it works, if it works then its the ISP ;)

FTP is a TCP based service exclusively. There is no UDP component to FTP. FTP is an unusual service in that it utilizes two ports, a 'data' port and a 'command' port (also known as the control port). Traditionally these are port 21 for the command port and port 20 for the data port. The confusion begins however, when we find that depending on the mode, the data port is not always on port 20.

Summary :

The following chart should help admins remember how each FTP mode works:

Active FTP :

command : client >1023 -> server 21

data : client >1023 <- server 20

Passive FTP :

command : client >1023 -> server 21

data : client >1023 -> server >1023

A quick summary of the pros and cons of active vs. passive FTP is also in order:

Active FTP is beneficial to the FTP server admin, but detrimental to the client side admin. The FTP server attempts to make connections to random high ports on the client, which would almost certainly be blocked by a firewall on the client side. Passive FTP is beneficial to the client, but detrimental to the FTP server admin. The client will make both connections to the server, but one of them will be to a random high port, which would almost certainly be blocked by a firewall on the server side.

Luckily, there is somewhat of a compromise. Since admins running FTP servers will need to make their servers accessible to the greatest number of clients, they will almost certainly need to support passive FTP. The exposure of high level ports on the server can be minimized by specifying a limited port range for the FTP server to use. Thus, everything except for this range of ports can be firewalled on the server side. While this doesn't eliminate all risk to the server, it decreases it tremendously

Check this site for more on FTP : http://slacksite.com/other/ftp.html
Click to expand...
 
@dipdude: I keep the default settings for Windows Firewall most of the times. Its very unlikely the prob is from there. I haven't changed any CuteFTP settings since the FTP was not working from any other client. So its not a CuteFTP related problem acc. to me.

@deejay: no..everything remains normal.
 
Last edited by a moderator:
Back
Top