Attachment did not work so here it is: (ahh, can't stop thunderbird wrapping - sorry)

No.     Time            Source          Destination     Protocol                
Length  Info
190     10.344855       192.168.1.31    65.212.180.79   FTP     72      
Request: PASV
191 10.524256 65.212.180.79 192.168.1.31 FTP 117 Response: 227 Entering Passive Mode (65,212,180,79,214,237) 192 10.524302 192.168.1.31 65.212.180.79 TCP 66 54818 > ftp [ACK] Seq=494 Ack=1663 Win=66668 Len=0 TSval=443118091 TSecr=384651593 193 10.525193 192.168.1.31 65.212.180.79 TCP 78 54831 > 55021 [SYN] Seq=0 Win=65535 Len=0 MSS=1460 WS=2 TSval=443118091 TSecr=0 SACK_PERM=1 194 10.701375 65.212.180.79 192.168.1.31 TCP 74 55021 > 54831 [SYN, ACK] Seq=0 Ack=1 Win=5792 Len=0 MSS=1402 SACK_PERM=1 TSval=384651774 TSecr=443118091 WS=64 195 10.701407 192.168.1.31 65.212.180.79 TCP 66 54831 > 55021 [ACK] Seq=1 Ack=1 Win=66720 Len=0 TSval=443118267 TSecr=384651774 196 10.702119 192.168.1.31 65.212.180.79 FTP 105 Request: STOR 18012012_1014160_leeEcersley.csv 197 10.880935 65.212.180.79 192.168.1.31 FTP 143 Response: 150 Opening ASCII mode data connection for 18012012_1014160_leeEcersley.csv 198 10.880970 192.168.1.31 65.212.180.79 TCP 66 54818 > ftp [ACK] Seq=533 Ack=1740 Win=66642 Len=0 TSval=443118445 TSecr=384651954
199     10.881595       192.168.1.31    65.212.180.79   FTP-DATA        157     
FTP Data: 91 bytes
200 10.881754 192.168.1.31 65.212.180.79 TCP 66 54831 > 55021 [FIN, ACK] Seq=92 Ack=1 Win=66720 Len=0 TSval=443118445 TSecr=384651774 201 11.062593 65.212.180.79 192.168.1.31 TCP 66 55021 > 54831 [ACK] Seq=1 Ack=92 Win=5824 Len=0 TSval=384652133 TSecr=443118445 202 11.062625 192.168.1.31 65.212.180.79 TCP 66 54831 > 55021 [FIN, ACK] Seq=92 Ack=1 Win=66720 Len=0 TSval=443118625 TSecr=384652133 203 11.063438 65.212.180.79 192.168.1.31 TCP 66 55021 > 54831 [FIN, ACK] Seq=1 Ack=93 Win=5824 Len=0 TSval=384652136 TSecr=443118445 204 11.063465 192.168.1.31 65.212.180.79 TCP 66 54831 > 55021 [ACK] Seq=93 Ack=2 Win=66720 Len=0 TSval=443118625 TSecr=384652136 205 11.064379 65.212.180.79 192.168.1.31 FTP 89 Response: 226 Transfer complete 206 11.064404 192.168.1.31 65.212.180.79 TCP 66 54818 > ftp [ACK] Seq=533 Ack=1763 Win=66696 Len=0 TSval=443118626 TSecr=384652137
207     11.142144       192.168.1.31    65.212.180.79   FTP     72      
Request: PASV
208 11.316388 65.212.180.79 192.168.1.31 FTP 115 Response: 227 Entering Passive Mode (65,212,180,79,202,2) 209 11.316422 192.168.1.31 65.212.180.79 TCP 66 54818 > ftp [ACK] Seq=539 Ack=1812 Win=66670 Len=0 TSval=443118878 TSecr=384652389 210 12.820295 192.168.1.31 65.212.180.79 TCP 78 54832 > 51714 [SYN] Seq=0 Win=65535 Len=0 MSS=1460 WS=2 TSval=443120374 TSecr=0 SACK_PERM=1 211 13.010071 65.212.180.79 192.168.1.31 TCP 74 51714 > 54832 [SYN, ACK] Seq=0 Ack=1 Win=5792 Len=0 MSS=1402 SACK_PERM=1 TSval=384654080 TSecr=443120374 WS=64 212 13.010112 192.168.1.31 65.212.180.79 TCP 66 54832 > 51714 [ACK] Seq=1 Ack=1 Win=66720 Len=0 TSval=443120563 TSecr=384654080 213 13.010847 192.168.1.31 65.212.180.79 FTP 105 Request: STOR 18012012_1014360_leeEcersley.csv 214 13.191201 65.212.180.79 192.168.1.31 FTP 143 Response: 150 Opening ASCII mode data connection for 18012012_1014360_leeEcersley.csv 215 13.191241 192.168.1.31 65.212.180.79 TCP 66 54818 > ftp [ACK] Seq=578 Ack=1889 Win=66642 Len=0 TSval=443120743 TSecr=384654264

On 01/02/2012 15:00, Info2004 wrote:
Hi,

Some additional information after hooking up wireshark.

I have attached a csv of the capture.

What it shows me is that I get the 150 from the server, I then send an
ACK, but I don't send the FTP-DATA.

Then of course, I don't see the request done event, because I have not
sent the data.

For the ACK to go out after the 150 response I am assuming that the ftp
client has seen the response, and sent the ack. Or am I mistaken? Is
this a lower level interaction? (in winsock somewhere)

Why would I not send the data - is my question really?

I don't have any Application.ProcessMessages loops in my application -
apart from a start up splash screen, and an application shut down loop
waiting for a thread to close down. Neither are active when my ftp stalls.

The thread I create has nothing (intentionally) to do with the ftp
client. It monitors a usb serial port, downloads serial data and creates
files on the file system. This thread is not downloading serial data and
creating files, as there is no device connected.

I do now detect the stall with a timer, but don't currently restart -
just display a message so that the user can retry.

I am logging all RequestDone events, and nothing is reported when I
stall. I have attached the csv that shows the last good transfer, then
the stall. If an alternative format is preferred, just ask.

Ideas?

Thanks,

Andy
On 31/01/2012 15:43, Info2004 wrote:
Hi,

I have been using the ftp client component for a couple of years now
without a hitch. Until recently. The version is 7.09.

I have in the main thread a timer that runs a state machine to control
logging in and sending of the files. But recently, the state machine
stalls and times out. I have logged the debug from the component, and
you can see two successful sends, and the last one fails.

In the failed send, the STOR is issued, but the 150 Opening ASCII ...
does not happen. This is as a result of calling PutAsync on the
component.

Now before I dust off wireshark, does anybody know what could cause the
150 after the STOR command?




--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be

--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be

Reply via email to