Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Something like

cp \\target_machine local_file.txt c:\dest_file.txt
share|improve this question
up vote 6 down vote accepted

Assuming you have appropriate permissions, you can do it like this:

copy local_file.txt \\target_machine\c$\dest_file.txt

Use "c$" to reference C drive on the remote machine.

share|improve this answer

It's like this:

copy c:\local_path\local_file.txt \\target_machine\destination_path\destination_file.txt

If you have \\target_machine\destination_path\ mapped to a network drive, say, Z: then the command becomes

copy c:\local_path\local_file.txt Z:\destination_file.txt

share|improve this answer
when I try the first option (without the c$ stuff) I get "The system cannot find the path specified" or "The network name cannot be found", depending on one or two backslashes before machine name. – Ash Oct 8 '10 at 5:15
Hmm, there was an error in Markdownformatting which showed only single backslash instead of 2. If you're getting The network name cannot be found then it's a network problem, either you don't have permissions or the firewall is blocking your requests – Sathya Oct 8 '10 at 12:23
I tried both one and two backslashes, and got the different error messages depending on which I used. "Network name cannot be found" was with two backslashes. Interesting. That works with your network setup? It didn't work with either our server or other clients... – Ash Oct 8 '10 at 13:45
@Ash single backslash indicates you are accessing the current drive, hence you got the system cannot find path specified error. Double backslash is used for accessing network shares with UNC naming scheme. Yes, this works on my network, I have couple of scripts where I make use of this ( scripts are to export data, compress them and move them to NAS). I suspect permissions problems. Are the machines you want to copy on different domains/workgroups ? – Sathya Oct 8 '10 at 13:59
On Windows machines/networks, a share such as c$ must be used. – Timtech Mar 27 '15 at 0:24

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .