Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

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

Let's say I copy a network folder(Machine A) contents to another(Machine B) and I do this copying operation on a different machine (Machine C). How does the traffic flow? Does the data flow from Machine A to Machine B directly? or does it go through Machine C?

Edit:- Seems like different protocols work differently. I'm interested in whatever protocol that works behind Windows Network copy

share|improve this question
This is protocol dependent. Can you clarify how you are copying the files? – lee Aug 31 '09 at 19:34
up vote 4 down vote accepted

With windows shares (cifs / smb ), like most protocols, all the trafic will go through the C computer. You can verify it with performance monitor.

share|improve this answer
...or see the traffic with Wireshark. Removes all doubt. – John Gardeniers Aug 31 '09 at 21:54

Depends on what you use. FTP can do do it so the traffic never goes through machine C, it is called FXP.

share|improve this answer
Most ftp servers won't let you do this anymore though, or prevent ftp bouncing. – Cian Sep 1 '09 at 2:04

Since you are operating at C, there is no other way then data to come from A to C then from C to B. So, you are wasting twice the network resources you need.

However, if you use Remote Desktop to login to B and pull data directly from A, you'll manage to go lot cheaper, since data will flow directly, and only other overhead will be remote console updates. Even more, use telnet and log into B to pull data from A via the command line.

Hope that clarifies it.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.