in reply to NET::FTP trouble with SEQ?

If you are talking about the packet sequence numbers being off, this is most likely a hardware or tcp/ip stack problem, unrelated to any application.

I have seen this quite a bit while supporting routers at my last gig at an e-commerce company. A handful of customers would have packet sequence numbers jump, and we would miss a block of data that was the window size of the last good packet.

If you believe Net::Ftp may have something to do with it, try using the Windows FTP client do do the comm. You could even call it from Perl with something like:

`ftp -s scriptfile.txt`;

scriptfile.txt would contain the open command, the username, password, and everything you would type to the ftp client if you were running it interactively. One command per line, just like a batch file.

But, were I a gambling man, I'd bet money it ends up being hardware.

Replies are listed 'Best First'.
Re: Re: NET::FTP trouble with SEQ?
by choeppner (Pilgrim) on Oct 30, 2003 at 14:00 UTC
    Well, I am leaning toward this being a hardware/router problem, but I just wanted to ask.

    We will put network sniffers at both ends and wait for it to happen again. Then its down into the details of TCP traffic for lots of fun.

    Thanks for the response.