Stream close System.IO.IOException

[support2]

It certainly looks like a server timeout. The other possibility is a firewall timeout - the firewall then kills the connection.

So is there any way to handle a problem like this? Do you have any example code that deals with this kind of situation? Would using the FTPconnectionClosedException class be the way to handle this problem?

I would guess that if this problem occurs, the software should be able to detect it and then reconnect and resume sending the file. Does that sound like the right way to proceed? If so, is there example code that demonstrates this?

Again, any help and especially example code, would be appreciated.

[support2]

Query1
Why is it that you call the .UploadStream() after the .ResumeTransfer()?
Isn't it not needed?

Query2
Is this still necessary if all of the bytes have been transferred?
My code seems to fail despite every byte having been uploaded already. (Mind you, it gives a EnterpriseDT.Net.Ftp.ControlChannelIOException)

Nevermind about Query 1 - I just looked at the docs again and noticed the "Makes the NEXT transfer" bit.

Nevermind about Query 2 - I found your other post that answers it.