Not really possible in the way you want.
Once the connection is interrupted and the transfer interrupted, re-establishing
the connection is not going to uncorrupt (if there is such a verb !) your files.
The flaw in the setup you have is in the transfer mechanism which is not resilient
enough to what it is having to cope with. You need the equivalent of a download manager,
but its the applications which are driving the transfer which you need to be changing.
That of course may be impossible.
But the underlying issue is really one of the design of your application architecture.
For instance why not have the program write to a local drive and then use a separate
process to copy to your network drive - then you can re-copy if the oringianl copy
process fails through interruption ?
