Archived Forum Post

Index of archived forum posts

Question:

ftp error: Timeout waiting to read socket or accept connection

May 20 '13 at 16:40

Hi there, I'm using chillkat ftp to transfer files between 2 production servers and quite often at last error catch (if !Success) I'm getting this error: Timeout waiting to read socket or accept connection I browsed all the previous answers to similar problems other people had and they don't help. e.g. I set ftp.SendBufferSize = 4096; and it makes no difference. The files I'm getting the error on are not large at all. e.g . this last file is only 136 KB.

Here is my full Last error:

ChilkatLog:
PutFile:
DllDate: Dec 22 2010
UnlockPrefix: MICROFFTP
Username: SYSTEM
Component: .NET 2.0
LocalFilename: C:inetpubwwwrootSupportline_tempincidentfiles2645941Server-newException-0000-16-2013-05-10-14-20-25.dmp
RemoteFilename: Server-newException-0000-16-2013-05-10-14-20-25.dmp
IdleTimeoutMs: 60000
ReceiveTimeoutMs: 60000
ConnectTimeoutSeconds: 60
localFileSize: 135073
initialGreeting: 220 nwb-support.microfocus.com
restartNext: 0
ModeZ: 0
BinaryMode: 1
Passive transfer mode
hostAddr: 199.250.120.230
DataConnect:
hostname: 199.250.120.230
port: 21
ConnectTimeoutMs: 60000
calling ConnectSocket2
This is an IPV4 numeric address...
Connect using IPV4.
ipAddress: 199.250.120.230
socketHandle: 0x2270
ai_addrlen: 16
ai_addr: 0200 0015 C7FA 78E6 0000 0000 0000 0000 
myIP_3: 199.250.120.192
myPort_3: 1563
connect successful.
SetupPassiveDataSocket: Elapsed time: 0 millisec
command: STOR 
PutFilename: [Server-newException-0000-16-2013-05-10-14-20-25.dmp]
DataConnectionReady: Elapsed time: 0 millisec
Timeout waiting to read socket or accept connection
timeoutMs: 60000
Failed to read FTP response line..
Failed to read STOR reply
Filename: Server-newException-0000-16-2013-05-10-14-20-25.dmp
TotalTime: Elapsed time: 60016 millisec
Failed.

Any help would be appreciated.


Answer

See http://www.cknotes.com/?p=282


Answer

check with your network admin if port 21 is being blocked. i had the same issue with port 22 and sure ebough it was blocked. after unblocking it connected every time.