Closing control connection

Advertisement

therapiekind
Joined:
Posts:
3

Closing control connection

Hello there,

I get this error regularly with (I think) all of my FTP connections:
No transfer timeout (300 seconds): closing control connection
Filezilla seems to handle this correctly, it doesn't happen there. And one strange thing is, when transferring large files, the error pops up in the middle of the upload, and when pressing "Connect" in the error dialogue it seems like the upload has been kept up in spite of the error (read, I don't have to press "Connect" everytime to keep the upload going, I just do it every now and then to see where progress currently is).

An interesting forum post might be at the PSPad forums: <invalid link removed by admin>

Btw, greatest software on earth. It outrivals everything I've ever seen and tried!

Reply with quote

Advertisement

martin
Site Admin
martin avatar
Joined:
Posts:
40,476
Location:
Prague, Czechia

Re: Closing control connection

What FTP server are you using?

And one strange thing is, when transferring large files, the error pops up in the middle of the upload, and when pressing "Connect" in the error dialogue it seems like the upload has been kept up in spite of the error (read, I don't have to press "Connect" everytime to keep the upload going, I just do it every now and then to see where progress currently is).
Do you use foreground or background transfers?

Reply with quote

therapiekind
Joined:
Posts:
3

Hello, thanks for the reply.

What do you mean by "what FTP server"? Maybe a connection log might answer this:
--------------------------------------------------------------------------
WinSCP Version 4.0.7 (Build 370) (OS 6.0.6000)
Login time: Montag, 17. Marz 2008 18:50:19
--------------------------------------------------------------------------
Session name: user@ftpserver.com
Host name: ftpserver.com (Port: 21)
User name: user (Password: Yes, Key file: No)
Tunnel: No
Transfer Protocol: FTP
Ping type: C, Ping interval: 15 sec; Timeout: 15 sec
Proxy: none
FTP: Passive: Yes
Local directory: default, Remote directory: home, Update: No, Cache: Yes
Cache directory changes: Yes, Permanent: Yes
DST mode: 1
--------------------------------------------------------------------------
Verbinde mit ftpserver.com ...
Verbunden mit ftpserver.com. erwarte Willkommensnachricht ...
220 FTP on xxx.xxxxxxxxxx.com ready
USER user
331 Password required for user
PASS ********************
230 User user logged in
SYST
215 UNIX Type: L8
FEAT
211-Features:
 MDTM
 AUTH TLS
 PBSZ
 PROT
 REST STREAM
 SIZE
211 End
Verbunden
--------------------------------------------------------------------------
Using FTP protocol.
Doing startup conversation with host.
PWD
257 "/" is the current directory
Getting current directory name.
Rufe Verzeichnisinhalt ab...
TYPE A
200 Type set to A
PASV
227 Entering Passive Mode (85,13,138,18,195,86).
LIST -a
150 Opening ASCII mode data connection for file list
226 Transfer complete
Verzeichnisinhalt erfolgreich abgerufen
Startup conversation with host finished.
And I'm using background transfers by default, yes.

Reply with quote

martin
Site Admin
martin avatar
Joined:
Posts:
40,476
Location:
Prague, Czechia

therapiekind wrote:

What do you mean by "what FTP server"?
I've meant what software does the FTP server use. I guess you do not know.

And I'm using background transfers by default, yes.
WinSCP uses separate connection for background transfers. Hence even when the primary (foreground) connection is terminated, the background transfers are not stopped.

Anyway the next version will include improved keepalive mechanism.

Reply with quote

therapiekind

Yay!

Just wanted to note, that version 4.1.0 and an increased server response timeout of 30 seconds (I think it's 15 seconds by default) fixed the problem.

Thanks for that! :)
_________________
I'm afraid Mary is dead.

Reply with quote

Advertisement

You can post new topics in this forum