I have a WIN2K3 Server SP2 Dell server with 4 gigs of ram and dual core 2 duo
processors running Virtual Server 2005 SP1. I just loaded Cirtual Server
this week. I downloaded the WIN2K3 Server SP1 VM from Microsoft.

I have the the VM configured to use the 2nd NIC on the server which is
connected to our LAN. As soon as I start the VM the Physical Server can no
longer communicate over that NIC. It still shows a connection but I can not
ping anything on the LAN. The VM server, however, works great and can Ping
anything on the LAN. As soon as I shutdown the VM Server, the Physical
Server can communicate on the LAN.

So only one OS can use the nic at a time. It has to be something simple I
am missing. What ever it is, after 4 days, I am at a loss. Any would
be appreciated.

TKS

Found the issue. I thought asll the drivers were up-to-date on that server.
However, after reading another post here I decided to double check on the NIC
driver. There was a new one on the Dell site. Loaded it without need for a
reboot and then my VMs started working correctly.

So if all else fails, check your drivers one more time.



"JohnnyF" wrote:

> I have a WIN2K3 Server SP2 Dell server with 4 gigs of ram and dual core 2 duo
> processors running Virtual Server 2005 SP1. I just loaded Cirtual Server
> this week. I downloaded the WIN2K3 Server SP1 VM from Microsoft.
>
> I have the the VM configured to use the 2nd NIC on the server which is
> connected to our LAN. As soon as I start the VM the Physical Server can no
> longer communicate over that NIC. It still shows a connection but I can not
> ping anything on the LAN. The VM server, however, works great and can Ping
> anything on the LAN. As soon as I shutdown the VM Server, the Physical
> Server can communicate on the LAN.
>
> So only one OS can use the nic at a time. It has to be something simple I
> am missing. What ever it is, after 4 days, I am at a loss. Any would
> be appreciated.
>
> TKS
>
>

Glad you got it sorted out. Problems like that are almost always due to
the driver in the host OS. The driver in the host and the Virtual Machine
Network Services have to work smoothly with each other for virtual
networking to be successful.

"JohnnyF" <JohnnyF@discussions.microsoft.com> wrote in message
news:CEAC01FF-B603-4EBD-8DEE-1C28B98AA3FF@microsoft.com...
> Found the issue. I thought asll the drivers were up-to-date on that
> server.
> However, after reading another post here I decided to double check on the
> NIC
> driver. There was a new one on the Dell site. Loaded it without need for
> a
> reboot and then my VMs started working correctly.
>
> So if all else fails, check your drivers one more time.
>
>
>
> "JohnnyF" wrote:
>
>> I have a WIN2K3 Server SP2 Dell server with 4 gigs of ram and dual core 2
>> duo
>> processors running Virtual Server 2005 SP1. I just loaded Cirtual Server
>> this week. I downloaded the WIN2K3 Server SP1 VM from Microsoft.
>>
>> I have the the VM configured to use the 2nd NIC on the server which is
>> connected to our LAN. As soon as I start the VM the Physical Server can
>> no
>> longer communicate over that NIC. It still shows a connection but I can
>> not
>> ping anything on the LAN. The VM server, however, works great and can
>> Ping
>> anything on the LAN. As soon as I shutdown the VM Server, the Physical
>> Server can communicate on the LAN.
>>
>> So only one OS can use the nic at a time. It has to be something simple
>> I
>> am missing. What ever it is, after 4 days, I am at a loss. Any
>> would
>> be appreciated.
>>
>> TKS
>>
>>