Then, there is no need for the IPs (host and guest) to be on the same subnet.
The NIC that is used for the guests needs to be allocated to one VLAN (on your L3 switch, or otherwise connected to the appropriate interface on your router), and the NIC used by the host needs to be patched to a switch port on the other VLAN. Cheers Ken -----Original Message----- From: Stephen Wimberly [mailto:[email protected]] Sent: Tuesday, 3 August 2010 11:13 PM To: NT System Admin Issues Subject: Re: Hyper-V and 'Default Gateway' The box has four NICs in it. Although we currently only have two connected, one is the "Host NIC" and the other is used for the different virtual machines. We have two others we can grow into as need arises. Our Network department charges us per network connection, so we are trying to limit our connections until need arises. The free alternative would be to request multiple IP Addresses in the same range and grow into them as needed. On Sun, Aug 1, 2010 at 10:33 AM, Ken Schaefer <[email protected]> wrote: > If you have multiple NICs on your machine, then there is no need for them to > be all in the same subnet. Obviously they would connect to different > interfaces of a router, or to ports on a switch that are on different VLANs. > > My guess is that you only have a single NIC. In that case, the virtual NIC on > the guest, and the physical NIC on the host are both connected *at the other > end* to a single switch port that needs to be connected to a single VLAN or > router interface. In that case, they need to be on the same subnet. > > Cheers > Ken > > -----Original Message----- > From: Stephen Wimberly [mailto:[email protected]] > Sent: Saturday, 31 July 2010 5:41 AM > To: NT System Admin Issues > Subject: Re: Hyper-V and 'Default Gateway' > > Thanks for the replies! Now I just need to beg our network team for > addresses in the same subnet!!! ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
