ASP Developer Network - Brought to you by Steve Radich and BitShop, Inc. - http://www.bitshop.com

ASPDeveloper

ASPDeveloper.Net / VirtualServerFAQ.COM

Make sure you go to our home page for:

* Virtual Server 2005 FAQ
* ASP.Net 2.0 Information
* ASP.Net 2.0 Streaming Tutorials
* ASP.Net 2.0 HTML based Tutorials

Made possible by Business Internet Technology Shop (BitShop)

Virtual Server 2005

Recent Virtual Server 2005 posts

* Hyper-V. VM"s can"t get external access
* Access denied when using HVRemote command
* Virtual Server in Disaster Recovery
* hello! Want to buy software Retail or OEM, Microsoft, Adobe, Macromedia, Corel Symantec
* hello! WTB SELL ME YOUR software OEM or Retail LARGE and SMALL QTY
* Failover cluster of Hyper-V Virtual Machine with pass-through disk
* hyper-v boot order
* Can"t ping or connect to Hyper-V Server
* Virtual Server 2005
* Question about Virtual Server file sharing and loopback adapter
* Hyper-V How to uninstall integration services from a windows 2008 guest OS?
* How to: Multiple user logins. Same VM
* Hyper-V- How to have shared folders like what we have virtual pc?
* What"s the difference: virtual server vs. virtual pc
* high processor queue length
* Network Bridge / Multiple NIC in virtual network?
* Networking question
* Linux support under Hyper-V
* One RAID Volume for all VM"s or 1:1 for each?
* Is it that easy to convert SCSI drives from VS2k5 to Hyper-V?

Add Solution

Curious ping behaviourwith dual homed phyiscal host - can anyone explain?

Source: microsoft.public.virtualserver
Sent: 05/01/2009
From: "Trust No One®" <(email address - cut out)>
Message:

Hi All,

I was hoping someone can explain the curious behaviour I'm seeing with the
ping command in my Virtual Server 2005 R2 implementation.

The physical host server runs Window 2003 and has 2 network interfaces.
Both interfaces are active and have ip addresses on the same subnet. I've
configured the server so that the VS service is bound to the second network
interface only. The virtual network interface defined in VS references the
second interface.

I've defined a virtual machine in VS and built it as a Windows 2003 domain
controller.

The "curious" behaviour I'm seeing is that when the virtual domain
controller is powered off I can ping both physical network interfaces in the
physical host by their respective IP addresses. However if the virtual
domain controller is powered on then I'm no longer able to ping the second
network interface of the physical host - the one to which VS is bound. This
remains the case until I power off the virtual domain controller.

I can't recall seeing this behaviour in a physical host with a single
network interface - I can always ping the physical host irrespective of
whether VMs are running.

Can anyone explain this behaviour? Is it normal or have I configured
something incorrectly somewhere?

--
Peter <X-Files fan>

Post Reply | This is Spam! | Mark as Spam

Related Messages

Post Reply | This is Spam! | Mark as Spam

Other groups

Virtual PC (Mac)(3592)	Virtual PC(12844)	Virtual PC (French)(496)
Virtual Server 2005(6245)

Our Sponsors

Virtual Server 2005 Info Here!
http://www.aspdeveloper.net

Wiki

Blogs

Articles

Image galleries

File galleries

Forums

Maps

Directories

ASP Developer Network (since 1996) - Brought to you by Steve Radich and BitShop, Inc. - http://www.bitshop.com
Copyright © 1997-2005 by BitShop, Inc. All Rights Reserved.
No content may be reproduced in any form without written permission from BitShop, Inc.
We will be honored to assist with reproduction rights on our material if you contact us.
We also can provide print articles for your magazine, private training seminars at your site, and conference presentations.
Thank you for visiting. Please bookmark our site if you found it useful!
If you wish to make a donation it will help further the development of these free resources: