Slow copy from Host to VM

You could be having an issue just between the the Host and guests, with something called TOE!

Don't know if it applies to Windows 2008, but it does to Windows 2003!

--------------

Iremember having this problem on two Windows 2003 SP2 machines that wewere running VMWare server one or two years back. It's got to do withTCP segmentation offload (TOE). Normally happens with broadcom Nics.Apparently this issue came about when SP2 was introduced when MSchanged a few settings.  I've done this search and think you need tothis on your host to solve your problem.

In fact, this post from me on the VTMN solution should work for you too!

http://communities.vmware.com/message/867573#867573

Work through the entire post.

You need to disable,  "Offload TCP_LargeSend" on the network card itself, disable chimney settings

and then what I listed here,

-----------------

Disablingall TCP Offload settings on my Broadcom NIC in an HP DL 360 allowed theVM Guest and VMware Host (2003 R2 SP2) to finally communicate.
I also ran disabled the Chimney settings

However,copying large files (over 2Mb) from the Host to the guest from withinthe Guest would cause the error "The specified network name is nolonger available"

The only thing that solved that problem was to disable the Denial of Service Attack option on the LanManServer settings:
Disable Denial-Of-Service attack detection

Click Start, click Run, type regedit in the Open box, and then click OK.
Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanManServer\Parameters
On the Edit menu, point to New, and then click DWORD Value.
Type DisableDos for the name of the DWORD value, and then press ENTER.
Right-click DisableDos, and then click Modify.
In the Value data box, type 1 to disable denial of service attack detection, and then click OK.

This problem is definitely irritating if you have a Windows 2003 R2 Host Server, with TOE!  

------------------
You could be having an issue just between the the Host and guests.
I remember having this problem on two Windows 2003 SP2 machines that we were running VMWare server one or two years back. It's got to do with TCP segmentation offload (TOE). Normally happens with broadcom Nics. Apparently this issue came about when SP2 was introduced when MS changed a few settings.  I've done this search and think you need to this on your host to solve your problem.
In fact, this post from me on the VTMN solution should work for you too!
http://communities.vmware.com/message/867573#867573
Work through the entire post.
You need to disable,  "Offload TCP_LargeSend" on the network card itself, disable chimney settings
and then what I listed here,
-----------------
Disabling all TCP Offload settings on my Broadcom NIC in an HP DL 360 allowed the VM Guest and VMware Host (2003 R2 SP2) to finally communicate.
I also ran disabled the Chimney settings

However, copying large files (over 2Mb) from the Host to the guest from within the Guest would cause the error "The specified network name is no longer available"

The only thing that solved that problem was to disable the Denial of Service Attack option on the LanManServer settings:
Disable Denial-Of-Service attack detection

Click Start, click Run, type regedit in the Open box, and then click OK.
Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanManServer\Parameters
On the Edit menu, point to New, and then click DWORD Value.
Type DisableDos for the name of the DWORD value, and then press ENTER.
Right-click DisableDos, and then click Modify.
In the Value data box, type 1 to disable denial of service attack detection, and then click OK.

This problem is definitely irritating if you have a Windows 2003 R2 Host Server, with TOE!  
------------------