Then maybe you want to send them by mail? Or use rsync to copy the files over when the connection has been restored?

I think it will be far more efficient if you describe to us the exact setup and network environment, so that we don't have to guess at a good solution multiple times. Maybe you can also tell us the exact problem you're trying to solve. Having a view of the big picture often helps in understanding the implied constraints.

I have windows machine in a domain. Now I need to run a perl executable on x machines in the domain. Okay?

Now there is this one main server which throws the perl executable to thses x machines . This perl exe generates a output file which keeps on modifying. The reult files needs to be pulled by server from x machines and then they are compiled at server for final result. Server needs to pull these result files after every y minutes. Can i do that?

What i do now is that i create a share on server and the writing the result files to it as Corion already suggested. But then i lose connection and it creates a problem. So Now I want to create reult files on x machines and then want server to pull them after y min.How to do it?

I would consider one of <trike>three four approaches:

1. On each client: Use rsync to upload the file from the client, possibly retrying every five minutes. Rsync can resume transfers that broke instead of starting fresh every time.
2. On the server: Use rsync to download the files from the clients on the server, possibly retrying every five minutes. Rsync can resume transfers that broke instead of starting fresh every time.
3. On the server: Use File::Copy on the server to copy the file from the client using an Admin Share (\\machine\C$\)
4. Push a second Perl executable to the clients that uploads the files. If the client has no network connection, it won't receive the "upload now" command.

One way that works on Windows without re-entering the password is to use Windows Explorer to open a window on it. Just

system("start E:");
[download]

Of course, after a while, you'll end up with a bunch of windows (or 1, at best) that you don't need. Oh, well. :)