My event log is full of VPCNetS2 informational events 12, 6, 5, 10, 10, and
13. It looks like something is disabling and re-enabling packet reception
every 31 to 32 seconds. Is this normal? If so, how do I supress these
messages? (It fills up the log and makes it harder to find other events.)

Configuration: Dell PowerEdge 2950 server running Virtual Server 2005 R2
SP1 (1.1.603.0 EE R2 SP1) on Windows Server 2003 R2 Enterprise with SP2. Two
physical NICs and two Microsoft Loopback Adapters (one for host-only
communication between the VMs and host and one set up for NAT between the VMs
and the rest of the network using Routing and Remote Access).

Did you get an answer to this. Identical issue. Losing network connectivity
at odd times on guest. When I log in it comes back up. HP NIC. Same errors
after starting virtual back up from save state.

"Victor S." wrote:

> My event log is full of VPCNetS2 informational events 12, 6, 5, 10, 10, and
> 13. It looks like something is disabling and re-enabling packet reception
> every 31 to 32 seconds. Is this normal? If so, how do I supress these
> messages? (It fills up the log and makes it harder to find other events.)
>
> Configuration: Dell PowerEdge 2950 server running Virtual Server 2005 R2
> SP1 (1.1.603.0 EE R2 SP1) on Windows Server 2003 R2 Enterprise with SP2. Two
> physical NICs and two Microsoft Loopback Adapters (one for host-only
> communication between the VMs and host and one set up for NAT between the VMs
> and the rest of the network using Routing and Remote Access).

No, I never did get an answer.

As to your issue, I have seen intermittent network connectivity like that
when there are two NICs (network cards) on a server that are teamed. Virtual
Server seems to have a problem when using the team for a guest. If you do
have teamed NICs, bind one of the individual NICs to the guest instead of the
team. (Note, it doesn't matter if the individual NICs have TCP/IP active on
them. They just need Virtual Machine Network Services bound to them.)
I've also seen certain network and teaming drivers cause this issue.
Usually, updating to the latest version helps but I had to go back to an
older version once.