> Hello:
>
> I have created two Red Hat Enterprise 4 vms. Initally, they appear to behave
> fine. But, after working on them for several hours (either via incoming SSH or,
> on the VM, using web browsing), the connectivity just drops. After a period of
> time (from a few minutes to an hours or more), the connection comes back up. I
> have engaged Microsoft tech support on this without much success.
>
> Here are some of the symptoms: When the connection to VM drops,
> - pings from the client workstation to it also fail.
> - pings and VMRC access to the host machine still work.
> - pings to other VMs (including Linux VMs) sometimes still work. That is, you
> can run two separate ping -t sessions to different VMs on the same host and one
> will work and one will fail.
> - Sometimes pings from the host OS to the guest VM will work when the ping from
> the production network fails.
>
> The configuation is:
> - Host: Dell PowerEdge 1850 with four Intel PRO/1000 ports (two onboard; two in
> a dual PCI card) w/ 4GB RAM. One port goes to the production VLAN, one to the
> iSCSI array, and two are disabled.
> - Host OS: Windows Server 2003 R2
> - Virtualization Environment: Virtual Server 2005 R2 Enterprise
> - Guests: two instances of Red Hat Enterprise 4 (Linux); two instances of
> Windows Server 2003 Enterprise.
>
> Any help or suggestions would be very welcome. MS has been close to no help on
> this. I have had many good experiences with MS paid support, but not this one.
> Their staff appear to be shooting in the dark and do not really seem to
> understand virtualization or the VS product. I am very close to being forced to
> abandon the whole VS concept.
>
> Thanks.
>
> Nordic

>
>> Hello:
>>
>> I have created two Red Hat Enterprise 4 vms. Initally, they appear to behave
>> fine. But, after working on them for several hours (either via incoming SSH
>>or,
>> on the VM, using web browsing), the connectivity just drops. After a period
>>of
>> time (from a few minutes to an hours or more), the connection comes back up.
>>I
>> have engaged Microsoft tech support on this without much success.
>>
>> Here are some of the symptoms: When the connection to VM drops,
>> - pings from the client workstation to it also fail.
>> - pings and VMRC access to the host machine still work.
>> - pings to other VMs (including Linux VMs) sometimes still work. That is,
>>you
>> can run two separate ping -t sessions to different VMs on the same host and
>>one
>> will work and one will fail.
>> - Sometimes pings from the host OS to the guest VM will work when the ping
>>from
>> the production network fails.
>>
>> The configuation is:
>> - Host: Dell PowerEdge 1850 with four Intel PRO/1000 ports (two onboard; two
>>in
>> a dual PCI card) w/ 4GB RAM. One port goes to the production VLAN, one to
>>the
>> iSCSI array, and two are disabled.
>> - Host OS: Windows Server 2003 R2
>> - Virtualization Environment: Virtual Server 2005 R2 Enterprise
>> - Guests: two instances of Red Hat Enterprise 4 (Linux); two instances of
>> Windows Server 2003 Enterprise.
>>
>> Any help or suggestions would be very welcome. MS has been close to no help
>>on
>> this. I have had many good experiences with MS paid support, but not this
>>one.
>> Their staff appear to be shooting in the dark and do not really seem to
>> understand virtualization or the VS product. I am very close to being forced
>>to
>> abandon the whole VS concept.
>>
>> Thanks.
>>
>> Nordic
>
>See http://www.mcse.ms/archive235-2005-10-1814958.html
>Disabling DHCP is a workaround that worked for me.
>
>Posted via http://www.VirtualServerFaq.com - Brought to you by Business
>Information Technology Shop - http://www.bitshop.com

> Thanks. I checked out that link. As I said there, all the IPs are static. I am
> particularly concerned that the action of pinging may be what is keep the Linux
> machine's network connection active.
>
> Any other thoughts about this?
>
> Thanks.
>
> "Anonimous"<(email address - cut out)> wrote:
> >
> >> Hello:
> >>
> >> I have created two Red Hat Enterprise 4 vms. Initally, they appear to behave
> >> fine. But, after working on them for several hours (either via incoming SSH
> >>or,
> >> on the VM, using web browsing), the connectivity just drops. After a period
> >>of
> >> time (from a few minutes to an hours or more), the connection comes back up.
> >>I
> >> have engaged Microsoft tech support on this without much success.
> >>
> >> Here are some of the symptoms: When the connection to VM drops,
> >> - pings from the client workstation to it also fail.
> >> - pings and VMRC access to the host machine still work.
> >> - pings to other VMs (including Linux VMs) sometimes still work. That is,
> >>you
> >> can run two separate ping -t sessions to different VMs on the same host and
> >>one
> >> will work and one will fail.
> >> - Sometimes pings from the host OS to the guest VM will work when the ping
> >>from
> >> the production network fails.
> >>
> >> The configuation is:
> >> - Host: Dell PowerEdge 1850 with four Intel PRO/1000 ports (two onboard; two
> >>in
> >> a dual PCI card) w/ 4GB RAM. One port goes to the production VLAN, one to
> >>the
> >> iSCSI array, and two are disabled.
> >> - Host OS: Windows Server 2003 R2
> >> - Virtualization Environment: Virtual Server 2005 R2 Enterprise
> >> - Guests: two instances of Red Hat Enterprise 4 (Linux); two instances of
> >> Windows Server 2003 Enterprise.
> >>
> >> Any help or suggestions would be very welcome. MS has been close to no help
> >>on
> >> this. I have had many good experiences with MS paid support, but not this
> >>one.
> >> Their staff appear to be shooting in the dark and do not really seem to
> >> understand virtualization or the VS product. I am very close to being forced
> >>to
> >> abandon the whole VS concept.
> >>
> >> Thanks.
> >>
> >> Nordic
> >
> >See http://www.mcse.ms/archive235-2005-10-1814958.html
> >Disabling DHCP is a workaround that worked for me.
> >
> >Posted via http://www.VirtualServerFaq.com - Brought to you by Business
> >Information Technology Shop - http://www.bitshop.com
>
>