Server - set up - time out recommendations

[ekimr]

Hi

We are looking at setting up a single remote server where our in house application software (delivered to customers and living on customers PC;s around the UK) would log in, be authenticated, then deliver small files to the server.

Woud the server control the time out period and close the connection if the remote machine didn't come back to it in a set time...

OR should the software control the time out period - where if it detected the communcation with the server had stopped - then it would close the connection ..

Also - Are there disadvantages of just having long time out settings to allow for slow connections..

Thanks

Mike

 

[thedaver]

using what applications or protocols?

D.E.R. Management - IT Project Management Consulting

http://www.dermanagement.com/

 

[ekimr]

woops - sorry!

FTP

 

[thedaver]

Typically FTP servers have an inactivity timeout as part of their operation. Thus, if the client sits idle for long enough, the server (silently?) aborts the connection and readies itself to answer more queries.

This may be as opposed to something like a "total time per session" timeout, which is kind of implied in your note. Don't know if specific FTP servers support such things.

I would NOT attempt to enforce any behaviors through the client ends.

Check into VSFTPD, it's a highly secure and highly CONFIGURABLE ftp server. Not really super simple, but may give you the controls you're looking for.

D.E.R. Management - IT Project Management Consulting

http://www.dermanagement.com/