Wednesday, May 27, 2009

Problem of copying big file within a VM from the host

Have you ever experienced the following error?

Cannot copy <file_name>: The specified network name is no longer available.

Regardless of which Microsoft Windows, this problem occurs whenever you use Bridged mode on VMware network. Everything works fine with Host-only or NAT.

On VMware Server 1, I can disable the automatic bridging and then reconfigure other virtual adapter (not vmnet1 or vmnet8) as Bridged network by binding it to a physical adapter. This problem will go away. But this technique doesn't work for VMware Server 2. Thus, the problem still remains unresolved. What I can do is to copy files within the host to the VM, instead of inside the VM and do copying.

I don't believe that this post is correct. VMnet1 is Host-only. Indeed, I am not sure how we can change the nature of vmnet1 and vmnet8 to Bridged. Since the author of that post was using Host-only on vmnet1, certainly copying big file problem would not be an issue.

The other thing I would like to mention is that any newly added virtual adapter is always Host-only if the VMware Server is running on Windows. I am not sure if it holds true for other platforms.

1 comment:

  1. This blog is very interesting for me and others, I will return very soon for other items, thank you very much!

    Ant treatment Vancouver