Ftp Connection Time

[runninghorse]

I do alot of testing and uploading (because I'm running programs in the cgi-bin and can't test them locally) and was wondering if it's possible to reset the time limit on my FTP program so it doesn't close after 300 seconds or something. I'd like to have a little more time, 600 sec? 900 sec? What's the protocol for something like this?

 

Thanks!

[natimage]

I use a free version of Ipswitch WS-FTP, and it looks like I could change the time up to 120 seconds...

 

...so I would think your FTP program might have a setting you could change. Not sure. I haven't worked with much besides WS-FTP. Probably ought to, though...

[runninghorse]

I use the full version of WS-FTP. I was told at one point (don't know if it was correct or not) that the timeout settings were only changable on the server end.... Where do you find the setting to change in your program (Im sure ours are very similar).

[runninghorse]

From WS_FTP's Help:

 

Network Timeout

 

This is the number of seconds before WS_FTP Pro times out waiting for an FTP site to respond to a command.

Note that the initial timeout is determined by your Winsock DLL. Setting this value higher does not have any effect on the initial connection to the FTP site. Setting to less than the amount of time that your Winsock DLL uses causes the connection to fail in that amount of seconds.

[natimage]

yea...that's what I was looking at. Guess that's not the ticket, huh?? Sorry 'bout that!

[TCH-Bruce]

When you log into the ftp server from a command line it states that the connection will remain active unless there is 15 minutes of inactivity.

 

Open a support ticket if this isn't so and have then check for you.

[natimage]

Mine has definately never remained active for 15 minutes using WS-FTP. Seems like I do get a longer connection most times using Dreamweaver.

[fromsitepoint]

I'm having the same problem with ws_ftp, disconnecting after 300 seconds...but only with certain hosts. Don't know why. Settings all seem the same.

[jandafields]

I've never gotten near 15 minutes. 300 seconds is about what I'm getting, and it is not my ftp program. It is set to try and "keep the session alive" by sending random commands like ls and pwd. But, I still get disconnected because "no file transfer in 300 seconds"

[TCH-Bruce]

If you aren't transferring files then why stay connected? You are using a shared server which has limited FTP sessions. The reason for the timeouts is if everyone sat there with the ftp program logged in and then someone else came along to ftp something they would get a too many connections message and to try again later.

 

I'm sure you wouldn't want to be the one that received the message.

[jandafields]

I'm not saying I want to leave my ftp client connected all the time. Besides, I'm on dial up most of the time. When I leave my desk, I disconnect the Internet. I'm not trying to use up more of my share or be unfair.

 

By the way, what is the ftp user limit on the shared reseller servers before you get a "too many connections" message?

[TCH-Bruce]

I'm not saying I want to leave my ftp client connected all the time. Besides, I'm on dial up most of the time. When I leave my desk, I disconnect the Internet. I'm not trying to use up more of my share or be unfair.

My post wasn't directed at anyone in particular. I was just trying to let everyone know why the server disconnects you.

 

By the way, what is the ftp user limit on the shared reseller servers before you get a "too many connections" message?

 

I'm not certain but will look into it for you.

[TCH-Bruce]

To answer the question of limits on the number of connections it is 50 on all of the shared servers.

[jandafields]

Thanks Bruce!