Re: Workstation 9.0.0 Bridged Networking problem

happyuserbg · ‎09-09-2012

Hello,

I have upgraded VMware Workstation to 9.0.0 and now I am having problems with the Bridged Networking when I copy big files between the host and the guest using Windows File Sharing.
Soon after I start the copy operation I lose connectivity to all other hosts except the Virtual Machine. After the copying is complete it needs some time to recover before the connectivity is restored.

Here is what happens when I copy a 426 MB file from the host to the guest.

Pinging my router:

C:\>ping -t 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=341ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3750ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.1.1:
Packets: Sent = 20, Received = 13, Lost = 7 (35% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 3750ms, Average = 314ms

Pinging the IP of the VM:

C:\>ping -t 192.168.1.116

Pinging 192.168.1.116 with 32 bytes of data:
Reply from 192.168.1.116: bytes=32 time<1ms TTL=128
Reply from 192.168.1.116: bytes=32 time<1ms TTL=128
Reply from 192.168.1.116: bytes=32 time<1ms TTL=128
Reply from 192.168.1.116: bytes=32 time<1ms TTL=128
Reply from 192.168.1.116: bytes=32 time<1ms TTL=128
Reply from 192.168.1.116: bytes=32 time<1ms TTL=128
Reply from 192.168.1.116: bytes=32 time<1ms TTL=128
Reply from 192.168.1.116: bytes=32 time<1ms TTL=128
Reply from 192.168.1.116: bytes=32 time<1ms TTL=128
Reply from 192.168.1.116: bytes=32 time<1ms TTL=128
Reply from 192.168.1.116: bytes=32 time<1ms TTL=128
Reply from 192.168.1.116: bytes=32 time<1ms TTL=128
Reply from 192.168.1.116: bytes=32 time<1ms TTL=128
Reply from 192.168.1.116: bytes=32 time<1ms TTL=128
Reply from 192.168.1.116: bytes=32 time<1ms TTL=128
Reply from 192.168.1.116: bytes=32 time<1ms TTL=128
Reply from 192.168.1.116: bytes=32 time<1ms TTL=128
Reply from 192.168.1.116: bytes=32 time<1ms TTL=128
Reply from 192.168.1.116: bytes=32 time<1ms TTL=128
Reply from 192.168.1.116: bytes=32 time<1ms TTL=128
Reply from 192.168.1.116: bytes=32 time<1ms TTL=128
Reply from 192.168.1.116: bytes=32 time<1ms TTL=128
Reply from 192.168.1.116: bytes=32 time<1ms TTL=128
Reply from 192.168.1.116: bytes=32 time<1ms TTL=128
Reply from 192.168.1.116: bytes=32 time<1ms TTL=128
Reply from 192.168.1.116: bytes=32 time<1ms TTL=128
Reply from 192.168.1.116: bytes=32 time<1ms TTL=128
Reply from 192.168.1.116: bytes=32 time<1ms TTL=128
Reply from 192.168.1.116: bytes=32 time<1ms TTL=128
Reply from 192.168.1.116: bytes=32 time<1ms TTL=128
Reply from 192.168.1.116: bytes=32 time<1ms TTL=128
Reply from 192.168.1.116: bytes=32 time<1ms TTL=128
Reply from 192.168.1.116: bytes=32 time<1ms TTL=128
Reply from 192.168.1.116: bytes=32 time<1ms TTL=128
Reply from 192.168.1.116: bytes=32 time<1ms TTL=128
Reply from 192.168.1.116: bytes=32 time<1ms TTL=128
Reply from 192.168.1.116: bytes=32 time<1ms TTL=128
Reply from 192.168.1.116: bytes=32 time<1ms TTL=128
Reply from 192.168.1.116: bytes=32 time<1ms TTL=128
Reply from 192.168.1.116: bytes=32 time<1ms TTL=128
Reply from 192.168.1.116: bytes=32 time<1ms TTL=128
Reply from 192.168.1.116: bytes=32 time<1ms TTL=128
Reply from 192.168.1.116: bytes=32 time<1ms TTL=128
Reply from 192.168.1.116: bytes=32 time<1ms TTL=128
Reply from 192.168.1.116: bytes=32 time<1ms TTL=128
Reply from 192.168.1.116: bytes=32 time<1ms TTL=128
Reply from 192.168.1.116: bytes=32 time<1ms TTL=128
Reply from 192.168.1.116: bytes=32 time<1ms TTL=128
Reply from 192.168.1.116: bytes=32 time<1ms TTL=128
Reply from 192.168.1.116: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.116:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Both pings were running simultaneously.
The speed of the copying is around 50 MB/s.

I haven't had this problem with VMware Workstation 8.0.4.

My NIC is Realtek PCIe GBE Family Controller
The driver version is 7.46.610.2011 from 10.06.2011, installed via Windows Update.

Host OS: Windows 7 x64 SP1

CPU: Core 2 Duo E6400 2.13 GHz
Motherboard: ASUS P5B

RAM: 8 GB (DDR2-800)

Guest OS: Windows 7 x64 SP1

Guest RAM: 1.5 GB

There is nothing in the Event Log or vmware.log.

happyuserbg · ‎09-09-2012

Tested with Windows XP Guest and the problem still exists but there are some differences.

When I start to copy a large file in the Guest from a shared folder on the host the copying fails with this message:

Cannot copy (filename): The specified network name is no longer available.

This error appears in the Event Log of the host:

Log Name:      System
Source:        srv
Date:          09.09.2012 13:28:10
Event ID:      2021
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      ****
Description:
The server was unable to allocate a work item 3204 times in the last 60 seconds.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="srv" />
    <EventID Qualifiers="32768">2021</EventID>
    <Level>3</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2012-09-09T10:28:10.765548900Z" />
    <EventRecordID>122817</EventRecordID>
    <Channel>System</Channel>
    <Computer>****</Computer>
    <Security />
</System>
<EventData>
    <Data>\Device\LanmanServer</Data>
    <Data>3204</Data>
    <Data>60</Data>
    <Binary>000000000300280000000000E5070080000000009A0000C000000000000000000000000000000000</Binary>
</EventData>
</Event>

abirhasan · ‎09-09-2012

While copying the file the file path may be using maximum bandwidth that's way some ping lost. Please check the ping request weather drop or not when no data is sending..

admin · ‎09-09-2012

Hi happyuserbg,

Welcome to communites .

If you have additional NIC Please map that one to VM then check it .

If it start working then split your network wiht those NIC .

"Don't go through life, grow through life."

continuum · ‎09-10-2012

Map the share to a driveletter - then it will be more stable

________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

All

Workstation 9.0.0 Bridged Networking problem